Tom's blog

Microsoft recently released new cumulative updates for SQL Server 2008 R2. You can find the new cumulative updates, build numbers and link to the download site underneath.

SQL 2008 R2

SQL 2008

Tom

Microsoft has recently released CU 1 for SQL 2012. It contains 55 hotfixes for issues that are fixed after the release of SQL 2012.

Tom

Microsoft recently released new cumulative updates for SQL Server 2008. You can find the new cumulative updates, build numbers and link to the download site underneath.

SQL 2008 R2

SQL 2008

Tom

Microsoft recently released new cumulative updates for SQL Server 2008 R2.

SQL 2008 R2

SQL 2008

Tom

I have updated the Service Pack and Cumulative Update list for SQL 2008 R2 and SQL 2008:

SQL 2008 R2

SQL 2008

Tom

Recently Microsoft has released Service Pack 3 for SQL 2008. I have updated the overview for both SQL 2008 R2 and SQL 2008

I changed the overview a bit, so you can better see the levels of cumulative updates and how they correspond to each other

SQL 2008 R2

SQL 2008

Tom

I recently had a strange error when installing a slipstreamed installation of SQL 2008 SP2:

The summary didn’t give a clear explanation:

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Exit code (Decimal):           -2068643839
  Exit facility code:            1203
  Exit error code:               1
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2011-08-17 11:08:48
  End time:                      2011-08-17 12:22:59
  Requested action:              Install

So I took a look in the detailed setup log, more or less the same:

2011-08-17 12:23:01 Slp: Error result: -2068643839
2011-08-17 12:23:01 Slp: Result facility code: 1203
2011-08-17 12:23:01 Slp: Result error code: 1

Apparantly the SQL services have tried to start, and an ERRORLOG was generated:

2011-08-18 11:34:14.28 Server      Error: 17182, Severity: 16, State: 1.
2011-08-18 11:34:14.28 Server      TDSSNIClient initialization failed with error 0×80092004, status code 0×80. Reason: Unable to initialize SSL support. Cannot find object or property.

2011-08-18 11:34:14.28 Server      Error: 17182, Severity: 16, State: 1.
2011-08-18 11:34:14.28 Server      TDSSNIClient initialization failed with error 0×80092004, status code 0×1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.

2011-08-18 11:34:14.28 Server      Error: 17826, Severity: 18, State: 3.
2011-08-18 11:34:14.28 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2011-08-18 11:34:14.28 Server      Error: 17120, Severity: 16, State: 1.
2011-08-18 11:34:14.28 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

After searching for this on the www, I found some references to a corrupt user profile for the account running SQL Services. I took a look at the profiles and it seemed that for this user, only a temporary profile was created. After looking at the account properties in AD it seemed that there was something weird with it, no user logon name was specified and the pre-windows 2000 logon name had a space at the end.

We deleted the account, re-created it, re-installed SQL and no problems anymore!

Recently our operational team had to do a restore of a database for BizTalk. These databases require a special restore routine, to let the BizTalk components in sync with the DB.

First they restored the latest full backup, which went without problems.

Then they needed to restore the transaction log backups, with the STOPATMARK option set:

RESTORE LOG [Database] FROM

DISK = N’LocationOfBackupFile’

WITH FILE = 1, NOUNLOAD, STATS = 10,

STOPATMARK = N’BTS_2011_06_06_00_00_29_087′ AFTER N’2011-06-06T02:00:32′

GO

which results in an error:

100 percent processed.

Processed 0 pages for database ‘Database’, file ‘Database’ on file 1.

Processed 2 pages for database ‘Database’, file ‘Database_log’ on file 1.

Location:     diskio.c:1769

Expression:   filepos + cBytes <= (DWORDLONG) m_size << PAGESIZEBITS

SPID:         65

Process ID:   1908

Msg 3013, Level 16, State 1, Line 1

RESTORE LOG is terminating abnormally.

Msg 3624, Level 17, State 1, Line 1

A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

When restoring the log without the STOPATMARK option, no problems are encountered.

The log mark entries where all filled in correctly. You can see this by querying the dbo.logmarkhistory table in msdb.

We opened a case at Microsoft and they confirmed that this is a bug and is fixed in CU4 for SQL 2008 SP2 (http://support.microsoft.com/kb/2527180). I’ve asked for more information, but they cannot provide it for the moment as it is confidential. I still hope to find some more information though, I’ll update this post with the details.

Tom

Microsoft recently released two new cumulative updates: CU14 for SQL 2008 SP1 and CU4 for SQL 2008 SP2.

This makes following build table:

Current Cumulative Update Packs for SQL 2008:

Current Cumulative Update Packs for SQL 2008 R2:

Current Cumulative Update Packs for SQL 2008: