Does your SQL account have access to delete files in backup folder?

No, it's just basically ignored. I just noted for you reference so you don't worry about it in the future.

http://msdn.microsoft.com/en-us/library/ms190673(SQL.90).aspx

You don't need to worry about the AWE for 64 bit. It's basically ignored as the memory can be directly accessed.

Didn't know this. Good to know.

For some reason I was thinking...

a quick google search of "how to set page file size windows 2003" (or your OS) will give you many pages on how to.

it's your order by, your are referencing an alias.

change it to "ORDER BY 5 DESC" instead of "ORDER BY NOTA.CODLIQ DESC"

Did you try searching for this in google?

http://msdn.microsoft.com/en-us/sqlserver/bb671432.aspx

On here somewhere there is security best practices documents.

There's also tools like the Microsoft Baseline Security Analyzer and the SQL...

Check out sp_Delete_backuphistory

http://technet.microsoft.com/en-us/library/ms188328(SQL.90).aspx

Be careful with this SP as it's slow as hell. If you have like 6 months worth of history, delete out like a few weeks...

The first thing you need to do is find out what time the tape backup starts and how long it takes. Find your window. If you can't do...

See if this works for you

http://benchmarkitconsulting.com/colin-stasiuk/2009/06/03/sql-server-2005-edition-upgrade/

If you insist on using SQL for this, I would --

create script to enable xp_cmdshell & run cacls.exe using xp_cmdshell & then disable xp_cmdshell

choose a method to multi query multiple...

Set it back up in the SQL Configuration Manager. That should give the account permissions needed (I believe). It does for Server/Agent.

that's where I would start.

You could use robocopy (in the win2003 resource kit tools).

It has options to move files, sync folders, only copy files older than (or newer than) x days, auto restart, resume...

you can use the import/export wizard in SSMS. Right click database, goto Tasks, then Import (or export) Data

add on a few hours to compensate for the variance in backup time.

it doesn't have to be 6 hours. depends on how long your backup tasks run over all...