New Changes to SQL Server 2016 Installation

SQLServerF1

With every new release of SQL Server, there are many changes that comes like new features, enhancement to existing features, etc. Important thing which DBAs look is SQL Server installation, as we need to first get the downloadable and then install the software to be able to explore the new features or play with the product and some enthusiastic users even want to find bugs and report to the product team. Over a period of time, since SQL Server 2000, there have been many changes to the way the installation of SQL Server in standalone or cluster environment. The installation wizard changes were also inspired by the newer versions of operating systems, like Windows Server 2008 lead to different experience of the installation wizards. In SQL Server 2005, install shield was used, and starting SQL Server 2008 R2, installation center has been introduced with various different options and there were major changes when it came to cluster SQL installation. In SQL Server 2005, cluster install was started from one node and automatically it used to install on both nodes using task scheduler, but there were lot of problems with that, so in SQL Server 2008, the cluster installation was changed significantly, where we install on one node and remaining nodes we perform Add node operation, this made life easier with cluster installs.

Now coming back to changes in installation wizard or steps with SQL Server 2016 are mentioned below.
– In previous versions of SQL Server, in the feature selection page, there were many options which include Database Engine services and under that there were sub options for replication, full-text, Data-quality services. Starting with SQL Server 2016, we now have a new option under database engine services, which is PolyBase Query Service for External Data. If you are wondering what is this new feature, it enables using integrated querying across Hadoop data and SQL Server data using standard T-SQL statements. When we select this feature to be installed along with database engine, there will be additional checks performed by the installer which include checking for Microsoft .NET Framework 4.0, and if Oracle Java SE RunTime Environment (JRE) version 7.51 or higher is present or not. If this are not present, then the installation will fail. Also, after the successful install you will find three new databases DWConfiguration, DWDiagnostics, and DWQueue created by default if we choose to install PolyBase Query Service for External Data.

Another change that comes with SQL Server 2016 installation is, we can now select number of tempdb files when want to create along with the SQL Server installation. Previously this option was not present and DBAs had to manually create additional data files for tempdb. Also, there is a recommendation on number of tempdb files to be created based on number of cores on the server. Primarily, there are the tow main changes, other than this there are changes to licensing agreement and feedback to be sent to Microsoft, which is now an option which we cannot opt out off.

Hope this was helpful.

This is applicable for below versions of SQL Server

Microsoft SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Benefits at Glance of Using New SQL Server 2016

SQLServerF1

Microsoft has released most awaited RTM version of SQL Server 2016 on June 1 2016. There was lot of buzz around with the release of new SQL Server 2016 and has been already downloaded by many community DBAs and developers to start testing or learning using the new features. Just like any other SQL Server version, even in new SQL Server 2016, there has been lot of new features introduced in areas like security, performance, scalability, stability, etc. Also there is support for SQL Server on linux in pipeline, which makes it much more interesting and to enter new companies which did not use windows operating system. As a DBA or developer it is very important to gets handon new features and suggest to the management how it will benefit the clients or customers or their own business with the new features. Always, test in a test environment thoroughly before deciding to move to production. Also, as like any new version, it is expected to have lot of bugs too, so it is up to you to decide whether to wait till a service pack is released or just go ahead and install it right away now. My preference is to start testing on test environment and see how application reacts to it, and if the new features are beneficial and performance has improved with the applicaion, then I prefer to go ahead with the new SQL Server 2016 on production environment.

Following are some of the important benefits of new SQL Server 2016 which we might want to keep on top of our head.
– Microosft claims Enhanced in-memory performance which provides up to 30x faster transactions, and more than 100x faster queries than disk based relational databases and real-time operational analytics.
– New security feature Always Encrypted which helps in protecting our data at rest and in motion, on-premises and in the cloud, with master keys sitting with the application, without requiring any changes to the application.
– Built-in advanced analytics– provide the scalability and performance benefits of building and running advanced analytics algorithms directly in the core SQL Server transactional database.
– Business insights through rich visualizations on mobile devices with native apps for Windows, iOS and Android
Simplify management of relational and non-relational data with ability to query both through standard T-SQL using PolyBase technology

– New features like Stretch Database technology keeps more of our historical/cold data at our fingertips by transparently stretching your warm and cold OLTP data to Microsoft Azure in a secure manner without application changes.
– Faster hybrid backups, high availability and disaster recovery scenarios to backup and restore our on-premises databases to Microsoft Azure and place your SQL Server AlwaysOn secondaries in Azure.
– Closer integration with Azure SQL Database which helps more customers comfortable to migrated to cloud with the new security features.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Pre-install Information for SQL Server 2016

SQLServerF1

Microsoft has officially released new SQL Server 2016 on June 01 2016 for public to download and install it on their development, test or production servers. It is important to test the applications thoroughly before moving to production environment, as there may be some changes required to the application to work seamlessly. If the application is vendor application, then contact the respective vendor and get approval to use new SQL Server 2016, most times, vendors releases new version of the application which works fine on new versions of SQL Server. Although, installing and using SQL Server 2016 is straight forward, but important to take care of things prior to install to ensure no hiccups later for the installation process. SQL Server 2016 has a critical pre-requisite for updated Visual Studio VC++ 2013 Runtime Libraries. To install or check if this update is required on your system, refer KB316398 for further information.

Review SQL Server 2016 system requirements – Memory Minimum requirement for Express Editions is 512 MB, All other editions: 1 GB, however recommended for Express Editions is 1 GB and for All other editions is at least 4 GB and should be increased as database size increases to ensure optimal performance. Processor speed required minimum is x64 Processor: 1.4 GHz, however recommended is 2.0 GHz or faster. Type of x64 Processor is AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support. Important point to note is SQL Server 2016 is supported on x64 processors only. It is no longer supported on x86 processors. WOW64 is not supported for SQL Server 2016. Review SQL Server release notes – check the release notes of SQL Server before installation to get all the details.
Download and install full-featured software for a 180-day trial edition or buy a licenseed edition for production environments and developer edition for development purposes. We may also choose to use express edition based on our requirement, if we are not using all features.

Make sure the account which used to RDP to the server has administrative rights on the computer to install SQL Server 2016. We will have SQL Server 2016 DVD Image or ISO file for the installation.
The Microsoft SQL Server 2016 release is available for testing purposes only and should NOT be installed and used in production environments.
Side-by-Side installation with down-level production SQL Server instances as well as in-place upgrades of down-level production SQL Server instances, is supported for SQL Server 2008 and higher.
If you have questions or concerns that come up during your testing and evaluation, we encourage you to use the MSDN forum for SQL Server 2016 to search for answers or ask new questions.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

New Details regarding SQL Server on Linux and SQL Server 2016 Released on June 1st

SQLServerF1

Microsoft has officially released SQL Server 2016 on June 1st 2016. We can download an evaluation edition from here. This trial edition expires after 180 days, after which we will need to upgrade it to a licensed edition or download free express edition if the features used are minimal. Microsoft has introduced many new features with SQL Server 2016 in different areas. Some of the popular features include, Stretch database, Always Encrypt, Data Masking, also promises of significant improvement in the performance, much closer integration with SQL Azure, temporal tables, query store, Row level security, changes to upgrade advisor, etc. Initially Microsoft has released release candidate versions RC0, RC1, RC2 and RC3, which was downloaded and tested by many users in the DBA and Developer community and by some organizations and enough feedback was provided to improve the product. There were many bugs identified with the initial RC versions on various features, which were subsequently fixed in later RC versions.

Now SQL Server 2016 official RTM version has been launch on June 1st 2016. Once you install the new SQL Server 2016 RTM version, then you will see the build number as 13.0.1601.5. Some insights from Microsoft release documentation are “SQL Server 2016 is here! It is the biggest leap forward in Microsoft’s data platform history with faster transactions and queries, deeper insights on any device, advanced analytics, new security technology, and new hybrid cloud scenarios. SQL Server 2016 delivers breakthrough mission-critical capabilities with in-memory performance and operational analytics built-in. Comprehensive security features like new Always Encrypted technology helps protect your data at rest and in motion, and a world class high availability and disaster recovery solution adds new enhancements to AlwaysOn technology.You can also gain the benefits of hyper-scale cloud with new hybrid scenarios enabled by new Stretch Database technology that lets you dynamically stretch your warm and cold transactional data to Microsoft Azure in a secured way so your data is always at hand for queries, no matter the size. In addition, SQL Server 2016 delivers a complete database platform for hybrid cloud, enabling you to easily build, deploy and manage solutions that span on-premises and cloud.”

Another exciting news from Microsoft team is the announcement of further details regarding SQL Server support on Linux Operating System. So far SQL Server was supported only on Windows environment, but not there is lot of work in progress to get SQL Server work on linux environment too, just like it works on a Windows environment. SQL Server version which works on linux has not yet been released with SQL Server 2016, instead it may be released as a sub version later or as a new SQL Server version, but looks mostly it will be a sub version of SQL Server 2016 R2 or as part of a service pack. If you want to get hands on with SQL Server 2017 linux version, then at this point all we can do is sign up for Microsoft SQL Server on Linux and wait for further updates. You can register here for Microsoft SQL Server on Linux preview. Also, there has been a video released with small demos on installing and running SQL Server on linux environment. You can watch the video here. Important thing to note is that only database engine is so far been created and tested, but other services like Integration services, Reporting services, Analysis Services are still going to take some time to get on to the linux environment.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Finding Tables Suitable for Stretch Databases in SQL Server 2016

SQLServerF1

Most of the DBAs must be familiar with SQL Server upgrade advisor, which we run during planning phase of upgrading to higher SQL Server versions inorder to identify any objects or features that will get affected during or after the instance or database upgrade. With every new release of SQL Server, some old features may be deprecated or retired and behavior of some features might change in new versions. So, running upgrade advisor during planning phase on a test server where the production database is restored, will give us good idea on what objects are going to break during or after upgrading to higher version of SQL Server. In previous releases of SQL Server, the Upgrade Advisor tool was made available only few days before the release of the new SQL Server version, but with SQL Server 2016, the upgrade advisor has been released way early giving options to test the instances or databases and then to proceed with testing on RC releases of the SQL Server. Although, we may be very familiar with using the upgrade advisors for SQL Server 2005, 2008 R2, 2012 and 2014, but there have been significant changes to SQL Server 2016 Upgrade Advisor in look and feel and its usage.

New feature which was introduced with SQL Server 2016 is Stretch Database which migrates our historical data transparently and securely to the Microsoft Azure cloud. Stretch Database provides some benefits to the users, but also has its own limitations which make it less likely to be used as of now, unless Microsoft comes up with significant improvements. Some of the benefits to decide on using SQL Server 2016 Stretch Database feature are, Provides cost-effective availability for cold data(historical data which is not accessed much, but still available to support user queries from Azure SQL database). Using this feature does not require any changes to the applications, this feature takes care of it internally and transparently. Moving cold or not frequently used data to Azure SQL database will reduce the maintenance efforts on the production data like less times required for backups, indexing statistics updates, etc. Stretch Database in a SQL Server instance requires at least one table. It then silently begins to migrate the historical data to Azure SQL Database. If we are storing historical data in a separate table, then we can migrate the entire table. If our table contains both historical and current data, then we can specify a filter predicate to select the rows which need to be moved to Azure SQL database. Also, importantly, Stretch Database ensures that no data is lost if a failure occurs during migration. There is also retry logic to handle intermittent connection issues that may occur during migration.

We can identity the tables which can be part of Stretch Database using SQL Server 2016 upgrade advisor, SQL Server 2016 upgrade advisor has different options to analyse a regular database and to analyze for Stretch Database. To get started, first download and install SQL Server 2016 upgrade advisor on a test server. Launch the SQL Server 2016 upgrade advisor and select “Scenarios” option -> choose ‘Run Stretch Database Advisor” -> Choose “Select Databases to Analyze” -> Provide SQL Instance name and make the successful connection to the SQL instance against which we want to run the analysis -> Select one or more databases from the list of databases list provided -> Run the analysis. It will take a while for the analysis to complete, after which we will be presented with a summary page of the analysis. We can save the results to HTML file or CSV file or other options as and when available.

But there are many limitations to the tables to be part of Stretch Database at this point of time. Below are some of the limitations.

– Uniqueness is not enforced for UNIQUE constraints and PRIMARY KEY constraints in the Azure SQL table that contains the migrated data.
– Insert/Delete operations are not supported and also insert is not allowed through linked servers as well.
– Views cannot be created on the stretch enabled tables. Filters on SQL Server indexes are not propagated to the remote table.
– There are many other limitations on which data types cannot be used for the tables columns, some database properties are not supported like filetables, Memory-optimized tables, etc.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

SQL Server Cumulative Updates are More Stable to Install

Microsoft releases various service packs, cumulative updates, hotfixes for SQL Server to fix any bugs or known issues. Each of these serves different purposes. For example hotfixes address specific bug or issue and released when a customer opens a case with Microsoft and issue identified as bug, then hoxfix will be released to rectify the specific issue. So, DBAs are required to only apply the hotfix if they are facing that issue. Cumulative updates contain more number of fixes which include multiple hotfixes and additional bug fixes raised by customers. Service Packs are more higher level and contain all service packs, cumulative updates released so for for that version of SQL Server.

With each release of SQL Server version, Microsoft has been making various improvements to the product and the process based on the feedback received from the customers. For example, since SQL Server 2008, Microsoft has allowed possibility of uninstalling service packs, thus providing a better and easier way of rollback in case something goes wrong after applying the patch. Now in year 2016, Microsoft has come up with approach of recommending to install latest available service pack or cumulative update and stated that both of these will be stable as the level of testing done will be same. Previously, in DBA community, there has been assumption that service packs are more stable compared to cumulative updates, as service packs contain more fixes and tested thoroughly and thought that CUs are not tested as thoroughly as SPs.

Now with the article, Microsoft has made it clear that even service packs going forward from year 2016 are stable and recommends to install them as soon as they are available, similar to how DBAs react to release of service packs. This is due to change in the way the service packs and cumulative updates are created and tested. Microsoft has made effort to update the KB articles to reflect the same. Previously, the KB articles used to have message that “This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems.”, which made many customer back down from applying the cumulative updates, but now they are updating the message with “we now recommend ongoing, proactive installation of CU’s as they become available.”

This change was welcomed by the DBA community where it makes it easier to convince the management to go ahead with applying the latest updates available from Microsoft whether it is a service pack or a cumulative update. Hope, with coming years there will be many more changes which not only improves the product, but also improves the processes.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

SQL Server 2016 Can Be Installed on Linux

As a SQL Server DBA, we never would have expected that Microsoft will someday support installing and running SQL Server instance on a linux machine, but it has come true as a surprise, as Microsoft confirmed in their official website about the same. Refer here for more information. Since the inception of SQL Server, it was never supported or possible to install SQL Server on a linux Operating System. Although, some baby steps on this was started, when SQL Server was supported to run on Windows Core. Since many years Microsoft had a firm stand on not supporting its applications on different Operating System platforms, but with changing world, Microsoft had to change its view as well. There has been mixed response from the SQL Server community regarding this move.

One of the main reasons sighted by Microsoft regarding this move was taking into consideration clients who preferred to use Linux operating System, but wanted to use SQL Server. As SQL Server was not supported to run on Linux, many organizations have moved away from SQL Server as they do not want to get stuck with Microsoft suite, which benefited oracle and other open source technologies like MySQL. With this move, now SQL Server will be picked up by many organizations which are running linux or other open source applications. Although this news has been received positively across the SQL Server and other platforms community, still there are many questions about the stability and performance of SQL Server running in linux operating system. Once we have more details on this and people start installing the SQL Server on linux, we get more details about the problems that arise while installing SQL Server in linux and trouble administering the SQL Server on linux. Also, it would be interesting to see how the performance would differ, while SQL Server running on Windows and linux systems with same hardware.

This will be a benefit for the SQL Server DBAs as they will now get an opportunity or even forcefully have to learn working with linux operating system, which mostly operates through commands better. Most SQL Server DBA’s get stuck with knowing only windows operating system, which makes it difficult for them to lean other RDBMS products like Oracle or MySQL as they can run on both Windows as well as linux operating systems. Oracle/MySQL DBA’s had more feasibility to learn SQL Server, than SQL Server DBA’s leaning Oracle or MySQL, now this will change. Also, this will change the mindset of the SQL Server DBA’s to understand the importance of managing or administering SQL Server and operating system though commands, rather than GUI. There is still a long way to go, as it is expected that there are many challenges on the way for the SQL Server to work seamlessly on linux operating as it works on Windows operating System. This will bring more customer adopt SQL Server product, thus opening more DBA jobs. Also DBA’s who like challenging tasks would love this move, as it is completely new and no or very little documentation will be ever on this, which makes their job more challenging and interesting.

Stay tuned for more information.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Reasons to upgrade to SQL Server 2014

SQLServerF1

There has been quite few new SQL Server versions released frequently since the launch of SQL Server 2008. Currently the most used versions in most of the organizations are SQL Server 2005, SQL Server 2008 R2 and BDAs or organizations have been planning to upgrade from these versions to next higher version SQL Server 2012, however there has been another new release which is SQL Server 2014. Now there could be confusion about upgrading to which version? should we upgrade from SQL Server 2005/2008 R2 to SQL Server 2012 or 2014?

If you are planning to upgrade to higher version, then it is advisable to go with the latest release of SQL Server 2014, by skipping SQL Server 2012, as you can avoid use this version for longer time and there will be no need for another upgrade in few years, instead we can run with SQL Server 2014 for many years. Along with this there are also few other things which will prove to go ahead with SQL Server 2014 instead of SQL Server 2012, which include the license cost, which is almost same for both SQL Server 2012 and SQL Server 2014. Another important thing is that the end of life cycle date is far to ahead, so there is no force to upgrade to higher versions atleast for next 10+ years, unless we want to use any particular latest feature.

By upgrading directly to SQL Server 2014, you can get chance to use new features of SQL Server 2014 like In-Memory-OLTP, etc and also there are many enhancements to features like AlwaysON and also there are many enhancements to BI technology like SSAS, SSRS and SSIS. So, if you are planning to upgrade, it is better to prefer to go ahead with the latest releases always and in this case it is SQL Server 2014.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Pre-Installation Details for Microsoft SQL Server 2016

SQLServerF1

Recently Microsoft has made an announcement about the upcoming release of SQL Server 2016 Community Technology Preview 2 (CTP2 ). There has been great enthusiasm about features that will be released with the new SQL Server 2016 and the enhancements that are made to the new SQL Server 2016. To test out the new features we need to download and install new SQL Server 2016, so below are the details you would need to know before installing SQL Server 2016 which are referred to as SQL Server 2016 CTP2 Pre Installation Details.

Installation Guidelines for SQL Server 2016
– Make sure that you have an account that has local administrative rights on the computer where installing SQL Server 2016 CTP2.
– SQL Server 2016 CTP2 DVD Image: You can use this ISO image from http://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2016 and then burn it to your own DVD. Download the following .ISO file from the Evaluation Center: http://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2016
SQLServer2016CTP2-<architecture>-<language>.iso
Using your DVD-burning software, select the options to burn a DVD from an .ISO image. When you are prompted for a file to use, select the image file that you downloaded. After burning the DVD, locate and double-click Setup.exe on the DVD to begin the installation.
SQL Server 2016 CTP2 CAB file:
– Download the following files from the Evaluation Center to a temporary directory on your device:
SQLServer2016CTP2-<architecture>-<language>.box
SQLServer2016CTP2-<architecture>-<language>.exe
Once the download has completed, extract the zip files then double click on the SQLServer2016CTP2-<architecture>-<language>.exe to begin the installation process.

Instructions for installing SQL Server 2016 CTP2 on Microsoft Azure
Microsoft Azure has been in news of recent and many DBAs and developers want to try installing on Microsoft Azure too. For instructions on how to install SQL Server 2016 on Microsoft Azure, please go to the Microsoft Azure Infrastructure Services Page.
Some important Notes About SQL Server 2016 CTP2:
– The Microsoft SQL Server 2016 CTP2 release is NOT supported by Microsoft Customer Services and Support (CSS). Meaning, if you encounter any issues, you cannot open a support case with Microsoft, instead you can post it on any popular community forum which will be addressed if it is a critical issue.
– The Microsoft SQL Server 2016 CTP2 release is made available by Microsoft mainly for testing purposes only and should NOT be installed and used in production environments.
– Side-by-Side installation with down-level production SQL Server instances as well as in-place upgrades of down-level production SQL Server instances, is supported for SQL Server 2008 and higher.

Hope this was helpful to you

This is applicable for below versions of SQL Server

SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Node and Cluster Edition Match Setup Rule Check Failed

SQLServerF1

One of the common task of a DBA is to perform installation of SQL Server or applying patches. Most often of not the installation completes successfully without any errors, however sometimes the setup fails with small and simetimes complex weird errors. Unfortunately there are also great lot of bugs with the setup media as well. Starting with SQL Server 2008, the cluster installation has changed where we have to install SQL Server as cluster instance on first node and then run ADD Node operation on remaining all other nodes. Below is one of the error we faced in our environment while performing ADD node operation of SQL Server cluster instance.

Rule Check Result
Rule “Node and cluster edition match” failed.
The edition of the new node does not match the edition of the cluster.
From Details.txt log file
Microsoft.SqlServer.Configuration.SetupExtension.AddNodeEditionBlock
Slp: The edition user specified is: ENTERPRISE
Slp: The edition of the cluster instance: STANDARD
Slp: Evaluating rule : AddNodeEditionBlock

The error message in this case is pretty clear which states that the edition is not matching. As we have already performed installation of SQL instance as cluster in first node, and we are performing add node operation, it is possible that the setup media used to run add node operation can be of different edition than what was installed on first node. Checking the detail.txt setup log clarifies the doubt where it specifies that the edition of SQL Server setup media used is ENTERPRISE, but the SQL Server cluster instance to which we are trying to add is STANDARD edition, thus the mismatch. It is not possible or allowed to use different editions on each node, it has to be same.

Sometimes the errors are small and has clear message, so it is just a little common sense to understand and fix the problem. This kind of issue is very rare as installation on all cluster nodes are performed by same DBA on same day in a span of few days, but in some cases where installation of one or more nodes is performed and after few months or years, they decide to install another node. In such cases it is better to review the existing environment rather than directly performing the installation.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 
1 2 3 5