Though the message specifies as an informational message only and no user action is required, you should take some action to avoid current behaviour of databases within your environment. Also check whether you have enabled the AUTO_CLOSE property for any of the databases on that SQL Server instance, on the down side it is not recommended in ...

The following pages were recently modified. Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise Edition & SQL Server 2005 Standard Edition Notification Contents: New and Major Modifications Some or all SQL Server 2005 services are not listed in SQL Server Configuration Manager, or you receive a ''No SQL Server 2005 components ...

This error started generating since last 2 days on a scheduled job that uses SSIS to import content from a flat file. Eventually we found that a derived column within the table and the flat file flow where dates in YYYYMMDD are changed to MM/DD/YYYY format. Then the string MM/DD/YYYY is converted to a date in a Data Conversion flow. And finally ...

Source: Knowledge Base Product: Microsoft SQL Server 2005 Standard Edition, SQL Server 2005 Enterprise X64 Edition & SQL Server 2005 Enterprise Edition Notification Contents: New and All Modifications FIX: Error message when you run a query that is associated with a parallel execution plan in SQL Server 2005: ''SQL Server Assertion: File: ...

Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise Edition Notification Contents: New and Major Modifications FIX: Error message when you run a query in SQL Server 2005: ''Cannot insert duplicate key row in object <TableName> with unique index <IndexName>'' http://support.microsoft.com/kb/937533/en-US FIX: A Service ...

To my surprise a deadlock information is not logged on SQL Server log, after a struggle for half-day I found that the startup parameters were messed up! It may be usual practice by adopting [ ; -T1204; -T1222 (with blank after semicolon) ] that is what we applied and though the application generating deadlock information the error log is missing ...

What to do when you get the error specified on the subject above? You might get this error message from a job which will send email to an operator when it is completed. First thing to check whether a valid email has been mentioned in the operator. Also there are few other steps involved that involves restarting SQL Server Agent service, here it ...