This is how I do it: I write a log record in a table when it starts and updates the column [endtime] in that logtable when the procedure finishes. If...

UPDATE:

For some reason, somebody blew up the tempdb. This caused a Quest databaseperformance collector (quest_sccollector64.exe) to go mad and hammered the CPU. After killing this process, SQL is normal (including...

Thanks for your reply, but that's not what I'm looking for.

I'm just curious to know what's causing this problem and how I can identify these types of problems.

Implementing NT...

forgot to say : it's 64bit

Try this key:

Set@RegPath = 'SOFTWARE\Microsoft\Microsoft SQL Server\' + @SQLInstance + '\Setup'

EXECmaster..xp_regread 'HKEY_LOCAL_MACHINE', @RegPath, 'SQLDataRoot', @value=@DataPath OUTPUT

Thanks for your reply. Just extend the edition check to:

/*

Snapshots are only supported on Developer and Enterprise editions

*/

if CAST(serverproperty('Edition') AS VARCHAR) not...

Update:

I removed an identity clause with Management Studio and traced the statements. SQL is actually not executing the statement I'm looking for but it's copying data into a temp table,...

Am I missing something? If max server memory is unlimited, and your database is large, or you don't have much stored procedures, or you have a lot of connections etc....

If you put a snapshot on a mirrored database, you can use the database for read operations

About logshipping: If you apply logs, no one...

Why would you do that? (I assume you use a primary key field for something like an order number) It's better to separate your data with a primary key, used...

Try this:

declare @stepsize int

declare @rownumber int

set @step = 20

set @rownumber = 64

select * from table

where rownumber between ((@rownumber / @step) * @step) and ((@rownumber / @step) * @step) +...

If the need for this index is out of the question, maybe you'll have to rebuild/reorganize your indexes more frequently.

I recommend the script from Lara Rubbelke http://blogs.digineer.com/blogs/larar/archive/2006/08/16/smart-index-defrag-reindex-for-a-consolidated-sql-server-2005-environment.aspx

It's not worth to rebuild indexes with less than 1000 pages (not rows), fragmentation on such a small index is not an issue.

here we go again .... to summarize previous discussions: AWE is not necessary on 64bit (completely ignored), however, lock pages in memory is recommended (and necessary if you want...

I agree with Bob. Why write some unreadable code in order to avoid cursors? To my opinion, cursors are easy to implement, very straightforward and the extra cost of performance...