Of course, you can still fix it...

QUOTENAME(REPLACE(REPLACE(somecolumn,']',''),'[',''))

Where does this proc live?  In Master?

Aren't you still using the 4 part naming in the dynamic SQL?  I don't think that's gonna work unless you try it like this... (although, I certainly could be wrong)...

EXEC...

Sorry... just figured out what you're trying to do...

If you call the stored proc in Master from a given other database, then I think you just do the delete using...

OK, but you need to use dynamic SQL anyway... why temp fate with Master?  Create the DBA database and work from there...

You'll need to use dynamic SQL to create and execute the delete, but I've gotta ask a question...

Your DBA let's you write to the Master database??? Or, if you're the...

Echo.>>yourfilename simply appends a blank line to your file... Echo. creates the blank line.... ">>" is the old DOS notation for "take the output of the command to the left...

Moving data from the main database does not shrink the space reserved for the main database... nor should you shrink it unless this is the very first time you've archived.

Pretty sure that's what it means...

Maybe in SQL Server 2005... in 2000 the estimated execution plan show "something" and the actual execution plan shows absolutely nothing.

You said the query was throwing an error... probably be helpful if you posted the error message(s).

It depends... what kind of string is it??? CSV, Fixed Field, XML, Quoted CSV, or ????

Close... I'd check just for dupe ID_Num's first... the rest of the columns are ancillary in nature...

Or, just take out the ID_Num to see if the same person has been...

Are you looking at sp_Who2 during these times?  You need to find the code or process that's grabbing resources and see if you can change it.

A function call is limited to the 3 part naming convention... See Books Online.