You can join the table with the names of tables also the statement.

If not references are present on the tables:

EXEC sp_MSForEachTable 'truncate TABLE ? ' will be enough to truncate all tables.

the sp_MSForEachTable replace the ? for the actual table Name.

We used a similar aproach,however, most of the time whe want the trigger to do as little and as fast as possible, so we move the data straight into an...

Yes, it will work, however, before trying this is always good to create a backup of your database; also, it doesn't hurt to set the database to single_user and run...

I will gladly help you if you write about what are you trying to do. There are many uses for the script such as inserting into a bulk insert, deleting...

Here it is:

--------------4. Restore Relationships. ON delete NO action to be research ------------

/* Restore relationships for delete set to no action; for update set to no action as on

...

What about if all you want is to give an empty shell to a developers groups or you want to do a bulk insert into multiple tables?

The proper syntax should be:

EXEC sp_MSForEachTable 'ALTER TABLE ? NOCHECK CONSTRAINT ALL'

where the ? is been replace for the table name

Going forward, we kind of loose track of the actual question for the post. In conclusion:

1. A sql trace or profiler can be use to track what is been execute.

2....

I do agree on the weakness of using the host name, however, we are making assumptions of how the users are connecting to the database, are they using an application?...

What about the sql server 2005 Dashboard performance reports :

http://www.microsoft.com/downloads/details.aspx?FamilyId=1d3a4a0d-7e0c-4730-8204-e419218c1efc&displaylang=en

That will give you a lot of information about what is going on from the cache to the average...

Third party tool like SQL Auditing from apex is not bad, however, what about using the host name from the connection string such as the computer name? Have a look...

Thanks, this process can be used to many others uses, a cp files can be however, not many dba's like to have cmd other than sqlcmd runing on theirs boxes

q1) there are many ways. The easiest would be to detach the database copy the .mdf,ldf and logs zip them (.rar ) get them to the second server and then...

If all you want to do is rename just run this:

alter database database name set single_user with rollback immediate

go

alter database DatabaseName modify name = NewDatabaseName

go

alter database NewDatabaseName set multi_user

go

print...