|
|
-
|
|
SQL Server force you to put columns in SELECT DISTINCT list which are part of ORDER BY clause. But what if we don’t want to add that column/s in SELECT list???...
|
|
-
|
|
Recently, due to SQL Server Log message The time stamp counter of CPU on scheduler id 13 is not synchronized with other CPUs. we have decided to resolve it by installing Service Pack 3 for SQL Server 2005. To confirm, that target server has version prior t...
|
|
-
|
|
This morning in log report of one of our production server I found an unusual error.DeviceIoControl failed, error 21 DeviceIOControl is a function which sends code to your disk drivers to perform read or writes functions and error 21 clearly indicates ...
|
|
-
|
|
It happened dozen of times when I tried to get an Estimated Execution Plan, it return object verification error, while the same Stored Procedure was working perfectly. Then what’s wrong with Estimated Execution Plan, lets create a simple procedure.CREATE P...
|
|
-
|
|
Yes you can restore a backup file which is taken from SQL Server Enterprise Edition to Standard Edition BUT if source database is not using Enterprise Edition Specific Features. Like partition functions in our case. This happened to one of my junior, wh...
|
|
-
|
|
Problem occurs when we try to restore a database from backup set, but using MOVE option and when you provide wrong logical name of file in MOVE section of RESTORE script. To avoid this problem, first, one must verify original logical names of files by us...
|
|
-
|
|
Recently we have found that our index defragmentationjob is failing on a production server, due to REORGANIZE failure of one of our index. SQL Server was unable to REORGANIZE this index because mistakenly we have an index with the ALLOW_PAGE_LOCKS option...
|
|
-
|
|
One can check integrity issues by using DBCC CHECKDB (“DatabaseName”) and unfortunately if DBCC CHECKDB returns some type of database corruption, then it can be solved by executing DBCC CHECKTABLE. According to BOL “DBCC CHECKTABLE: Checks the integrity ...
|
|
-
|
|
This morning, while going through my regular SQL Server Logs reports, for one of our production server, I found a different error. SQL Server has encountered 52 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\Program Fil...
|
|