You could start by running sp_Lock during the periods of slowness. Running sp_HelpDB will allow you to figure out the DBID for TempDB... check for blocking on that DBID...

It was a way of saying "Thanks, Steve". I do it the same way Remi does...

Any luck yet on the triple spacing problems I told you about or...

Heh... I know that's gotta be right... just inserting 1 row into a brand new copy of the table gives me... (note that I run this type of code in...

And, here's a good article by the gent that got me interested in Tally tables a thousand years ago... just remember, he doesn't really explain how to do the "business...

Like any other function that returns a table, you should be able to use the function to create a permanent table...

[font=Courier New]

SELECT *

INTO dbo.newdatetable

FROM dbo.F_TABLE_DATE(somestartdate,someenddate)[/font]

My concern is... what do you...

Guess I get to put the bat down... 😀 Separate tables.

One of the recommendations in Books Online under "deadlocks, avoiding" is...

Keep Transactions Short and in One Batch

A deadlock typically occurs when several long-running transactions execute concurrently in the same database....

And, lookup "parameter sniffing" on this site or Google...

Like everything else, it depends...

It's easier to maintain security differences on two procs if you only want certain people to be able to use the "full-details" version. If you...

I agree with Ed... sure, you should be sending backup tapes off site. Sure, you should save some text files and send them offsite. And, I agree... what...

Adding an Identity column to each table isn't that much work if you write a little dynamic SQL to do it for you... especially if you have it all worked...

Heh... thanks, Lowell... you're too kind :blush:

Clarence,

If your barcodes/customer numbers get above 11,000, you can very easily change the "Tally" table to a million, but I wouldn't go much higher...

It's an SQL Server 2000 forum... no CTE's here...

Hi Mick,

Long time, no see...

Just an FYI... be real careful about using SET ROWCOUNT... if the queries after the SET have ORDER BY on large tables, you're going to...

...or duplicated data...