-
[quote user="Madhivanan"]Havn't you read previous links?[/quote]
yes , i do
The example show, extra information that say:
Take into account order of computation from left to right
select 7/6 * 1.0
is different than
select 1.0 *7/6
-
Starting May 18, 2009:
SQL Server 2005 SP3
Cumulative Update 4 and SQL Server 2008 SP1 Cumulative Update 2, introduces support for SQL Server Standard editions
to use the Lock pages in memory user right
review: http://support.microsoft.com/kb/970070/
http://msdn.microsoft.com/en-us/library/ms187499.aspx
-
Cumulative update for SQL Server 2008 Service Pack 1 contains
hotfixes for the Microsoft SQL Server 2008 issues that have been fixed
since the release of SQL Server 2008 Service Pack 1.
view: http://support.microsoft.com/kb/970315
The good news in that update
Support for Locked Pages on SQL Server 2008 Standard Edition 64-bit ...
-
Your data size is 30 GB , when reindex database you need extra about 30 GB, so at least 60 GB needed for database.
when you backup log file , the extra space is truncated, and re-used again.
It is better not to shrink database, shrinking may hurt performance .
if you want avoid increase of database due to reindexing , set sort_in_tempdb ...
-
Here , every stored procedure is created in a file with its name:
Catch procedure Name in the variable $a
foreach($Name in dir) {
$a=$Name.Name
$Name.Script() |out-file c:\$a.txt
}
-
Try these magic numbers:
select 7/6
select 7/6 * 1.0
select 1.0 *7/6
select 7.0/6
-
Compare the execution plan for both solution ,use set statistics IO /Time ON to find the difference
I agree with Adrian sp_executesql with parameters is better.
-
check
http://msdn.microsoft.com/en-us/library/ms146934(SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms143470(SQL.90).aspx
-
It may be terminated by software.
can you review windows system log, application log and security log for the time before 2009-05-28 01:05:40.90
If you have auditing system, you may find records that help.
i don't think that Invalid buffer received from client (about 10 hours before stopping)is the reason.
-
if table size is less than 1000 page (1000*8k =8000k =~8 MB) , is considered small table , so don't care for that tables for statistics.
if table is large, and it has auto incremented field, and that fields is pk or indexed , like int with auto increment, auto increment datetime , MS recomend run statistics with full scan, ...