valuable article; whenever I found a situation similar to this, I always blamed out of date statistics, and updated statistics and recompiled procedures; nice detective work, I have a better...

Tony may be on to something....a typical problem where something works fine, and then slows down over time often points to out of date statistics on the database; this can...

i think what you are seening is whenever anyone is given the role db_owner(), their user_name is considered to be dbo for the queries performed.... since everyone else comes in...

i fat fingered the link and added a backslash..sorry.

I edited the link and it does take me to the right spot now.

a better explanation of index hints than BOL supplies can be found here:

http://www.sqlservercentral.com/columnists/rmarda/performanceaddinghints_printversion.asp

it's bad to second guess SQL Server's abilities as far as deciding which index to use, but...

you didn't really describe what the problem was...whether it was slow running, received a real error, or just bad performance.....so here's my guesstimate:

There's no problem creating a really big temp...

Glad you worked it out , Dave;  keep reading SSC; lots of good stuff here.

it looks to me like you are using a loop to insert one group of data at a time, when you could do it all as a single set based...

are you sure you want to do in in SQL Server? why not a programming language, like .NET,VB6 or something?  you stated you just want to copy it to disk,...

pointing out the obvious, but you should not be trying to display all 4.8 million rows in EM while connected to a production database....

you are right, EM and SQL server...

i can only suggest some general/generic things to look at; nothing obvious or strange in your query, so I'd look at things like service pack on the machines that fail...

what Guru is saying is you will receive an error if you try and use EXEC to populate a @table variable;you must use a #temp or ##temp table

here's a proc...

we recently did the same thing in our shop...we had separate databases for each application.  whenever one of our clients had more than one application, the issue of duplicate data...

don't know if this will help, but this thread talks about differences in file/folder permissions screwing up an install on a normal machine:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=357952#bm358701

HTH

you cannot do that natively. the change/insert information related to data is not captured.

usually, if this is required,  you'd add two columns to the table, as well as a trigger....search...