MS SQL Server


Encrypted Backup in SQL Server 2014

Encryption for Backups is a new feature introduced in SQL Server 2014 and the benefits of this option are
1.Encrypting the database backups helps secure the data.
2.Encryption can also be used for databases that are encrypted using TDE.
3.Encryption is supported for backups done by SQL Server Managed Backup to Windows Azure, which provides additional security for off-site backups.
4.This feature supports multiple encryption algorithms including AES 128, AES 192, AES 256, and Triple DES
5.You can integrate encryption keys with Extended Key Management (EKM) providers.

The following are pre-requisites for encrypting a backup:

1.Create a Database Master Key for the master database.

USE master;
GO
CREATE MASTER KEY ENCRYPTION BY PASSWORD = ‘SomePass@WordStronG123’;
GO
2. Create a certificate or asymmetric Key to use for backup encryption.

Use Master
GO
CREATE CERTIFICATE CertforBackupEncryption
WITH SUBJECT = ‘Certificate for Backup Encryption ‘;
GO
3. Backup the database with encryption:

BACKUP DATABASE [addarr]
TO DISK = N ‘D:Backupaddarr.bak’
WITH
INIT,
COMPRESSION,
ENCRYPTION
(
ALGORITHM = AES_256,
SERVER CERTIFICATE = CertforBackupEncryption
),
STATS = 10
GO
Restoring the encrypted backup:
SQL Server restore does not require any encryption parameters to be specified during restores. It does require that the certificate or the asymmetric key used to encrypt the backup file be available on the instance that you are restoring to. The user account performing the restore must have VIEW DEFINITION permissions on the certificate or key. If you are restoring the encrypted backup to a different instance, you must make sure that the certificate is available on that instance. More info

Back to top

Microsoft SQL Server 2014 White Papers

Analysis Services MOLAP Performance Guide for SQL Server 2012 and 2014
Database Backup Encryption
Idle Connection Resiliency
In-Memory OLTP – Common Workload Patterns and Migration Considerations
In-Memory OLTP – SQL Server In-Memory OLTP Internals Overview
Introducing Microsoft Business Intelligence (BI) Tools
Microsoft IT: A Case Study on “Hekaton” against RPM – SQL Server 2014 CTP1
Migrating Content Between Report Servers
Optimizing Your Query Plans with the SQL Server 2014 Cardinality Estimator
SQL Server 2014 and Windows Azure Blob Storage Service: Better Together
Using Power BI in a Hybrid Environment

 

Product Documentation

Books Online for SQL Server 2014
Developer Reference for SQL Server 2014
Installation for SQL Server 2014
Setup and Servicing Installation
Upgrade Advisor
Tutorials for SQL Server 2014
Microsoft JDBC Driver 4.0 for SQL Server
Microsoft Drivers for PHP for SQL Server
Microsoft ODBC Driver for SQL Server
Microsoft OLE DB Provider for DB2 Version 5.0

Microsoft SQL Server 2012 White Papers

A Case Study on Building a Highly Scalable Enterprise Application that uses Massively Parallel Processing (MPP) to Deliver High Performance and Scalability on SSIS-SQL Server 2012
AlwaysOn Solution Guide: Offloading Read-Only Workloads to Secondary Replicas
AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using AlwaysOn Availability Groups
AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups
An Analysis Services Case Study: Using Tabular Models in a Large-scale Commercial Solution
Benefits of Dynamic Rolling Twelve Month Dimension in Tabular Models
Choosing a Tabular or Multidimensional Modeling Experience in SQL Server 2012 Analysis Services
Cleanse and Match Master Data by Using EIM
Cross-cluster Migration of AlwaysOn Availability Groups for Operating System Upgrades
Data Access Tracing in SQL Server 2012
Exporting Master Data from Master Data Services
Extending SSIS Capabilities by Creating Custom SSIS Components for SharePoint
Extracting and Loading SharePoint Data in SQL Server Integration Services
Fast Track Data Warehouse Reference Guide for SQL Server 2012
Hardware Sizing a Tabular Solution (SQL Server Analysis Services)
How to Choose the Right Reporting and Analysis Tools to Suit Your Style
How to Cluster SQL Server Analysis Services
Installing Master Data Services in an AlwaysOn Environment
Introducing the BI Semantic Model in Microsoft® SQL Server® 2012
Leveraging a Hadoop cluster from SQL Server Integration Services (SSIS)
Master Data Services (MDS) Operations Guide
Microsoft BI Authentication and Identity Delegation
Microsoft IT: A case study on Business Continuity and Disaster Recovery – SQL Server 2012
Microsoft SQL Server AlwaysOn Solutions Guide for High Availability and Disaster Recovery
Migrating Content Between Report Servers
Migration Guide: Migrating to AlwaysOn Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping, Part 1
Migration Guide: Migrating to SQL Server 2012 Failover Clustering and Availability Groups from Prior Clustering and Mirroring Deployments, Part 1
Optimized Bulk Loading of Data into Oracle
Patching SQL Server Failover Cluster Instances with Cluster-Aware Updating (CAU)
Performance Evaluation of XtremIO Flash Array in a SQL 2012 BI Environment
Performance Tuning of Tabular Models in SQL Server 2012 Analysis Services
Plan Caching and Recompilation in SQL Server 2012
Planning Disaster Recovery for Microsoft SQL Server Reporting Services in SharePoint Integrated Mode
Power View Infrastructure Configuration and Installation: Step-by-Step and Scripts
Resource Governor in SQL Server 2012
Securing the Tabular BI Semantic Model
SQL Server 2012 Parallel Data Warehouse – A Breakthrough Platform for Next-Generation Data Warehousing and Big Data Solutions
SQL Server 2012 Upgrade Technical Guide
SQL Server Analysis Services to Hive
SSIS for Azure and Hybrid Data Movement
SSIS Operational and Tuning Guide
Statistical Analysis in Excel and SQL Server Analysis Services: An Example using Boxplot
Using AlwaysOn Availability Groups for High Availability and Disaster Recovery of Data Quality Services
Using DirectQuery in the Tabular BI Semantic Model

 

Back to top

 SQL server 2012 Service pack 1 upgrade bug issue there

1: SQL service did not turn up after the Service pack Upgrade and received the message at Event viewer “service specific error code 3417”

Workaround: To resolve the issue we have to repair the sql server service.

*    Launch the SQL Server 2012 Setup program (setup.exe) from the distribution media.
*    In the left navigation area, click Maintenance, and then click Repair.
*    Setup support rule and file routines run to ensure that your system has prerequisites installed and that the computer passes Setup validation rules. Click OK or Install to continue.
*    On the Select Instance page, select the instance to repair, and then click Next.
*    The repair rules will run to validate the operation. To continue, click Next.
*    From the Ready to Repair page, click Repair. The Complete page indicates that the operation is finished.

Note: The important note is the sql server is appeared along with all existing user databases so safely we can go for the existing environment. Earlier we have to attach the user database again after rebuild the system databases but in 2012 no need to worry for the same. As a safety   you can copy the data file and log files for user database and msdb database. The repair command rebuilds the system databases and the above option applicable if you don’t have the master database backup. Once the repair has been done successfully afterwards you have to start the sql server service manually from configuration manager.

2: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.

To resolve the above issue we have to install the Visual studio service pack. It is a known bug in SQL 2012 SP1 and it forces the need for a complete install of Visual Studio 2010.  The version that is installed I don’t think will work.

Note: SQL cannot be updated until Visual Studio is installed, and SP1 applied to VS2010.  Then we can update SQL to SP1. Reference link here

Back to top

 

SQL Server 2014 has several new features.

sql2014_now

SQL Server 2014 has several enforce new features that can definitely justify an upgrade. There is a no-doubt, the most notable new feature is the new In-Memory OLTP engine, which promises some big performance improvements for OLTP applications. The past couple of SQL Server releases have had a strong focus on business intelligence (BI), which makes the new In-Memory OLTP engine an especially for relational database professionals.

 New In-Memory OLTP Engine

The most important new feature in SQL Server 2014 is the In-Memory OLTP engine (formerly code-named Hekaton)-(I already mention in last blog). By moving select tables and stored procedures into memory, you can drastically reduce I/O and improve performance of your OLTP applications. Microsoft states that some applications can expect up to a 20x performance improvement. Edgenet, an early adopter, saw a 7x performance increase in its online and retail supply application.

The In-Memory OLTP engine is designed for high concurrency and uses a new optimistic concurrency control mechanism to eliminate locking delays. The In-Memory OLTP tables are copied into memory and made durable by transaction log writes to disk. An all-new lock-free engine processes the transactions for memory-resident tables. Stored procedure performance is improved by compiling the stored procedures into native code DLLs. Standard T-SQL stored procedures are interpreted, which adds overhead to the execution process. Compiling the stored procedures to native Win64 code makes them directly executable, thereby maximizing their performance and minimizing execution time.

You evaluate how the In-Memory OLTP engine will improve your database performance, Microsoft includes the new Analysis, Migrate, and Report (AMR) tool. Like its name suggests, the AMR tool analyzes your database and helps you identify the tables and stored procedures that would benefit from moving them into memory. It lists the expected performance improvements as well as any incompatibilities that need to be addressed. In addition, the AMR tool can help you perform the actual migration of tables to the new memory-optimized format.

The In-Memory OLTP engine works with commodity server hardware, but it has a number of limitations. For instance, not all of the data types are supported. Some of the data types that aren’t supported for memory-optimized tables include geography, hierarchyid, image, text, ntext, varchar(max), and xml. In addition, several database features can’t be used with the new In-Memory OLTP capability. Database mirroring, snapshots, computed columns, triggers, clustered indexes, identity columns, FILESTREAM storage, and FOREIGN KEY, CHECK, and UNIQUE constraints aren’t supported.

The In-Memory OLTP engine is supported on Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 SP2. In addition, you need to be using the SQL Server 2014 Enterprise, Developer, or Evaluation edition. Notably, In-Memory OLTP won’t be supported on the SQL Server 2014 Standard edition.

Windows Server 2012 Integration

SQL Server 2014 provides improved integration with Windows Server 2012 R2 and Windows Server 2012. SQL Server 2014 will have the ability to scale up to 640 logical processors and 4TB of memory in a physical environment. It can scale up to 64 virtual processors and 1TB of memory when running on a virtual machine (VM).

SQL Server 2014 also provides a new solid state disk (SSD) integration capability that enables you to use SSD storage to expand SQL Server 2014’s buffer pool. The new buffer pool enhancements can help increase performance in systems that have maxed out their memory capability by using high-speed nonvolatile RAM (NVRAM) in the SSD drives as an extension to SQL Server 2014’s standard buffer pool. The new buffer pool extensions can provide the best performance gains for read-heavy OLTP workloads.

SQL Server 2014’s Resource Governor provides a new capability to manage application storage I/O utilization. First introduced with SQL Server 2008, the Resource Governor originally enabled you to limit the amount of CPU and memory that a given workload can consume. SQL Server 2014 extends the reach of the Resources Governor so that you can now manage storage I/O usage as well. The SQL Server 2014 Resource Governor can limit the physical I/Os issued for user threads in a given resource pool, allowing you to have more predictable application performance.

SQL Server 2014 also integrates with several new and improved features in Windows Server 2012 R2 and Windows Server 2012, i.e. SQL Server 2014 supports the OSs’ new Storage Spaces feature. With Storage Spaces, you can create pools of tiered storage to improve application availability and performance. In addition, SQL Server 2014 can take advantage of the OSs’ Server Message Block (SMB) 3.0 enhancements to achieve high-performance database storage on Windows Server 2012 R2 and Windows Server 2012 file shares. Many enhancements were made to SMB 3.0, with the most notable being SMB Transparent Failover and SMB Direct. The new SMB Transparent Failover feature provides highly reliable SMB storage that’s fully supported for applications like SQL Server and Hyper-V. With the new SMB Direct feature, you can leverage the NIC’s Remote Direct Memory Access (RDMA) feature to provide access speeds for SMB file shares nearing the access speed for local resources.
Enhancements to AlwaysOn Availability Groups – HA

SQL Server 2014’s AlwaysOn Availability Groups has been enhanced with support for additional secondary replicas and Windows Azure integration. First introduced with SQL Server 2012, AlwaysOn Availability Groups boosted SQL Server availability by providing the ability to protect multiple databases with up to four secondary replicas. In SQL Server 2014, Microsoft has enhanced AlwaysOn integration by expanding the maximum number of secondary replicas from four to eight. Readable secondary replicas are now available for read-only workloads, even when the primary replica is unavailable. SQL Server 2014 also provides Windows Azure AlwaysOn integration. This new integration feature enables you to create asynchronous availability group replicas in Windows Azure for disaster recovery. In the event of a local database outage, you can run your SQL Server databases from Windows Azure VMs. The new Windows Azure AlwaysOn availability options are fully integrated into SQL Server Management Studio (SSMS).                                  Back to top

SQL 2014 Backups

Database backups in SQL Server now support built-in database encryption. Previous releases all required a third-party product to encrypt database backups. The backup encryption process uses either a certificate or an asymmetric key to encrypt the data. The supported backup encryption algorithms are Advanced Encryption Standard (AES) 128, AES 192, AES 256, and Triple DES (3DES).

SQL Server 2014 also provides new Windows Azure integration to SQL Server’s backup capabilities. You can specify a Windows Azure URL as the target for your SQL Server 2014 database backups. This new Windows Azure backup feature is fully integrated into SSMS.
Updateable Columnstore Indexes

Columnstore indexes are another of Microsoft’s high performance in-memory technologies. Microsoft introduced the columnstore index in SQL Server 2012 to provide significantly improved performance for data warehousing types of queries. Microsoft states that for some types of queries, columnstore indexes can provide up to 10x performance improvements. However, in the original implementation of the columnstore indexes, the underlying table had to be read-only. SQL Server 2014 eliminates this restriction. The new updateable columnstore index enables updates to be performed to the underlying table without first needing to drop the columnstore index. A SQL Server 2014 columnstore index must use all of the columns in the table, and it can’t be combined with other indexes.
SQL Server Data Tools for Business Intelligence

Previously known as Business Intelligence Development Studio (BIDS) 🙂 and SQL Server Data Tools (SSDT), the new SQL Server Data Tools for BI (SSDT BI) is used to create SQL Server Analysis Services (SSAS) models, SQL Server Reporting Services (SSRS) reports, and SQL Server Integration Services (SSIS) packages. SSDT BI is based on Microsoft Visual Studio 2012 and supports SSAS and SSRS for SQL Server 2014 and earlier, but SSIS projects are limited to SQL Server 2014. In the pre-release version of SQL Server 2014 Community Technology Preview 2 (CTP2), SQL Server Setup doesn’t install SSDT BI. Instead, you must download it separately from the Microsoft Download Center.

Power BI for Office 365 is Microsoft’s cloud-based BI solution that leverages familiar Office 365 and Excel tools. Power BI for Office 365 provides business insights through data visualization and navigation capabilities. Power View’s new multidimensional support, go to MSDN’s Power View for Multidimensional Models

Microsoft’s Power BI for Office 365 tools at Microsoft’s Power BI for Office 365

SQL Server 2014, check this out MSDN’s Deprecated Database Engine Features in SQL Server 2014 and Discontinued Database Engine Functionality in SQL Server 2014

2014

Now ask your self as DBA, DBD Time to Upgrade? or ..

Welcome any and all feedback from all sql dude’s there

Mehboob

Microsoft Certified Solutions Associate (MCSA)                                    Back to top

 

SP For SQL

Microsoft provides support on the current service pack, and in some cases the immediately preceding service pack, for the products listed below. Export this table to a exl file

Service & service pack, for the products listed Service Pack Support End Date

Microsoft has released Cumulative Update for SQL Server 2014.

  • KB Article: KB #2931693
  • 114 fixes listed at time of publication (121 total)
  • Build number is 12.0.2342
  • Relevant for @@VERSION 12.0.2000 through 12.0.2341

SQL Server 2012 Service Pack 1

The SQL Server team has released SQL Server 2012 SP1 Cumulative Update.

  • KB Article: KB #2954099
  • Build # is 11.0.3431
  • Currently there are 36 public fixes listed (38 total)

The SQL Server team has released SQL Server 2012 SP1 Cumulative Update.

  • KB Article: KB #2931078
  • Build # is 11.0.3412
  • Currently there are 29 public fixes listed (33 total)

The SQL Server team has released SQL Server 2012 SP1 Cumulative Update.

  • KB Article: KB #2917531
  • Build # is 11.0.3401
  • Currently there are 32 public fixes (34 total); the most interesting to me are:
    • KB #2892741 – FIX: Query that you run against a partitioned table returns incorrect results in SQL Server 2008, SQL Server 2008 R2 or SQL Server 2012
    • KB #2888996 – FIX: Data purity corruption in sys.sysbinobjs table in master database when you log on to SQL Server 2008 R2 or SQL Server 2012 by using the SA account and then run DBCC CHECKDB
    • KB #2901714 – FIX: Server crashes when you import a Windows Azure SQL database to a local SQL Server 2012 database
    • KB #2918791 – FIX: The system function sys.fn_hadr_backup_is_preferred_replica does not work correctly after you have CU7 for SQL Server 2012 SP1 installed
    • KB #2923460 – FIX: The query deadlocks when the ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT are enabled in SQL Server 2012

Update for SQL Server 2008 SP3, here we go ….                 Back to top

The final Update for SQL Server 2008 SP3

Microsoft has released the final Cumulative Update  for SQL Server 2008 Service Pack 3.
  • Build # 10.00.5861
  • KB Article: KB #2958696
  • 9 public fixes
  • Relevant for builds 10.00.5500 -> 10.00.5860
  • NOT for SQL Server 2008 R2 (10.50.xxxx)

Once more, this is the last cumulative update for SQL Server 2008. Both 2008 and 2008 R2 exit mainstream support in July of this year. That’s two months away. If you want a final service pack for either or both of these major versions, and want your voice high and heard, just vote and express your opinions on this connect sql team, Good Luck

Connect #814658 : Release Final Service Packs for SQL Server 2008 and 2008 R2

January 2014 Cumulative Update for SQL Server 2008 SP3

Microsoft has released SQL Server 2008 Service Pack 3 Cumulative Update

  • Build # 10.00.5850
  • KB Article: KB #2923520
  • 3 public fixes (4 total)
  • Relevant for builds 10.00.5500 -> 10.00.5849
  • NOT for SQL Server 2008 R2 (10.50.xxxx)

Microsoft has released the final Cumulative Update (#17) for SQL Server 2008 Service Pack 3.

  • Build # 10.00.5861
  • KB Article: KB #2958696
  • 9 public fixes
  • Relevant for builds 10.00.5500 -> 10.00.5860
  • NOT for SQL Server 2008 R2 (10.50.xxxx)

Once more, this is the last cumulative update for SQL Server 2008. Both 2008 and 2008 R2 exit mainstream support in July of this year.

April 2014 Update for SQL Server 2008 R2 SP2

Microsoft has released Cumulative Update #12 for SQL Server 2008 R2 Service Pack 2.

  • KB Article: KB #2938478
  • 13 fixes listed at time of publication
  • Build number is 10.50.4305
  • Relevant for @@VERSION 10.50.4000 through 10.50.4304

Microsoft provides support on the current service pack, and in some cases the immediately preceding service pack, for the products listed below. See the Lifecycle Support Policy FAQ for details on the Service Pack Support Policy. If you have any questions regarding support for a product, please contact your Microsoft representative. If you need technical support, visit the Contact Microsoft Web site.

Mehboob

Microsoft Certified Solutions Associate (MCSA)                                        Back to top

 

 

Microsoft Business Intelligence

 

MS BI Whitepapers

 

 

 

 

Mehboob

Microsoft Certified Solutions Associate (MCSA)             Back to top

Microsoft Cert BI – 70-463

I passed in 463 exam so i want to share this through this blog some of my notes for other to prepare. Visit here for more info:  Implementing a Data Warehouse with Microsoft SQL Server 2012

Skills Measured:

•Design and implement dimensions
•Design and implement fact tables
•Define connection managers
•Design data flow
•Implement data flow
•Manage SSIS package execution
•Implement script tasks in SSIS
•Design control flow
•Implement package logic by using SSIS variables and parameters
•Implement control flow
•Implement data load options
•Implement script components in SSIS
•Troubleshoot data integration issues
•Install and maintain SSIS components
•Implement auditing, logging, and event handling
•Deploy SSIS solutions
•Configure SSIS security settings
•Install and maintain Data Quality Services
•Implement master data management solutions
•Create a data quality project to clean data

Let start with Why do we need a Data Warehouse ?

1) Data stored in normalized schema in OLTP systems can have hundreds to thousands of tables for an enterprise. OLTP systems have a probability, that a portion of these tables can be often less descriptive due to lack of self relevant naming conventions. This makes designing queries harder for reporting purposes.

2) As normalised schema has a lot of tables, a single piece of related information is split and stored into various tables with referential integrity constraints. This means that reading this data requires creating joins with many tables. For reporting and analysis purposes over a very huge dataset spanning thousands to millions of records of historical data, such queries would perform very poorly.

3) OLTP systems tend to archive data time to time on a scheduled basis. It might be in the form of hard / soft delete. Lack of historical data can limit the level of analysis that can be performed on the data.

4) OLTP systems tend to store most updated version of data only. For ex employee address, product name, martial status etc. Generally history for such attributes would not be preserved, which results in loss of historical data. Lack of history for such attributes can limit the level of analysis that can be performed on the data.

5) OLTP data in an enterprise can be federated across different departments / business units / associate group companies. Each of it would typically have their own set of applications. There would be inevitably as set of common master data duplicated across the units. Due to duplicate and non-synchronized master data, consolidated reporting and analysis that combines data across the enterprise becomes almost impossible.

6) As each working unit of an enterprise can have their own OLTP system, different attributes can have data representation in different forms for the same data. For ex, an employee is permanent can be represented by Yes / No, Y / N, 1 / 0 etc. Even this makes data extremely difficult to interpret and hence raising the challenges to a centralized reporting over the enterprise data.

7) OLTP systems can contain data in free form, which can lead to degraded data quality. For example, free form address entry can lead to a very poor quality of geographic information due to typographic mistakes, effectively leading to unusable data and inviting data cleansing exercise.

8) OLTP systems tend to have a very good classification of business entities, but the some entities required for analysis are not normalized to the most detailed extent. For example, attributes related to date would would stored in datetime format. Entities like date and time has constituents like day / week / month / quater / year / fiscal year / sec / minute / hour etc. Mostly reporting and analytics works on a time scale. To report data based on any particular constituent of date / time, it would require extracting this constituent from the date value on a very huge dataset. This could lead to great performance issues.
What is a Star schema and when it should be used ?

1) Data model / schema used to create a data warehouse is also known as dimensional model. In this model, reference / lookup / master tables are called dimensions. Measureable details of data are called measures / facts and the tables that host the same are called Fact Tables.

2) Typcially, a simplified denormalized schema that covers the most granular section of a business entity can be represented by a star schema. Such a schema would have a single fact table containing measurable / aggregatable values. This fact table would have foreign keys from all dimension tables that completes identity of that record and provides different angles of analysis.

If you look at AdventureworksDW 2012 schema, FactInternetSales / FactResellerSales is a Fact Table. This table has reference from different dimensions like Date, Time, Product, Customers etc. Together these Fact and Dimensions form a schema known as Star Schema.
What is a Snowflake schema and when it should be used

1) A typical dimension is a highly denormalized business entity. If the same is normalized to 2nd or 3rd normal form, then the same star schema is termed as snowflake schema. For example, Product-ProductCategory-ProductSubCategory, Country-State-City etc are examples of snowflaked Product and Geography dimension respectively.

2) From a warehousing perspective, any data analysis done on data sourced from warehouse directly would suffer performance due to more joins as a result of more tables in a snowflake schema. From the perspective of creating data marts, snowflake schema would provide options to source data more selectively to datamarts.

3) Any typical enterprise class dimensional model would inevitably contain a snowflaked model of schema. Even if one selects not to normalize business entity into normalized dimensions, still dimensions would contain some common attributes like date keys, time keys, status keys etc. So Date dimension would be related Patent dimension by the date key for patenteddate field.
What is a Conformed Dimension ?

1) Theoretically considering if each discrete business area has a star schema, then different business areas typically tend to be connected to be each other. So if a star schema is created for each business unit in a enterprise, all these star schemas would have to be connected too.

2) Two schemas can be connected when they have something in common. If a dimension is shared across more than one schemas, then such dimensions are known as conformed dimensions. For ex, Date dimension would be shared by almost all the Fact tables in the schema.
What is a Data mart ?

1) Using a data warehouse as the source, technologies like SQL Server Analysis Services creates multidimensional data structures known as Cube. A cube contains dimensions and measures that can be used for large scale real-time analysis. These systems are known as Online Analytical Processing (OLAP) applications.

2) Typically a data warehouse can contain data from the entire enterprise along with history. A data mart would source data from a data warehouse and build specialized data structures on the top of the same for reporting and analytics.
What is Dimensionality / Granularity ?

1) If two business entities contain data at the same scale, then they are said to be at the same level of granularity. For example, if sales data is stores weekly in facts and orders data is stored daily, then order data can be said to have a lower granularity compared to sales.

2) To associate two entities in a dimensional model, they need to be calculated as the same level of granularity.
How does dimensional modeling of a data warehouse enable / empower analytics ?

1) Data analysis often requires pivoting huge amounts of data. Attributes of a dimension (i.e. columns in a dimension table) ideally contains non-continuous data. Such data is often suitable to slice / pivot data and can be used as a scale axis to visualize categorized data on a graph. Even if the data in attributes is continuous (i.e. data contains lots of distinct values), OLAP technologies like SSAS provides was to categorize continuous data into discrete categories.

2) For example, if we try to plot data on a graph use values in Age attribute for the population in a city, on A or B axis, then there would be inevitably 100 bars on a graph which is almost impossible to analyze. A better approach would be to divide age attribute in few distinct age groups and use those groups on the graph. Each group would represent a bar, and upon drilling down the bar, actual data can be brought on the graph.
Why do dimension tables often include columns that cannot be used for pivoting / filtering / analytics ?

1) Often dimensions like Geography, Employee, Account, Products etc have attributes describing the dimension member. For example Employee dimension can have attributes like Gender, Date of Birth, Marital Status, Number of children etc.. Such attributes are neither good candidates for pivoting nor for any kind of roll-ups or aggregation.

2) However broad or narrow be the analytical spectrum, inevitably almost any such system would have reporting on the top of it. If the dimensions have only pivotable or aggregatable attributes, then such data would be sufficient only to plot on a graph but not on a detailed report. Such data can facilitate drill-down, but not drill-through of the problem. For drill-through, one would require different attributes based on which a report can be sketched out.

3) For an Employee report, one might start to analyze a report based on salary attribute as it is pivotable. For example, list all employees whose gross income is less than 90k USD. But post that one would want to check which of those are women having more than three kids and are aged over fifty, to balance work load on them. For such a report, if dimensions do not contain such attributes, then a cross-database query joining data warehouse and transactional OLTP database would be required. This results in poor performance and other reporting issues. Hence such attributes are included in a dimension. Such attributes in a dimension are called member properties.
What are hierarchies and how they help in analytics ?

1) Attributes within a dimension as well as across dimensions can be related and well as unrelated. For example, date of birth and gender are unrelated attributes, but country and city are related attributes. Related attributes are often pivotable and form a hierarchy called natural hierarchies. Unrelated attributes have lesser probability of forming a hierarchy, and if they do, then it’s called unnatural hierarchies.

2) Hierarchies provide a drill-down path for data analysis are the data can be pivoted. Aggregatable attributes can only be rolled-up but cannot be drilled down to another level based on another related / unrelated attribute. For example salary can be rolled up from daily to the highest possible granularity. But to drill down salary from Year-Month-Week, a hierarchy made up of Year, Month and Date attributes is required which would slice rolled-up values of Salary attribute. Hierarchies formed of two or more related / unrelated attributes can be drilled-down which are very useful for analytics.
How to accommodate changing attribute values of a dimension in a dimensional model ?

1) Data archival policy is often overlooked or considered a trivial aspect in database modeling. But in data warehouse it has a very deep impact on the modeling itself. Facts should ideally contain transactional data, so there is no question of data update. Dimension attributes often have changing values, which might be worth keeping a track. For example, an organization might not be interested in keep a track of every time when an employee had children but only total number of children as of the latest status. But say, if the employee is a sales person, an organization would want to keep track of the field area where the sales executive was posted at any point in time. Without tracking this history, reports would always show that sales executive has operated in one area which might be his/her present area of operation, as the attribute value is always updated / overwritten. Such changing values of attributes in a dimension are addressed by a design aspect known as Slowly Changing Dimension (SCD).

2) SCD are of three types, based on how attribute history has to be preserved.

SCD-Slowly Changing Dimension Type 1: Attributes for which values are updated / overwritten, and history is not maintained is know as SCD Type 1.

SCD Type 2: To maintain history, at a minimum three new columns are added to the dimension – ValidFrom, ValidTill, and IsCurrent. ValidFrom and ValidTill defines the time scope during which the value was valid, and IsCurrent helps queries to easily identify the latest value of the attribute(s). When a value changes for an attribute, the ValidTill value is updated with the current date, and IsCurrent is marked as “N”. A new record with the latest value of the attribute is added to the dimension, having ValueFrom as the current date, ValidTill as NULL and IsCurrent as “Y”.

SCD Type 3: If one decided to maintain history of attribute values, and if the attribute values are frequently changing, then the dimension can have rapidly changing values (often known as rapidly changing dimension). Due to the same, dimension would have huge amount of dimension members effectively translating into performance issues in dimension processing as well as querying. Type 3 is a method where one can limit the amount of history to be preserved. Only the latest value and the one before that are preserved. Due to this design, the tracking and scoping fields required in Type 2 would not be required in Type 3.
How are dimensions (especially slowly changing dimensions) associated with facts in a dimensional model ?

1) Any dimension would have a business key, which is one of the candidates for primary key, for example ProductID in Product dimension. If a dimension does not have any SCD attributes, then Business key can be used as the primary key for the dimension. But in other case, whenever a new record is inserted for a SCD attribute, the business key would get duplicated. So to manage this, SCD dimensions have another field that acts as a placeholder of primary key – popularly known as Surrogate Key. This field would typically have auto-increment identity values in most of the cases.

2) Primary keys in a dimension act as a foreign keys in fact tables, which enables pivoting data based on dimension attributes for analytics. Business keys in a dimension helps in maintaining lineage with OLTP data sources, from where data is collected and warehoused typically using ETL methods. One can’t correctly slice data in a fact with a dimension whose key is not present directly / indrectly in the fact table. A combination of all the foreign keys in a fact table can be used as a composite primary key in many cases.

3) If a fact table is not associated with a dimension table, and still one wants to associate a dimension with a fact without adding primary key from dimension into the fact table, one can create bridge fact tables. These bridge tables contain only keys from dimension and fact, which creates an indirect association between dimension and fact tables.
What are measures and where are they stored ?

1) Attributes of a fact table are known as measures. Fact table should contain calculable data, which is measure of different attributes of an entity. For example, for a Sales fact table would have order value, number of units in order, tax on order value etc, profit margin percentage etc.

2) Additivity of different measures can be different – some can be fully additive like order value, some can be partially additive like tax, and some can be non-additive like profit margin percentage. Based on the nature of addivity, different aggregation functions can be applied on the attributes for roll-ups.
Infographics in a BI Solution: Data mined from unstructured data source can very well generate content to extract intelligence reported in the below infographic.

BI Solution_infographic

 

Welcome any comments:

Mehboob

Microsoft Certified Solutions Associate (MCSA)                   Back to top

E-Books in English – SQL Server 2012

5 Tips for a Smooth SSIS Upgrade to SQL Server 2012
A Hitchiker’s Guide to Microsoft StreamInsight Queries
Books Online: Backup and Restore of SQL Server Databases

Books Online: Data Analysis Expressions (DAX) Reference
Books Online: Data Mining Extensions (DMX) Reference
Books Online: Data Quality Services
Books Online: High Availability Solutions
Books Online: Master Data Services
Books Online: Monitor and Tune for Performance
Books Online: Multidimensional Expressions (MDX) Reference
Books Online: SQL Server Distributed Replay
Books Online: Transact-SQL Data Definition Language (DDL) Reference
Books Online: Transact-SQL Data Manipulation Language (DML) Reference
Books Online: XQuery Language Reference
Data Access for Highly-Scalable Solutions: Using SQL, NoSQL, and Polyglot Persistence Extracting and Loading SharePoint Data in SQL Server Integration Services
Integration Services: Extending Packages with Scripting
Introducing Microsoft SQL Server 2008 R2
Introducing Microsoft SQL Server 2012
Master Data Services Capacity Guidelines
Master Data Services (MDS) Operations Guide
Microsoft SQL Server AlwaysOn Solutions Guide for High Availability and Disaster Recovery Microsoft SQL Server Analysis Services Multidimensional Performance and Operations Guide Multidimensional Model Programming
Optimized Bulk Loading of Data into Oracle
Planning Disaster Recovery for Microsoft SQL Server Reporting Services in SharePoint Integrated Mode
QuickStart: Learn DAX Basics in 30 Minutes
SQLCAT’s Guide to BI and Analytics
SQLCAT’s Guide to High Availability Disaster Recovery
SQLCAT’s Guide to Relational Engine

SQL Server 2012 Tutorials: Analysis Services – Data Mining
SQL Server 2012 Tutorials: Analysis Services – Multidimensional Modeling
SQL Server 2012 Tutorials: Analysis Services – Tabular Modeling
SQL Server 2012 Tutorials: Reporting Services
SQL Server 2012 Tutorials: Writing Transact-SQL Statements
SQL Server 2012 Upgrade Technical Guide
SQL Server Community FAQs Manual
Transact SQL by TechNet WiKi Community
Troubleshooting SQL Server AlwaysOn

Welcome any comments here, back again.              Back to top

SQL Server 2008 Active-Passive/Active-Active Cluster 

SQL Server 2008 supports clustering using both the Standard and Enterprise editions. The Standard edition supports a two-node cluster, and the Enterprise edition supports the maximum number of nodes that the OS supports. The biggest changes in SQL Server 2008 cluster is that you can now use DHCP for clustering and use IP addresses from different subnets for each side of the cluster. The ability to use IP addresses from different subnets is most useful for creating multisite clusters, called geographically clusters.

I hope you had done with all the pre-requisites required by cluster.If you’re installing SQL Server 2008 in a cluster on Windows 2003, you’ll need to download and install the hotfix specified in the Microsoft article at before you can install SQL Server 2008. Installation of above hotfix requires a reboot, so you have to cancel out of the installer at this point and restart the process after installing that hotfix on all your cluster nodes.

Cluster00

Once you have selected option, installation will check for setup support rules to identify the problem. If it is failed due to any reason, you have to correct the issue. Please find the
below screen shot. If it passed click on OK command button.

Cluster01

Installation wizard will install the setup support files, click on Install command button.

Cluster02

Click on Next button

1. Product Key

2. Licence Terms

3. Feature Selection

4. Disk Space Reuirements

5. Error and Usage Reporting

6. Cluster instllation Rules

7. Ready to install

8. Installation Progress.

Cluster03

Enter Product Key or It will take automatically. See the below down for it.

Cluster04

Select required features, which you want install.

Cluster05

Specify the Network Name/Virtual Name for SQL Server to failover. As we are installing Active-Passive cluster we have to specify one virtual/network name. Active-Active clustering you have specify different network names as per the number of nodes.

Cluster06

SQL Server will review the disk space requirement for the features you have selected.

Cluster07

Create a new cluster resource group for your SQL server failover.

Cluster08

Select shared cluster disk resources for your SQL Server failover cluster.

Cluster09

Here you have to select network resources for your SQL Server failover cluster. You have to add IP address as well.

Cluster10

Service Account for SQL Server services, it is a best practice always keeps SQL Services in cluster in manual mode

Cluster11

Authentication more and SA password in account provisioning tab, configure the location of the data files, log files, temp database in data directories tab and enable file stream as per the requirement

Cluster13

Cluster14

Cluster15

SQL Server cluster is ready to install. Click on Install button.

Once installation is done on this node, we have to proceed with the installation of SQL Server on the other cluster nodes SQL Server 2008, we must manually install and patch each cluster node individually. This process allows for less downtime as we are patching the cluster or upgrading your cluster from SQL Server 2005 to SQL Server 2008.

Installation on the other nodes is similar to installing on the first node except that we have select the Add Node to a SQL Server failover cluster option from the initial menu. The same software requirements apply to the other nodes in the cluster, so the installer will handle the verification and installation of these components as well. Because most of the settings are picked up from the other node(s) in the cluster that already have SQL Server installed on them, the process of adding a node to the cluster is bit shorter than installing on the first node.

Installation on the other nodes is similar to installing on the first node except that we have select the Add Node to a SQL Server failover cluster option from the initial menu. The same software requirements apply to the other nodes in the cluster, so the installer will handle the verification and installation of these components as well.

Because most of the settings are picked up from the other node(s) in the cluster that already have SQL Server installed on them, the process of adding a node to the cluster is bit shorter than installing on the first node.

Cluster17

Just do next and next till you came on instance choice, write you instance name

Configure your new SQL Server installation — To reduce the attackable surface area of a system, SQL Server selectively installs and enables key services and features. For more information, see Understanding Surface Area Configuration on MSDN.

Welcome any comments:

Mehboob

MCTS –
//

SQL Server 2014 & 2012 feature’s

The release of SQL Server 2014 (CTP1) has brought good amount of new features and enhancements. Some of the notable features are presented below.

🙂    Database Engine Enhancement:
*        In-Memory OLTP for ~10X performance gains by moving most used tables into memory.
*        Updatable and clustered column store indexes for faster retrieval.
*        Enhanced query processing for better performance without app changes.
*        Buffer Pool extension to SSDs for faster paging.
*        Resource Governor controls IO along with CPU and memory.
*        Enhanced Always On now supports 8 secondary for better HA (High Availability)

🙂    Business Intelligence Enhancement:
*      Power Query (formally codename “Data Explorer”) in Excel makes easy to access Internal and External data (both Relational and Non-Relational).
*    Power Map (formally codename “Geo Flow”) in Excel can be used to get insights with 3D visualization.
Parallel Data Warehouse with Polybase to support querying Big Data with T-SQL.

🙂    Cloud support Enhancement:
*     Simplified cloud Backup and Deployment lets you Backup and Restore from SQL Azure/Windows Azure VM to SQL Server and vice-versa.
*    HA/Always On in Azure helps to handle disaster recovery.

Backup Encryption
Encrypting backups gets simpler in SQL Server 2014.  Check out a great illustration of the how you can prevent anyone from taking your backup file and restoring it to another database server with the new SQL Server 2014 encryption capabilities.

First start with Hekaton , yes that correct Code Name is Hekaton.

SQL Server 2014’s few new feature is its addition of the in-memory OLTP engine, formerly code-named “Hekaton.”  This engine allows for in-memory optimized tables within a conventional relational database.  Furthermore, stored procedures that operate on memory-optimized tables, though written in Transact SQL, are in fact compiled to native machine code.  The combination of in-memory data manipulation and native code execution makes for highly accelerated operations with certain workloads, and certain types of queries.

Another feature of SQL Server 2014 is the addition of updatable columnstore indexes to the product. SQL Ent have a full-fledged column store database while continuing to operate as the conventional row store database it has always been.  While columnstore indexes were introduced in SQL Server 2012, they were not updatable, making it tricky to keep data warehouses tables using these indexes updated.  With SQL Server 2014, that significant shortcoming is eliminated.

These two features, Microsoft is pushing a “one-stop-shop” approach to database management.  SAP and other vendors offer separate, specialized products for in-memory operation, and may require the purchase of high-end appliances to take advantage of column store technology.

Hekaton is a new database engine optimized for memory resident data and OLTP workloads. Hekaton is fully integrated into SQL Server; it is not a separate ystem advantage of Hekaton, a user simply declares a table memory optimized. I will update pretty soon .. Hang on 🙂

Here we go Microsoft has introduced SQL Server 2012 to the world and it’s time for IT professionals to start to come to speed on what’s new in this highly anticipated version of SQL Server.

1. AlwaysOn Availability Groups — This feature takes database mirroring to a whole new level. With AlwaysOn, users will be able to fail over multiple databases in groups instead of individually. Also, secondary copies will be readable, and can be used for database backups. The big win is that your DR environment no longer needs to sit idle.

2. Windows Server Core Support — If you don’t know what Windows Server Core is, you may want to come up to speed before Windows 8 (MS is making a push back to the command line for server products). Core is the GUI-less version of Windows that uses DOS and PowerShell for user interaction. It has a much lower footprint (50% less memory and disk space utilization), requires fewer patches, and is more secure than the full install. Starting with SQL 2012, it is supported for SQL Server.

3. Columnstore Indexes — This a cool new feature that is completely unique to SQL Server. They are special type of read-only index designed to be use with Data Warehouse queries. Basically, data is grouped and stored in a flat, compressed column index, greatly reducing I/O and memory utilization on large queries.

4. User-Defined Server Roles — DBAs have always had the ability to create custom database role, but never server wide. For example, if the DBA wanted to give a development team read/write access to every database on a shared server, traditionally the only ways to do it were either manually, or using undocumented procedures. Neither of which were good solutions. Now, the DBA can create a role, which has read/write access on every DB on the server, or any other custom server wide role.

5. Enhanced Auditing Features — Audit is now available in all editions of SQL Server. Additionally, users can define custom audit specifications to write custom events into the audit log. New filtering features give greater flexibility in choosing which events to write to the log.

6. BI Semantic Model — This is replacing the Analysis Services Unified Dimensional Model (or cubes most people referred to them). It’s a hybrid model that allows one data model will support all BI experiences in SQL Server. Additionally, this will allow for some really neat text infographics

7. Sequence Objects — For those folks who have worked with Oracle, this has been a long requested feature. A sequence is just an object that is a counter — a good example of it’s use would be to increment values in a table, based a trigger. SQL has always had similar functionality with identity columns, but now this is a discrete object.

8. Enhanced PowerShell Support — Windows and SQL Server admins should definitely start brushing up on their PowerShell scripting skills. Microsoft is driving a lot of development effort into instrumenting all of their server-based products with PowerShell. SQL 2008 gave DBAs some exposure to it, but there are many more in cmdlets in SQL 2012.

9. Distributed Replay — Once again this is answer to a feature that Oracle released (Real Application Testing). However, and in my opinion where the real value proposition of SQL Server is, in Oracle it is a (very expensive) cost option to Enterprise Edition. With SQL, when you buy your licenses for Enterprise Edition, you get everything. Distributed replay allows you to capture a workload on a production server, and replay it on another machine. This way changes in underlying schemas, support packs, or hardware changes can be tested under production conditions.

10. PowerView — You may have heard of this under the name “Project Crescent” it is a fairly powerful self-service BI toolkit that allows users to create mash ups of BI reports from all over the Enterprise.

11. SQL Azure Enhancements — These don’t really go directly with the release of SQL 2012, but Microsoft is making some key enhancements to SQL Azure. Reporting Services for Azure will be available, along with backup to the Windows Azure data store, which is a huge enhancement. The maximum size of an Azure database is now up to 150G. Also Azure data sync allows a better hybrid model of cloud and on-premise solutions

12. Big Data Support — I saved the biggest for last, introduced at the PASS (Professional Association for SQL Server) conference last year, Microsoft announced a partnership with Hadoop provider Cloudera. One part of this involves MS releasing a ODBC driver for SQL Server that will run on a Linux platform. Additionally, Microsoft is building connectors for Hadoop, which is an extremely popular NoSQL platform. With this announcement, Microsoft has made a clear move into this very rapidly growing space.

🙂 🙂 🙂  Send feedback

Features of SQL Server 2012

Microsoft has introduced SQL Server 2012 to the world and it’s time for IT professionals to start to come to speed on what’s new in this highly anticipated version of SQL Server.

1. AlwaysOn Availability Groups — This feature takes database mirroring to a whole new level. With AlwaysOn, users will be able to fail over multiple databases in groups instead of individually. Also, secondary copies will be readable, and can be used for database backups. The big win is that your DR environment no longer needs to sit idle. see SQL Server Multi-Subnet Clustering.

Replication supports the following features on Availability groups:

· A publication database can be part of an availability group. The publisher instances must share a common distributor. Transaction, merge, and snapshot replication are supported.

In an AlwaysOn Availability Group an AlwaysOn secondary cannot be a publisher. Republishing is not supported when replication is combined with AlwaysOn.

Peer-To-Peer (P2P), bi-directional, reciprocal transactional publications, and Oracle Publishing are not supported.

· A database that is enabled for Change Data Capture (CDC) can be part of an availability group.

· A database enabled for Change Tracking (CT) can be part of an availability group.

Four new stored procedures provide replication support for AlwaysOn.

· sp_redirect_publisher (Transact-SQL)

· sp_get_redirected_publisher (Transact-SQL)

· sp_validate_redirected_publisher (Transact-SQL)

· sp_validate_replica_hosts_as_publishers (Transact-SQL)

For more info replication with AlwaysOn, see Configure Replication for AlwaysOn Availability Groups (SQL Server), Maintaining an AlwaysOn Publication Database (SQL Server), and Replication, Change Tracking, Change Data Capture, and AlwaysOn Availability Groups (SQL Server).

2. Windows Server Core Support — If you don’t know what Windows Server Core is, you may want to come up to speed before Windows 8 (MS is making a push back to the command line for server products). Core is the GUI-less version of Windows that uses DOS and PowerShell for user interaction. It has a much lower footprint (50% less memory and disk space utilization), requires fewer patches, and is more secure than the full install. Starting with SQL 2012, it is supported for SQL Server.

3. Columnstore Indexes — This a cool new feature that is completely unique to SQL Server. They are special type of read-only index designed to be use with Data Warehouse queries. Basically, data is grouped and stored in a flat, compressed column index, greatly reducing I/O and memory utilization on large queries.

4. User-Defined Server Roles — DBAs have always had the ability to create custom database role, but never server wide. For example, if the DBA wanted to give a development team read/write access to every database on a shared server, traditionally the only ways to do it were either manually, or using undocumented procedures. Neither of which were good solutions. Now, the DBA can create a role, which has read/write access on every DB on the server, or any other custom server wide role.

5. Enhanced Auditing Features — Audit is now available in all editions of SQL Server. Additionally, users can define custom audit specifications to write custom events into the audit log. New filtering features give greater flexibility in choosing which events to write to the log.

6. BI Semantic Model — This is replacing the Analysis Services Unified Dimensional Model (or cubes most people referred to them). It’s a hybrid model that allows one data model will support all BI experiences in SQL Server. Additionally, this will allow for some really neat text infographics

7. Sequence Objects — For those folks who have worked with Oracle, this has been a long requested feature. A sequence is just an object that is a counter — a good example of it’s use would be to increment values in a table, based a trigger. SQL has always had similar functionality with identity columns, but now this is a discrete object.

8. Enhanced PowerShell Support — Windows and SQL Server admins should definitely start brushing up on their PowerShell scripting skills. Microsoft is driving a lot of development effort into instrumenting all of their server-based products with PowerShell. SQL 2008 gave DBAs some exposure to it, but there are many more in cmdlets in SQL 2012.

9. Distributed Replay — Once again this is answer to a feature that Oracle released (Real Application Testing). However, and in my opinion where the real value proposition of SQL Server is, in Oracle it is a (very expensive) cost option to Enterprise Edition. With SQL, when you buy your licenses for Enterprise Edition, you get everything. Distributed replay allows you to capture a workload on a production server, and replay it on another machine. This way changes in underlying schemas, support packs, or hardware changes can be tested under production conditions.

Data quality is not defined in absolute terms. It depends upon whether data is appropriate for the purpose for which it is intended. DQS identifies potentially incorrect data, and provides you with an assessment of the likelihood that the data is in fact incorrect. DQS provides you with a semantic understanding of the data so you can decide its appropriateness. DQS enables you to resolve issues involving incompleteness, lack of conformity, inconsistency, inaccuracy, invalidity, and data duplication.

DQS provides the following features to resolve data quality issues.

· Data Cleansing: the modification, removal, or enrichment of data that is incorrect or incomplete, using both computer-assisted and interactive processes, see Data Cleansing.

· Matching: the identification of semantic duplicates in a rules-based process that enables you to determine what constitutes a match and perform de-duplication, see Data Matching.

· Reference Data Services: verification of the quality of your data using the services of a reference data provider. You can use reference data services from Windows Azure Marketplace DataMarket to easily cleanse, validate, match, and enrich data, see Reference Data Services in DQS.

· Profiling: the analysis of a data source to provide insight into the quality of the data at every stage in the knowledge discovery, domain management, matching, and data cleansing processes. Profiling is a powerful tool in a DQS data quality solution. You can create a data quality solution in which profiling is just as important as knowledge management, matching, or data cleansing, see Data Profiling and Notifications in DQS.

· Monitoring: the tracking and determination of the state of data quality activities. Monitoring enables you to verify that your data quality solution is doing what it was designed to do, see DQS Administration.

· Knowledge Base: Data Quality Services is a knowledge-driven solution that analyzes data based upon knowledge that you build with DQS. This enables you to create data quality processes that continually enhances the knowledge about your data and in so doing, continually improves the quality of your data.

10. PowerView — You may have heard of this under the name “Project Crescent” it is a fairly powerful self-service BI toolkit that allows users to create mash ups of BI reports from all over the Enterprise.

11. SQL Azure Enhancements — These don’t really go directly with the release of SQL 2012, but Microsoft is making some key enhancements to SQL Azure. Reporting Services for Azure will be available, along with backup to the Windows Azure data store, which is a huge enhancement. The maximum size of an Azure database is now up to 150G. Also Azure data sync allows a better hybrid model of cloud and on-premise solutions

12. Big Data Support — I saved the biggest for last, introduced at the PASS (Professional Association for SQL Server) conference last year, Microsoft announced a partnership with Hadoop provider Cloudera. One part of this involves MS releasing a ODBC driver for SQL Server that will run on a Linux platform. Additionally, Microsoft is building connectors for Hadoop, which is an extremely popular NoSQL platform. With this announcement, Microsoft has made a clear move into this very rapidly growing space.

SQL 2012 is a big step forward for Microsoft -:) – the company is positioning itself to be a leader in availability and in the growing area of big data. As a database professional, I look forward to using SQL 2012.

SQL Server Install:

· Server Core Installation: Starting with SQL Server 2012, we can install SQL Server on Windows Server 2008 R2 Server Core SP1, see Install SQL Server 2012 on Server Core.

· SQL Server Data Tools (Formerly called Business Intelligence Development Studio): Starting with SQL Server 2012, you can install SQL Server Data Tools (SSDT) which provides an IDE for building solutions for the Business Intelligence components: Analysis Services, Reporting Services, and Integration Services.

SSDT also includes “Database Projects”, which provides an integrated environment for database developers to carry out all their database design work for any SQL Server platform (both on and off premise) within Visual Studio. Database developers can use the enhanced Server Object Explorer in Visual Studio to easily create or edit database objects and data, or execute queries.

· SQL Server multi-subnet clustering: You can now configure a SQL Server failover cluster using clustered nodes on different subnets, see SQL Server Multi-Subnet Clustering.

· SMB file share is a supported storage option: System databases (Master, Model, MSDB, and TempDB), and Database Engine user databases can be installed on a file share on an SMB file server. This applies to both SQL Server stand-alone and SQL Server failover cluster installations, see Install SQL Server with SMB fileshare as a storage option.

🙂 🙂

DBA work plan:

Daily tasks:
* Check for successful backup completion, including tape archives if using the “disk then tape” backup methodology.
* Confirm SQL Server Agent jobs completed successfully.
* Check free disk space on all disks, including system drives and SQL Server data, log, tempdb, and backup disks.
* Check the free space of each database’s data and transaction log files and expand if necessary to avoid autogrow operations.
* Check SQL Server errors logs and Windows event logs.
* Confirm DBCC checks executed without error by opening and inspecting the appropriate log files. Depending on the DBCC check frequency, this may be a weekly task.
* Check site-specific tasks as appropriate, such as the success of archive batch jobs.
* Check technology-specific tasks as appropriate, such as log shipping or database mirroring status/health.
* Throughout the day, monitor long-running queries and general performance of critical servers using a dashboard of key Performance Monitor counters.

Weekly tasks:
* Collate and update Performance Monitor log information for baseline analysis purposes, looking for emerging trends among counter values. This information will feed into the monthly capacity-planning task.
* Review recent wait statistics and include them alongside the Performance Monitor counter information in the performance baseline.
* Execute index and statistics maintenance jobs (during periods of low activity) as appropriate. For systems with large enough maintenance windows, this may be a simple rebuild of all indexes (while being aware of the impact on log shipping/ database mirroring) or a more targeted approach that selects the appropriate
technique (reorganize/rebuild) based on the fragmentation level.
* Record disk usage trends and note them for the monthly capacity-planning exercise.
* Review server configuration for unauthorized configuration changes. Policybased management is purpose built for this task.

Monthly tasks:
* Review and update documentation and scripts as appropriate, ensuring their accuracy and suitability for use in disaster-recovery situations.
* Review and plan the implementation of any service packs and/or hotfixes as appropriate.
* Conduct capacity planning using the inputs from the weekly baseline-analysis and disk-usage tasks. In addition to using this as a chance to identify upcoming budgetary requirements, this task may also serve as an opportunity to consolidate
databases and/or instances for a better performance/resource usage balance.
* Conduct “fire drills” to practice recovering from various failure conditions. Ideally these drills are random and unannounced and involve simulated corruption (preferably not on production databases!) to ensure all staff are capable of
recovering from a wide variety of possible failure conditions. The more these events are simulated and practiced, the quicker the recovery in the event of a real disaster.

🙂 🙂 🙂  Send feedback

Version and Edition Upgrades to 2014

Pre-release information describes new features or changes to existing features in Microsoft SQL Server 2014. You can upgrade from SQL Server 2008, and SQL Server 2008 R2, and SQL Server 2012. This topic lists the supported upgrade paths from these SQL Server versions, and the supported edition upgrades for SQL Server 2014.

Uppgrade Checklist ?
  • Before upgrading from one edition of SQL Server 2014 to another, verify that the functionality you are currently using is supported in the edition to which you are moving.
  • Before upgrading SQL Server, enable Windows Authentication for SQL Server Agent and verify the default configuration: that the SQL Server Agent service account is a member of the SQL Server sysadmin group.
  • To upgrade to SQL Server 2014, you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server 2014.
  • Upgrade will be blocked if there is a pending restart.
  • Upgrade will be blocked if the Windows Installer service is not running.
  • Cross-version instances of SQL Server 2014 are not supported. Version numbers of the Database Engine, Analysis Services, and Reporting Services components must be the same in an instance of SQL Server 2014.
  • Cross-platform upgrade is not supported. You cannot upgrade a 32-bit instance of SQL Server to native 64-bit using SQL Server Setup. However, you can back up or detach databases from a 32-bit instance of SQL Server, and then restore or attach them to a new instance of SQL Server (64-bit) if the databases are not published in replication. You must re-create any logins and other user objects in master, msdb, and model system databases.
  • You cannot add new features during the upgrade of your existing instance of SQL Server. After you upgrade an instance of SQL Server to SQL Server 2014, you can add features by using the SQL Server 2014 Setup. For more information, see Add Features to an Instance of SQL Server 2014 (Setup).
  • Failover Clusters are not supported in WOW mode.
  • Upgrade from an Evaluation edition of a previous SQL Server version is not supported.

SQL Server 2014 supports upgrade from the following versions of SQL Server:

  • SQL Server 2008 SP3 or later
  • SQL Server 2008 R2 SP2 or later
  • SQL Server 2012 SP1 or later

The table below lists the supported upgrade scenarios from earlier versions of SQL Server to SQL Server 2014.

Upgrade from Supported upgrade path
SQL Server 2008 SP3 Enterprise SQL Server 2014 EnterpriseSQL Server 2014 Business Intelligence
SQL Server 2008 SP3 Developer SQL Server 2014 Developer
SQL Server 2008 SP3 Standard SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 Standard
SQL Server 2008 SP3 Small Business SQL Server 2014 Standard
SQL Server 2008 SP3 Web SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 Web
SQL Server 2008 SP3 Workgroup SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 Web
SQL Server 2008 SP3 Express,SQL Server 2008 SP3 Express with Tools, andSQL Server 2008 SP3 Express with Advanced Services SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 WebSQL Server 2014 Express
SQL Server 2008 R2 SP2 Datacenter SQL Server 2014 EnterpriseSQL Server 2014 Business Intelligence
SQL Server 2008 R2 SP2 Enterprise SQL Server 2014 EnterpriseSQL Server 2014 Business Intelligence
SQL Server 2008 R2 SP2 Developer SQL Server 2014 Developer
SQL Server 2008 R2 SP2 Small Business SQL Server 2014 Standard
SQL Server 2008 R2 SP2 Standard SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 Standard
SQL Server 2008 R2 SP2 Web SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 Web
SQL Server 2008 R2 SP2 Workgroup SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 Web
SQL Server 2008 R2 SP2 Express,SQL Server 2008 R2 SP2 Express with Tools, andSQL Server 2008 R2 SP2 Express with Advanced Services SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 WebSQL Server 2014 Express
SQL Server 2012 SP1 Enterprise SQL Server 2014 EnterpriseSQL Server 2014 Business Intelligence
SQL Server 2012 SP1 Developer SQL Server 2014 Developer
SQL Server 2012 SP1 Standard SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 Standard
SQL Server 2012 SP1 Web SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 Web
SQL Server 2012 SP1 Express,SQL Server 2012 SP1 Express with Tools, andSQL Server 2012 SP1 Express Management Studio, andSQL Server 2012 SP1 Express with Advanced Services SQL Server 2014 EnterpriseSQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 WebSQL Server 2014 Express
SQL Server 2012 SP1 Business Intelligence SQL Server 2014 EnterpriseSQL Server 2014 Business Intelligence

Table lists the supported edition upgrade scenarios in SQL Server 2014.

For step-by-step instructions on how to perform an edition upgrade, see more click here to go Upgrade to a Different Edition of SQL Server 2014 (Setup).

Upgrade From Upgrade To
SQL Server 2014 Enterprise (Server+CAL and Core) 2 SQL Server 2014 Business Intelligence
SQL Server 2014 Business Intelligence SQL Server 2014 Enterprise (Server+CAL or Core License)
SQL Server 2014 Evaluation Enterprise 2 SQL Server 2014 Enterprise (Server+CAL or Core License)SQL Server 2014 Business IntelligenceSQL Server 2014 StandardSQL Server 2014 DeveloperSQL Server 2014 WebUpgrading from Evaluation Enterprise (a free edition) to any of the paid editions is supported for stand-alone installations, but is not supported for clustered installations.
SQL Server 2014 Standard 2 SQL Server 2014 Business IntelligenceSQL Server 2014 Enterprise (Server+CAL or Core License)SQL Server 2014 Developer
SQL Server 2014 Developer 2 SQL Server 2014 Enterprise (Server+CAL or Core License)SQL Server 2014 Business IntelligenceSQL Server 2014 Standard
SQL Server 2014 Web SQL Server 2014 Enterprise (Server+CAL or Core License)SQL Server 2014 Business IntelligenceSQL Server 2014 DeveloperSQL Server 2014 Standard
SQL Server 2014 Express 1 SQL Server 2014 Enterprise (Server+CAL or Core License)SQL Server 2014 Business IntelligenceSQL Server 2014 DeveloperSQL Server 2014 StandardSQL Server 2014 Web

Additionally you can also perform an edition upgrade between SQL Server 2014 Enterprise (Server+CAL license) and SQL Server 2014 Enterprise (Core License):

Edition Upgrade From Edition Upgrade To
SQL Server 2014 Enterprise (Server+CAL License) SQL Server 2014 Enterprise (Core License)
SQL Server 2014 Enterprise (Core License) SQL Server 2014 Enterprise (Server+CAL License)

1 Also applies to SQL Server 2014 Express with Tools and SQL Server 2014 Express with Advanced Services.

2 Changing the edition of a SQL Server 2014 failover cluster is limited. The following scenarios are not supported for SQL Server 2014 failover clusters:

  • SQL Server 2014 Enterprise to SQL Server 2014 Developer, Standard, or Enterprise Evaluation.
  • SQL Server 2014 Developer to SQL Server 2014 Standard or Enterprise Evaluation.
  • SQL Server 2014 Standard to SQL Server 2014 Enterprise Evaluation.
  • SQL Server 2014 Enterprise Evaluation to SQL Server 2014 Standard.

🙂                      🙂                       🙂      Send feedback

SCOM – New SQL Management Pack and Summary Dashboard Released

Microsoft has just released a new management pack update for monitoring SQL. We first got a preview of this management pack Workloads: Managing Windows, IIS & SQL Technologies  it’s release – mainly because of the new SQL Server 2012 Summary dashboard that comes bundled with it.

Here’s a screenshot of what the new dashboard looks like (keep in mind that this dashboard will only run on SQL 2012 databases):

SQL DashboardThe new MP comes with some additional monitors, rules and all round improvements – here’s a list of them taken directly from the MP guide:

  • Collect DB Active Requests count
  • Collect DB Active Sessions count
  • Collect DB Active Transactions count
  • Collect DB Engine Thread count
  • Thread Count monitor
  • Transaction Log Free Space (%) monitor
  • Transaction Log Free Space (%) collection
  • Collect DB Engine CPU Utilization (%)
  • CPU Utilization (%) monitor for DB engine
  • Buffer Cache Hit Ratio monitor
  • Collect DB Engine Page Life Expectancy (s)
  • Page Life Expectancy monitor
  • Collect DB Disk Read Latency (ms)
  • Collect DB Disk Write Latency (ms)
  • Disk Read Latency monitor
  • Disk Write Latency monitor
  • Collect DB Transactions per second count
  • Collect DB Engine Average Wait Time (ms)
  • Average Wait Time monitor
  • Collect DB Engine Stolen Server Memory (MB)
  • Stolen Server Memory monitor
  • Collect DB Allocated Free Space (MB)
  • Collect DB Used Space (MB)
  • Collect DB Disk Free Space (MB)
  • SQL Re-Compilation monitor
  • SPN monitor improved
  • Support for special symbols in DB names.
  • Improved AlwaysOn seed discovery
  • Run As configuration changes to support Low privilege for SQL Server 2012 Cluster
  • Improved performance of AlwaysOn discovery
  • Custom User Policy Discovery and Monitoring performance optimization
  • Hid AG health object from Diagram view.

You can download the MP and its associated guide from here: Click Me

As always, make sure you read the guide from front to back and test the MP out first before deploying 2 production.

🙂                      🙂                       🙂      Send feedback

Right now i am working on MDS & MQS 2012

SQL Server Master Data Services

Use the following resources to help understand, install, configure, manage, and troubleshoot Master Data Services (MDS) in SQL 2012.

 What is Master Data Services

Troubleshooting Master Data Services

Resources for MDS Deployment

Case Studies

More info visit

🙂                      🙂                       🙂      Send feedback

Microsoft SQL Server 2014 is here now …

SQL Server 2014 CTP1 builds on the mission-critical capabilities delivered in the prior release by providing breakthrough performance, availability and manageability for your mission critical applications. SQL Server 2014 delivers new in-memory capabilities built into the core database for OLTP and data warehousing, which complement our existing in-memory data warehousing and BI capabilities for the most comprehensive in-memory database solution.

Learn more about SQL Server 2014

And for those of you interested in downloading some of the products and trying them, here are some resources to help you:

  • Windows Server 2012 R2 Preview download
  • System Center 2012 R2 Preview download
  • SQL Server 2014 Community Technology Preview 1 (CTP1) download
  • Windows 8.1 Enterprise Preview download

Welcome any comments.

🙂                      🙂                       🙂      Send feedback

SQL Server 2012 Upgrade Technical Guide is a detailed resource that’s also available online for free. Each chapter was carefully crafted and explained in detail. Here is a quick list of the chapters included in the whitepaper. Downloading the guide, from below

Here’s the list:

1: Upgrade Planning and Deployment

2: Management Tools

3: Relational Databases

4: High Availability

5: Database Security

6: Full-Text Search

7: Service Broker

8: SQL Server Express

9: SQL Server Data Tools

10: Transact-SQL Queries

11: Spatial Data

12: XML and XQuery

13: CLR Chapter

14: SQL Server Management Objects

15: Business Intelligence Tools

16: Analysis Services

17: Integration Services

18: Reporting Services

19: Data Mining

 SQL Server 2012: Upgrade Planning Checklist DOWLOAD

Download SQL Server 2012 Upgrade Technical Guide

🙂                      🙂                       🙂      Send feedback

Microsoft SQL Server Migration Assistant (SSMA) 5.2 is Now Available

Automating Database Migration to SQL Server 2012

SQL Server Migration Assistant (SSMA) v5.2 is now available. SSMA simplifies database migration process from Oracle/Sybase/MySQL and Microsoft Access to SQL Server and SQL Azure. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing to reduce cost and reduce risk of your database migration project.

The new version of SSMA – SSMA 5.2 provides the following major enhancements:

  • Support conversion of Oracle %ROWTYPE parameters with NULL default
  • Support conversion of Sybase’s Rollback Trigger
  • Better user credential security to support Microsoft Access Linked Tables

Download SQL Server Migration Assistant (SSMA) v.5.2

Launch the download of the SSMA for Oracle.

Launch the download of the SSMA for Sybase.

Launch the download of the SSMA for MySQL.

Launch the download of the SSMA for Access.

🙂                      🙂                       🙂      Send feedback

Virtual labs are simple, with no complex setup or installation required.

You get a downloadable manual and a 90-minute block of time for each module. You can sign up for additional 90-minute blocks at any time.

SQL Server 2008 R2 Virtual Labs

🙂                      🙂                       🙂      Send feedback

SQL Server Technologies:-

SQL Server Resources:-

Documentation

SQL Server MVP Blogs

Other SQL Server Blogs

🙂                      🙂                       🙂      Send feedback

The common SQL DBA mistakes?

SQL DBA must follow set of best practices to ensure smooth and highly optimized databases availability. Here are few common mistakes that I have identified and would recommend to fix if you have encountered or seeing anything similar.

1. Not preparing and validating a reliable backup and recovery policy with backup files retention period for databases as per agreed data loss and application downtime it may cause while recovering databases.

Very often some DBA’s heavily on adding a database maintenance plan only for regular backups and considering it done. I believe it’s not enough; a DBA must frequently check how long it takes to recover databases and should verify backup files for point in time recovery. Also, depending on database size it may take longer than expected time to do database recovery. Therefore, taking backups may not solve your requirements and it’s advised to use standby server with log shipping or database mirroring for quick database DR solutions.

2. Not knowing server hardware limits and utilization. It’s must to check System resource utilization & identifying bottlenecks on regular intervals for DISKIO, memory, CPU, Locks & Blocking etc counters. This information can give insight about how much server hardware resources are utilized/ available for current and near future workload generated by application(s). This information can help stabilizing the performance for a longer period, as well as knowing its limitations.

3. Not verifying SQL Server security, and not applying latest service pack/ version. It’s highly recommended to patch and apply bug fixes as soon as possible. An obsolete SQL server build/version is not recommended to keep running for production servers. Do check that you have carefully selected sysadmin role members and removed excessive permission from normal database users. It’s a general practice to enable only SQL option/settings that are required like – xp_cmdshell, CLR etc and make use of encryption & auditing to safeguard critical data.

4. Not defragging indexes or running Database consistency checks. Also not running regular maintenance activities like update stats on production databases. Or in some cases executing maintenance and other high resource consuming activities during production working hours.

5. Not checking how much free space is available in data or log files and shrinking databases again and again. Or setting ‘Auto Shrink’ database option to true is equivalent harmful.

6. Creating databases for Dev, Staging, UAT, Test, QA etc on Production SQL Server or Instance. This majorly causes manual/human mistakes by deleting/modifying objects or incorrectly assigning permissions.

7. Proactive Monitoring: Not setting SQL Alerts with email notification for Severity errors from 17 to 25; Disk free space check, CPU utilization, SQL/Agent/SSRS/SSAS services restart etc. It’s highly advisable to set up automated alerts on SQL server for critical events. So that you are fully aware and feel secure that all events are reaching to you/team even though not sitting in front of computer screen. Going forward you may use Policy based management to capture events and streamlining various SQL instances in your environment.

8. Not using/applying High availability techniques (clustering, Mirroring, Log shipping) for critical databases. A DBA must identify business requirements and apply high availability techniques as per already defined SLA targets. It ensures timely availability of databases for applications in case of failure.

9. Running SQL profiler on production with no filters and end time. This is among most frequently happening mistakes. A DBA must understand that running profiler with no filters will capture all events and T-SQL queries thus generating extra workload on production. Its highly advised to use profiler with caution.

10. Setting database recovery option to ‘Full’ and never taking transaction log backups. I have seen cases where transaction log file size have increased 100 times to actual data due to backup negligence. Make sure you select database recovery model according to requirements and use backup policy accordingly. Also, carefully watch your transaction log backup jobs in logs hipping scenario to avoid large size database transaction log files.

🙂              🙂                🙂

SQL Server 2012 cause and Resolution of Database Engine Errors

MSSQLSERVER_-2

MSSQLSERVER_-1

MSSQLSERVER_2

MSSQLSERVER_53

MSSQLSERVER_102

MSSQLSERVER_107

MSSQLSERVER_125

MSSQLSERVER_137

MSSQLSERVER_207

MSSQLSERVER_208

MSSQLSERVER_233

MSSQLSERVER_360

MSSQLSERVER_511

MSSQLSERVER_601

MSSQLSERVER_605

MSSQLSERVER_611

MSSQLSERVER_617

MSSQLSERVER_701

MSSQLSERVER_802

MSSQLSERVER_823

MSSQLSERVER_824

MSSQLSERVER_825

MSSQLSERVER_833

MSSQLSERVER_844

MSSQLSERVER_845

MSSQLSERVER_846

MSSQLSERVER_847

MSSQLSERVER_905

MSSQLSERVER_916

MSSQLSERVER_926

MSSQLSERVER_945

MSSQLSERVER_948

MSSQLSERVER_1101

MSSQLSERVER_1105

MSSQLSERVER_1203

MSSQLSERVER_1204

MSSQLSERVER_1205

MSSQLSERVER_1222

MSSQLSERVER_1401

MSSQLSERVER_1406

MSSQLSERVER_1418

MSSQLSERVER_1457

MSSQLSERVER_1458

MSSQLSERVER_1461

MSSQLSERVER_1462

MSSQLSERVER_1505

MSSQLSERVER_1793

MSSQLSERVER_1803

MSSQLSERVER_1807

MSSQLSERVER_1904

MSSQLSERVER_2020

MSSQLSERVER_2501

MSSQLSERVER_2508

MSSQLSERVER_2511

MSSQLSERVER_2512

MSSQLSERVER_2515

MSSQLSERVER_2516

MSSQLSERVER_2518

MSSQLSERVER_2519

MSSQLSERVER_2522

MSSQLSERVER_2527

MSSQLSERVER_2530

MSSQLSERVER_2533

MSSQLSERVER_2534

MSSQLSERVER_2536

MSSQLSERVER_2537

MSSQLSERVER_2538

MSSQLSERVER_2539

MSSQLSERVER_2540

MSSQLSERVER_2546

MSSQLSERVER_2570

MSSQLSERVER_2574

MSSQLSERVER_2575

MSSQLSERVER_2576

MSSQLSERVER_2577

MSSQLSERVER_2579

MSSQLSERVER_2592

MSSQLSERVER_2593

MSSQLSERVER_2596

MSSQLSERVER_2814

MSSQLSERVER_3151

MSSQLSERVER_3156

MSSQLSERVER_3159

MSSQLSERVER_3168

MSSQLSERVER_3169

MSSQLSERVER_3176

MSSQLSERVER_3181

MSSQLSERVER_3260

MSSQLSERVER_3271

MSSQLSERVER_3313

MSSQLSERVER_3314

MSSQLSERVER_3413

MSSQLSERVER_3414

MSSQLSERVER_3417

MSSQLSERVER_3431

MSSQLSERVER_3437

MSSQLSERVER_3452

MSSQLSERVER_3456

MSSQLSERVER_3619

MSSQLSERVER_3937

MSSQLSERVER_3961

MSSQLSERVER_4064

MSSQLSERVER_4104

MSSQLSERVER_4186

MSSQLSERVER_4846

MSSQLSERVER_5228

MSSQLSERVER_5229

MSSQLSERVER_5231

MSSQLSERVER_5233

MSSQLSERVER_5235

MSSQLSERVER_5237

MSSQLSERVER_5242

MSSQLSERVER_5243

MSSQLSERVER_5245

MSSQLSERVER_5250

MSSQLSERVER_5256

MSSQLSERVER_5512

MSSQLSERVER_5515

MSSQLSERVER_5554

MSSQLSERVER_7308

MSSQLSERVER_7711

MSSQLSERVER_7901

MSSQLSERVER_7903

MSSQLSERVER_7904

MSSQLSERVER_7905

MSSQLSERVER_7906

MSSQLSERVER_7907

MSSQLSERVER_7908

MSSQLSERVER_7910

MSSQLSERVER_7911

MSSQLSERVER_7912

MSSQLSERVER_7913

MSSQLSERVER_7914

MSSQLSERVER_7915

MSSQLSERVER_7916

MSSQLSERVER_7920

MSSQLSERVER_7923

MSSQLSERVER_7931

MSSQLSERVER_7932

MSSQLSERVER_7933

MSSQLSERVER_7934

MSSQLSERVER_7935

MSSQLSERVER_7936

MSSQLSERVER_7937

MSSQLSERVER_7984

MSSQLSERVER_7986

MSSQLSERVER_7987

MSSQLSERVER_7988

MSSQLSERVER_7995

MSSQLSERVER_8443

MSSQLSERVER_8525

MSSQLSERVER_8601

MSSQLSERVER_8621

MSSQLSERVER_8630

MSSQLSERVER_8642

MSSQLSERVER_8645

MSSQLSERVER_8649

MSSQLSERVER_8651

MSSQLSERVER_8680

MSSQLSERVER_8689

MSSQLSERVER_8710

MSSQLSERVER_8712

MSSQLSERVER_8966

MSSQLSERVER_8974

MSSQLSERVER_8992

MSSQLSERVER_8993

MSSQLSERVER_8994

MSSQLSERVER_8996

MSSQLSERVER_9001

MSSQLSERVER_9002

MSSQLSERVER_9003

MSSQLSERVER_9004

MSSQLSERVER_9524

MSSQLSERVER_9532

MSSQLSERVER_9692

MSSQLSERVER_9790

MSSQLSERVER_9955

MSSQLSERVER_10001

MSSQLSERVER_10003

MSSQLSERVER_10060

MSSQLSERVER_10061

MSSQLSERVER_10502

MSSQLSERVER_10507

MSSQLSERVER_10509

MSSQLSERVER_10519

MSSQLSERVER_10520

MSSQLSERVER_10521

MSSQLSERVER_10531

MSSQLSERVER_10532

MSSQLSERVER_10533

MSSQLSERVER_10534

MSSQLSERVER_10535

MSSQLSERVER_10536

MSSQLSERVER_10537

MSSQLSERVER_10538

MSSQLSERVER_10539

MSSQLSERVER_10737

MSSQLSERVER_11001

MSSQLSERVER_11409

MSSQLSERVER_14265

MSSQLSERVER_14420

MSSQLSERVER_14421

MSSQLSERVER_15404

MSSQLSERVER_15599

MSSQLSERVER_15661

MSSQLSERVER_17053

MSSQLSERVER_17065

MSSQLSERVER_17066

MSSQLSERVER_17067

MSSQLSERVER_17128

MSSQLSERVER_17130

MSSQLSERVER_17132

MSSQLSERVER_17142

MSSQLSERVER_17147

MSSQLSERVER_17148

MSSQLSERVER_17194

MSSQLSERVER_17204

MSSQLSERVER_17300

MSSQLSERVER_17660

MSSQLSERVER_17676

MSSQLSERVER_17803

MSSQLSERVER_17809

MSSQLSERVER_17832

MSSQLSERVER_17883

MSSQLSERVER_17884

MSSQLSERVER_17887

MSSQLSERVER_18264

MSSQLSERVER_18452

MSSQLSERVER_18456

MSSQLSERVER_18752

MSSQLSERVER_20557

MSSQLSERVER_20572

MSSQLSERVER_20574

MSSQLSERVER_21862

MSSQLSERVER_21871

MSSQLSERVER_21879

MSSQLSERVER_21892

MSSQLSERVER_21893

MSSQLSERVER_21889

MSSQLSERVER_21898

MSSQLSERVER_21899

MSSQLSERVER_26013

MSSQLSERVER_26014

MSSQLSERVER_30053

MSSQLSERVER_30089

MSSQLSERVER_32040

MSSQLSERVER_32042

MSSQLSERVER_32043

MSSQLSERVER_32044

MSSQLSERVER_33027

MSSQLSERVER_33028

MSSQLSERVER_33081

MSSQLSERVER_33085

MSSQLSERVER_33128

MSSQLSERVER_33129

MSSQLSERVER_41030

Errors and Events Reference (Database Engine)

The following table links to and describes these resources.

Resource

Description

SQL Server Community This site has links to newsgroups and forums monitored by the SQL Server community. It also lists community information sources, such as blogs and Web sites. The SQL Server community is very helpful in answering questions, although an answer cannot be guaranteed.
SQL Server Developer Center Community This site focuses on the newsgroups, forums, and other community resources that are useful to SQL Server developers.
Microsoft Help and Support You can use this Web site to open a case with a Microsoft support professional.

5 thoughts on “MS SQL Server

  1. I’m extremely pleased to uncoover this site. I wanted to thank you foor ones time due to this wonderful read!!
    I definitely enjoyed every little bit of itt and i also
    have you aved as a favorite to look at new information in your website.

  2. Very rapidly this website will be famous amid all blog viewers, due too it’s nice articles

  3. What’s up, after reading this amazing post i am as well glad to share myy knowledge here with mates.

  4. I always emailed this weblog post page to all my
    friends, as if like to read it after that my contacts will too.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s