I've used sp_executesql but not sp_execute. The former provides for safe use of parameter specifiers for building injection-proof dynamic SQL. Maybe the latter is an application specific...

There is no way to find this out from SQL Server. SQL profiler can record this stuff but it has to have been running at the time.

How wide are the rows? (I suppose I should have specifically asked that as well).

I would try to keep the table as one (logical) table if at all possible. You...

That's a very good question... one I'd be asking the architect of that design.

What is your definition of "huge"?

It is really only dangerous in the case where appropriate and strict adherence to minimum required permissions and complex password safeguards are lacking or non-existent. Unfortunately this is true in...

look at the profile you set up for this account... see if you have checked the box: "this server requires a secure sockets connection" (or something like that).

Your server may...

I've always built my own log shipping mechanisms and they are easier to manage and more robust since they have more intelligence and robustness into the design than the stock...

if there were just a relative few you just fix them manually. If not, a cursor working on a set of these duplicates would allow you to consolidate the data...

you need to simply delete the ones you don't want. Write a procedure to resolve duplicates. Next you need to modify the business logic of your application and/or the...

I just kill any processes in that happen to be in the database before I execute the restore.

cursor loop through sys.sysprocesses where dbid = {yourdbid} and execute a dynamic kill...

SMO is pretty much required if you need to generate scripts of database objects or perform certain other server operations programaticaly.

This is called CONTROL permission, and yes the truncate will fail without it.

Truncate will...

I always use this:

select rowcnt from sys.sysobjects O JOIN sys.sysindexes I on O.id = I.id and indid = 1 where type = 'U' and name = 'TABLENAME'

PROBLEM RESOLVED.

What was causing this was an addition of a linked server insert... a single row insert to a table on another server, to the activated stored procedure.

Even though no...