hmm... i've already set all this up in sql server 7 with the good'ole .sql files that come with (BORK), and even tho i have it all set up properly it doesn't seem to be doing any thing. i'm thinking that you don't necessarily run the .sql's as a whole, but rather you go thru the code, and run blocks of it, changing variables as you go along.

i'm about to take this course of action, cause i'm not quite sure what i didn't do at this point. there really isn't a whole lot of material out there (at least none that i have found) on the subject of the sql code.

has any one done this with flying success? if so, i could use some info from a seasoned professional on the subject of sql 7 log shipping. if you could just walk me thru this one more time that would be great!!

thanks in advance.

cheers.

Mike1/25/2002 1:17:22 PM

Very well written. Clear. Concise. Step by step, without overly verbose descriptions.

Thanks!

Tyler Olsen 11/27/2001 6:08:10 PM

Has anyone had success implementing this? Although Ron doesn't suggest using log shipping for reporting purposes, I'd like to use it rather than setting up some huge replication scheme.

Thanks.

Randy M. Franklin, Jr. 4/17/2001 2:07:04 PM

If you don't want to reconfigure all your clients in a failover situation, just use a function-specific Netbios alias if your clients connect using named pipes or a function-specific DNS alias if you use IP sockets. In a failover, you just change the alias to point to the new server. Clients should never refer to a server by name or IP number. It causes to many headaches in the long run.

Stephen Brain 3/25/2001 5:28:47 PM