Hi,

I'm a consultant for some small company and they
purchased a MS SQL Standard Edition, I think it's MS SQL
2000, I think it's latest .. I can find out exactly if it
needes too, anyway here is what we want to accoplish and
I just wanted to find out what would be a better solution
for that..

we donig clustering, but not really clustering.. (i hope
i'm not too confusing.. =) ) anyway .. i dont think
standard edition can work as a cluster so what we though
we'll do for now is just somehow copy database,
preferable within ms sql itself it'd make 2 copys on two
diff machine/hdd/etc and in case if one machine goes down
we manually change ip or host if needed so that our
customers can use other machine.. while we restoring
first one..

what would be a better solution for that? and is it
possible to do within ms sql itself?

thanks in advance

Consider log shipping. But you need to roll your own or modify one of many
pubslished log shipping solutions. SQL2000 Standard Edition doesn't come
with the built-in log shipping feature available in SQL 2000 Enterprise
Edition or Developer Edition.

Do note that log shipping may incur some data loss, the extent of which
depends on the frequency of the log backups and whether or not you can do
the final log backup on the primary and ship it to the secondary.

If your database is a simple data store for your application, replication is
another potential choice, although it's messier than log shipping for
maintaining a recovery database. Log shipping is a simple backup and restore
and includes everything in the database, whereas replication involves a lot
more pieces and may not include some changes (e.g. certain schema changes)
in your database.

--
Linchi Shea
linchi_shea (AT) NOSPAMml (DOT) com


"ml (AT) db (DOT) nexgen.com" <anonymous (AT) discussions (DOT) microsoft.com> wrote

okay, that's seems about what we need where do i get
this "log shipping"?

thanks in advance

You can get custom log shipping scripts from many places:

1. SQL Server 2000 Resource kit has some scripts
2. Alan Hirt's Microsoft SQL Server 2000 High Availability
comes with two CDs containing some log shipping scripts.
(http://www.amazon.com/exec/obidos/tg.../-/0735619204?
v=glance)
3. SQL Server Professional published custom log shipping
scripts and articles (http://www.pinpub.com/html/main.isx?
sub=36)
4. Check out "What is the best way for maintaining a
standby SQL Server?" at
http://vyaskn.tripod.com/maintaining...sql_server.htm
5. Check out "How to Perform SQL Server Log Shipping" at
http://www.sql-server-
performance.com/sql_server_log_shipping.asp

Linchi

Linchi

Thanks for info, however I wasn't able to find a Resource Kit for MS SQL
2000. Also I found info on how to setup log shipping for ms sql at microsoft
site however they say its only possible with enterprise edition, and as i
specify earlier i only have standard edition that''s the problem, so i'm
still pretty much looking for best solution here, if you could give me a
link for option kit for ms sql 2000, that'd be lovely.. mean while i'm going
try to read up on what you gave me and i also going see maybe i have that
resource kit on my CDs

assuming that i did find resource kit, is it hard to set it up? log
shipping...

Thanks in advance


"Linchi Shea" <linchi_shea (AT) NOSPAMml (DOT) com> wrote

It's correct that the SQL Server built-in log shipping with its GUI is only
supported by the Enterprise Edition (and Developer Edition, but you can't
use that for production). That's why we are talking about custom setup for
log shipping.

I might be wrong, but I guess the log shipping scripts from SQL2000 Resource
Kit only come with the book. It's worth the money.

--
Linchi Shea
linchi_shea (AT) NOSPAMml (DOT) com


"John Smith" <someone (AT) microsoft (DOT) com> wrote

Linchi

I hope I don't bother you *that* much, but here is an update

I downloaded Microsoft SQL 2000 Resource Kit from MSDN site and I did find
Log Shipper, it's called Simple Log Shipper (SLS). I'm was reading all
documentation today all day long and still wasn't able to set it up yet..

I'm don't know if you familiar with this SLS but I was kinda of hoping you
would, or maybe someone else would help me out here..

so here is what I've done so far, and where did it take me..

I installed sp_ShipLog on primary and sp_ApplyStandbyLog on secondary
servers. I'm trying to run a sp_ShipLog on primary server now and I get
these errors:

Backing up n to DISK=\\db2d\SharedDocs\\n_20031208_0515_LOG.BAK
BACKUP LOG successfully processed 0 pages in 0.048 seconds (0.000 MB/sec).
Execute [db2d].master.dbo.sp_ApplyStandByLog
N'n',N'\\db2d\SharedDocs\\n_20031208_0515_LOG.BAK' ,N'c:\n_undo.dat'
Server: Msg 7202, Level 11, State 2, Line 1
Could not find server 'db2d' in sysservers. Execute sp_addlinkedserver to
add the server to sysservers.
Server: Msg 50000, Level 19, State 1, Procedure sp_ShipLog, Line 85
sp_ShipLog Error 7202 occurred on database n to server db2d using backup
file \\db2d\SharedDocs\\n_20031208_0515_LOG.BAK

parameters that I've specify while running sp_ShipLog is

exec sp_ShipLog
@DBName='n',
@StandbyServer='db2d',
@BackupLocationPath='\\db2d\SharedDocs\',
@UndoFile='c:\n_undo.dat',
@MinuteInterval=5,
@HourDuration=12


I get those errors, backup file on remote server (secondary) seems to be
creating even though I get all those errors, however it does not restore
this database on secondary server.

any ideas what those erros means and what am I meansing, and how do I get it
to work?


Thanks in advance



"Linchi Shea" <linchi_shea (AT) NOSPAMml (DOT) com> wrote

better yet


Executed as user: DB2C\Administrator. Backing up t to
DISK=\\db2d\c$\t_20031208_0645_LOG.BAK [SQLSTATE 01000] (Message 0) BACKUP
LOG successfully processed 0 pages in 0.043 seconds (0.000 MB/sec).
[SQLSTATE 01000] (Message 3014) Execute
[db2d].master.dbo.sp_ApplyStandByLog
N't',N'\\db2d\c$\t_20031208_0645_LOG.BAK',N'c:\t_u ndo.dat' [SQLSTATE 01000]
(Message 0) Could not find server 'db2d' in sysservers. Execute
sp_addlinkedserver to add the server to sysservers. [SQLSTATE 42000] (Error
7202). The step failed.

i might have passed that error that i had before but i'm stuck on new one..



"John Smith" <someone (AT) microsoft (DOT) com> wrote