Looks like this was a code change in 2005; works fine in 2005/2008 but not in 2000, which unfortunately is what we're using here.

Agreed, but I was still getting the error using NORESEED, as per my post. I'm guessing the DBCC code does a BEGIN TRAN whether you want it to reseed...

Just in case anyone finds this post later on, when I tried to run

DBCC CHECKIDENT(MyTableName, NORESEED)

while the database was in standby (read only) I got the following error:

Msg 3906, Level...

Surely this depends entirely on the usage patterns of the affected systems? We have some servers that are used mainly in the morning (eg 7am - 2pm) so we can...

I've actually brought the db online now and CHECKIDENT is not showing anything unexpected. CHECKDB didn't return any errors either.

Not sure what exactly caused errors but db and table appear...

Does anyone else think that, while this looks like a decent tool which gives quite a thorough report, it is vastly over-priced?

We have about 60 servers here and I have...

Thanks for this. You are right, both options are set OFF for the proc.

Can you explain why this would affect the generated execution plan?

SELECT work_code AS [Work

Code], work_nature AS [Work

Nature]

FROM sb_cm_work_nature

If you're doing this from Query Analyzer you will need to be in "results to text" mode to see it.

baxterg is correct. Here is another way of viewing the table variable in tempdb:

SELECT id INTO tmp

FROM tempdb..sysobjects

GO

DECLARE @t table (a int)

SELECT *

FROM tempdb..sysobjects

WHERE id NOT IN (SELECT id...

Not having any experience of SQL 2005 yet, I had to make an educated guess on this one. Was I the only one to be tripped up by the...

That features comparison does not even mention Developer edition though so you need to look at that separately. When you do (eg, check the other link in the explanation)...

I thought this was a rather ambiguous question. The question asked how you would exclude JUST the oldest error log from the report. The correct answer to this...

While I appreciate that questions on relational theory are perfectly valid in a SQL Server environment (and maybe the last few days' questions have even taught me something!), are we...

After my previous post, I had a thought that maybe it wasn't always dbo that was the owner - maybe it was actually owned by the user executing the procedure...

I agree with David, my tests also show dbo as the owner of any temp object created in a proc.

This is the procedure I tested with. UserA is a...