Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

Another quick one for today: When you encounter such an error (see the title and the print screen below), you might want to check this first: http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/b0665753-6bb6-48bb-a938-febc6e942d58 For the really lazy ones: it's a clear sign of memory pressure. I hope this helps. Best regards,io

BACKUP DATABASE TO DISK = N‘NUL’ – and misconceptions

Hopefully this will help someone out there. There is a command, BACKUP DATBASE <db_name> TO DISK = N'NUL' and apparently people either don't know that is there, or are using it for all the wrong purposes. We use this particular command to find out our "golden point", so to speak, which means that we can … Continue reading BACKUP DATABASE TO DISK = N‘NUL’ – and misconceptions

How can I tell if my restore process is actually doing something

Just stumbled into this: if you have a large DB to be restored, it might take forever to actually see the progress moving to 10%, 20%, and so on. Yeah, I know, you should never do a restore from the SSMS, but don't try to tell me thatJ. Anyway, coming back to our scenario: if … Continue reading How can I tell if my restore process is actually doing something

Is the primary key always clustered in SQL Server?

As I was playing in SSMS (SQL Server Management Studio), I created a table using the plain-old T-SQL, and then I decided to create a primary key, the "wizard" way, so to speak. Let's have a repro here: CREATE TABLE [dbo].[Employees] ( [empID] [int] NOT NULL , [firstname] [varchar](30) NOT NULL , [lastname] [varchar](30) NOT … Continue reading Is the primary key always clustered in SQL Server?