I need a different approach to programming a transfer of a database.

An old approach, kind of a hack, using SQL Agent to schedule running a
..BAT file, is to zip a .BAK file and copy it to another machine, which
runs a separate .BAT file that unzips the .BAK and runs a .SQL script
using ISQLW. The SQL script does a restore.

This is done from a SQL Server 2000 database to a SQL Server 2000
database.

I now have to do the same thing from a SQL Server 2000 to a SQL Server
2005, and, as best I can tell, 2005 has no ISQLW.

I know there are better approaches to achieving the same end, like log
shipping or using an SSIS 2005 package, and I'm open to suggestions.

The 2000 to 2000 transfer is over a slow WAN, the 2000 to 2005 is over
a LAN. The .BAK file is 6 gig and 900 meg zipped.

I'm hoping someone can recommend, and briefly outline and approach, for
a daily overnight process to maintain a backup database.

Thanks, Bren

You should look at using one of the third party tools that do compression in
the sql backup and restore.
www.red-gate.com
www.quest.com

In any case iSQL was replaced in 2000 with oSql and the new utility in 2005
is SqlCmd.

--
Andrew J. Kelly SQL MVP


<bren (AT) ebesser (DOT) com> wrote

Idera do a similar product too. Not a recommendation of this over the others
though, just info.
osql is still there in SQL 2005 as well, for compatibility I assume, as
sqlcmd has plenty more features.


"Andrew J. Kelly" <sqlmvpnooospam (AT) shadhawk (DOT) com> wrote