Is 3 hour data loss acceptable for the business ? I prefer log backups every 15 or 20 minutes.

I run a server side trace 24/7 on my production server...

I use SQL Agent job and CmdExec as mentioned for exactly the same purpose, along with the "forfiles" command:

[font="Courier New"]

forfiles /p "f:\tracefiles" /s /m *.trc /c "cmd /c del @path"...

In answer to your original question: Display the tables in the "Object Explorer" window. Then select the tables you want (all or some), right click, "Script Table as Create", then...

I look at backup history to give me approximate database growth over time. Maybe you can adapt that to get what you need ? Backup size is usually...

You may have open transactions. run dbcc opentran

I have a server side trace running 24/7, so I dump the trace file(s) to a table, then query for a specific date range and sort by duration desc for...

I was starting to troubleshoot a timeout error that an application is having. I...

Thanks. Sounds like I am misplacing the blame.

Thanks.

I was prompted to look at RAM as a solution after getting this error message when trying to run a stored procedure:

An error occurred while executing batch. Error message is:...

I haven't worked with replication in a while, but when I did, and wasn't sure about something critical, I created some test replication databases and tried things out there first....

I use microsoft utility FORFILES to delete old files and schedule it through SQL agent. I think the syntax varies depending on your version of Windows.

For me on Windows server...

Did you recently migrate from 2000 ? I recall some slowness issues after migrating. In our case I think they were related to joins with converted data types...

Perhaps there is a way to run Litespeed on Server'A' to restore the database to server'B' ??

I think Litespeed customer support might give you the best answer, since versions and...

Thanks for the replies. We will find a different box to use.

I will put this directly before the restore:

ALTER DATABASE MyDatabase SET OFFLINE WITH ROLLBACK IMMEDIATE

That should be more reliable than the "kill @spid" loop currently in place.

Thanks