traces continue to run in the background and keep on writing captured information in the trace log file. You wont see anything other than what u saw in the query...

deleting all data from tables will be much slower than truncating the table. Delete logs each and every transaction in the log file where as truncate logs minimally.

you can write a query to delete all tables in a schema.

Also wouldn't it be good to drop the database if you do not want tables to be there?

Question is...

This article posted as a link on SSC provides good example on how to setup a server side trace and how to query it.

http://www.builderau.com.au/program/sqlserver/soa/Write-custom-trace-files-in-TSQL/0,339028455,339282437,00.htm

seems the job owner is unable to reach the backup path due to insufficient privilages.

Provide access to the job owner to the shared path OR change the job owner...

yes restore in norecovery mode. and you cannot backup log if your source database is not in FULL recovery mode.

restore the full backup in norecovery mode and restore the log...

Can you perform backup/restore in norecovery/recovery modes. I've changed ur queries a bit.

1) Backup and restore DB

BACKUP DATABASE NorthWind TO DISK = 'c:\orthwind.bak' WITH INIT

RESTORE DATABASE NW2

FROM DISK = 'c:\orthwind.bak'

WITH...

i hope this is what you're doing. Backup of ur primary db

Backup database yourdb to disk = 'path\myFullBak.bak'

Restore this full on ur secondary

restore database yourdb from disk='path\myFulldb.bak' with standby

insert/delete/update...

select * from db2..sysobjects where name='myTablename' and xtype='U' should return a row if myTableName exists in db2 or NULL if it doesn't.

Once you get to know which query is blocking, you may want to see if it's optimized, whether it's using indexes properly.

may be someone had fired a huge insert/update query which was taking long to rollback....

it should run... 🙁

try executing alter database mydb set single_user with rollback immediate and then try restoring the backup again...

heh... there is no need to create linked server... OP wants data to access from other database and not other server.

This should do fine if db is present in same...

prefix the database name in the query.

if exists(select * from db2.dbo.sysobjects where id = object_id(N'[db2].[dbo].[sale]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)

change the database context to master database and then run restore log...