SQL Server Latest Updates (Nov. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2016 RTM and SP1 and 2017 RTM,:

Cumulative Update #2 for SQL Server 2017 RTM

Cumulative Update #9 for SQL Server 2016 RTM

Cumulative Update #6 for SQL Server 2016 SP1

Starting from this month, we finally get AdventureWorks on github! The direct location is https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks

Stay Tuned! 🙂

SQL Server Latest Updates (Oct. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2017 RTM, 2014 and 2012:

Cumulative Update #1 for SQL Server 2017 RTM

Cumulative Update #8 for SQL Server 2014 SP2

Last but not least, welcome the SQL Server 2012 Service Pack 4!

Stay Tuned! 🙂

SQL Server Latest Updates (Sep. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2016 RTM & SP1:

Cumulative Update #5 for SQL Server 2016 SP1

Cumulative Update #8 for SQL Server 2016 RTM

Starting with SQL Server 2017, the SQL Server releases will follow the Modern Servicing Model, read more here.

Stay Tuned! 🙂

Best Solutions to Repair Suspect Database in MS SQL Server

To repair Suspect database error in MS SQL 2005, 2008, 2012, 2014, 2016 and 2017 read this article to recover SQL Server database from Suspect mode.

What is Suspect Database Error?

Microsoft SQL Server serves as a storehouse for data that is needed for different software applications on a single system or across a network. Sometimes a user may face a situation where a database in the SQL Server instance currently under running state is marked as Suspect. This condition will lead to a failure in creating a connection with the database. Such a database which is tagged as Suspect can be accessed by removing the causes for this problem. The forthcoming article will discuss the causes for this problem to occur and the possible solutions to repair suspect database from SQL Server 2005, 2008, & 2012.

The error message shown to user is somewhat similar to the one given below

Starting up database ‘abc_d’.
Error: 9003, Severity: 17, State: 5.

The log scan number (189623:15:2) passed to log scan in database ‘abc_d’ is not valid.

The above-mentioned error shows that there is some corruption of the log file(.ldf) and does not adhere to the data file(.mdf). Other error messages can also be shown depending upon the cause due to which the database has been categorized as Suspect.

User queries help in getting a better idea about the problem and to recover SQL database.

“I am currently using SQL Server 2008 edition on my Windows 7 system and there are many applications of mine that are dependant on it. Recently I have been facing difficulties in connecting my applications to some of my Databases and they are being shown as Suspect. Kindly guide me to recover SQL database from Suspect mode.”

SQL Server Database Shown as Suspect: Possible Reasons

There are a number of reasons why SQL Server marks a particular Database as Suspect.
Some of these reasons are mentioned as follows

  • Corruption present in the SQL Server Database
  • Insufficient space available to SQL server to repair suspect database during startup.
  • The files of Database are in use by OS or other Backup software
  • Sudden SQL Server Shutdown, Hardware or Power Failure

There exist a number of techniques for solving the issue of Suspect SQL database and broadly they can be classified as Manual and Automated. The upcoming section will try and explain a Manual technique for achieving this goal.

Quick Tip: If you want to skip the tedious & complex manual approach then it is highly advised to use an automatic tool such as SQL Recovery to efficiently recover SQL database from Suspect mode

Repair Suspect Database Manually

Implement the steps given below to recover Suspect SQL Server Database and to access important data.

1. Bring Database in Emergency Mode using the following code

USE master
GO

ALTER DATABASE abc_d SET EMERGENCY
GO

2. Execute DBCC CHECKDB command.
This will scan and check the physical and logical integrity of objects present in the marked database

DBCC CHECKDB (abc_d )
GO

3. Bring the Database in Single Mode using the below-mentioned query

ALTER DATABASE abc_d SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO

4. After the Database is in Single Mode, execute the following code to repair suspect database

DBCC CHECKDB (abc_d, REPAIR_ALLOW_DATA_LOSS)
GO

5. Lastly, restore Multiple access to the database by executing the query

ALTER DATABASE abc_d SET MULTI_USER
GO

Repair Suspect Database by Manual Method: Shortcomings

  • Manual solution consumes a lot of the users’ time for SQL server suspect database repair
  • High risk of losing data forever during manual approach to recover SQL database from suspect mode
  • A Large number of queries to recover SQL database make it complex for non-technical users.
Conclusion

The Suspect database problem is a common issue faced by users of SQL Server database and it has various causes. There is a set of TSQL commands to overcome this error but it poses many issues during implementation. It is better to use automated tools designed specifically for this purpose to repair suspect database.

SQL Server Latest Updates (Jul. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2012, 2014 and 2016:

Cumulative Update #10 for SQL Server 2012 Service Pack 3

Cumulative Update #13 for SQL Server 2014 SP1

Cumulative Update #6 for SQL Server 2014 SP2

Cumulative Update #7 for SQL Server 2016 RTM

Cumulative Update #4 for SQL Server 2016 SP1

Stay Tuned! 🙂

SQL Server Latest Updates (Jan. 2017)

Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2012 and 2016:

Cumulative Update #7 for SQL Server 2012 SP3

Cumulative Update #16 for SQL Server 2012 SP2

Cumulative Update #1 for SQL Server 2016 SP1

Cumulative Update #4 for SQL Server 2016 RTM

and then, SQL Server vNext Management Pack!

Stay Tuned! 🙂