Help Needed - How Can I Set Up a Backup SQL Server Machine as an Exact Copy of My Producti

Any help would be greatly appreciated.

My problem is that I need to set up a backup SQL Server 2000 machine
which can be used in case of a failure to my primary. All databases
(30 as of now) must be an up to the minute exact copy of production
and include most recent changes in data as well as any structure
changes (Tables, Views, SP's, Triggers, Users . . etc).

When I tried this using Transactional Replication, the replication
process gets fouled up once I introduce any kind of structure changes
to the DB. I've considered the idea of doing periodic backups and
restoring it to my backup SQL server, but this does not give me the
concurrency needed with 0 latency.

I've seen articles that recommend using Transaction Replication with
'Scheduled Table Refresh', and also doing database dumps to restore on
the backup machine, but I have not been able to find any documentation
regarding this to try out. How can I implement this type of backup
strategy in SQL 2000?"Michael Orlando" <mjorlando@.campsystems.com> wrote in message
news:354e82fa.0310301256.12671603@.posting.google.c om...
> Any help would be greatly appreciated.
> My problem is that I need to set up a backup SQL Server 2000 machine
> which can be used in case of a failure to my primary. All databases
> (30 as of now) must be an up to the minute exact copy of production
> and include most recent changes in data as well as any structure
> changes (Tables, Views, SP's, Triggers, Users . . etc).

Clustering.

Though technically that's not a copy.

> When I tried this using Transactional Replication, the replication
> process gets fouled up once I introduce any kind of structure changes
> to the DB. I've considered the idea of doing periodic backups and
> restoring it to my backup SQL server, but this does not give me the
> concurrency needed with 0 latency.

If you use transactional replication you have to use sp_repladdcolumn and
sp_repldropcolumn for adding dropping columns. All other schema changes
generally have to be run against both copies.

Note also there's no guarantee as to the latency that Transactional
replication will introduce.

Log shipping will allow exact copies, but again with a built in latency.

I'd recommend picking up "SQL Server 2000 High Availability " from MS Press
and reading that.

> I've seen articles that recommend using Transaction Replication with
> 'Scheduled Table Refresh', and also doing database dumps to restore on
> the backup machine, but I have not been able to find any documentation
> regarding this to try out. How can I implement this type of backup
> strategy in SQL 2000?|||mjorlando@.campsystems.com (Michael Orlando) wrote in message news:<354e82fa.0310301256.12671603@.posting.google.com>...
> Any help would be greatly appreciated.
> My problem is that I need to set up a backup SQL Server 2000 machine
> which can be used in case of a failure to my primary. All databases
> (30 as of now) must be an up to the minute exact copy of production
> and include most recent changes in data as well as any structure
> changes (Tables, Views, SP's, Triggers, Users . . etc).
> When I tried this using Transactional Replication, the replication
> process gets fouled up once I introduce any kind of structure changes
> to the DB. I've considered the idea of doing periodic backups and
> restoring it to my backup SQL server, but this does not give me the
> concurrency needed with 0 latency.
> I've seen articles that recommend using Transaction Replication with
> 'Scheduled Table Refresh', and also doing database dumps to restore on
> the backup machine, but I have not been able to find any documentation
> regarding this to try out. How can I implement this type of backup
> strategy in SQL 2000?

What exactly do you mean by 'up to the minute'? The only other
'instant' alternative to transactional replication is clustering,
which would also avoid your schema change issues.

I don't know much about replication myself, so you might want to post
to microsoft.public.sqlserver.replication with your backup question.
Also, have a look at the October 2003 issue of SQL Server Magazine,
which had a number of articles on various high-availability solutions.

Simon

Help Moving a Database, Associated Logins and Objects

Hello. Newbie here....
I am attempting to move a database, logins, objects from 7 to 2000.
I've tried the copy database wizard, but it gives me a "failed to
create the share OMWWIZE" error.
I've search the MSDN, but the only solution says there are problems
with permissions. I've logged in as SA on both boxes...
Please help, I'm new to this and confused.A likely cause of the error is that the MSSQLServer service account does not
have permissions to the share. However, it's a fairly simple task to do
this manually using the following steps:
1) make note of the existing file locations:
EXEC sp_helpdb 'MyDatabase'
2) detach database
EXEC sp_detach_db 'MyDatabase'
3) copy database files to new location
4) attach database files from new location:
EXEC sp_attach_db 'MyDatabase',
'E:\MyDbDataFiles\MyDatabase.mdf',
'F:\MyDbLogFiles\MyDatabase_Log.ldf'
See http://support.microsoft.com/support/kb/articles/Q224/0/71.ASP for more
information.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"JD" <whatchoogot@.hotmail.com> wrote in message
news:b809817a.0311260547.44aeaefe@.posting.google.com...
> Hello. Newbie here....
> I am attempting to move a database, logins, objects from 7 to 2000.
> I've tried the copy database wizard, but it gives me a "failed to
> create the share OMWWIZE" error.
> I've search the MSDN, but the only solution says there are problems
> with permissions. I've logged in as SA on both boxes...
> Please help, I'm new to this and confused.

Help me to restore this database!!!

Hi,
I have a database named 'ePos' and i want to make
a copy from it by backup this database then restore
it as a new one with another name.
I use this commands:

sp_addumpdevice 'disk',
'ePosTest1',
'c:\test1.bak'

BACKUP DATABASE ePos TO ePosTest1 WITH INIT
GO

RESTORE DATABASE ePos_new FROM ePosTest1
GO

I have this error when restoring :
Server: Msg 1834, Level 16, State 1, Line 7
The file 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\ePos2006.mdf' cannot be overwritten. It is being used by database 'ePos2006'.

How can i restore the database with new filesys? how i can fix this problem?

PLZ help.

Regards.

For best results, try posting this in a different forum more related to your issue. At the top of the screen, you will see the forum hierarchy. (MSDN Forums >> SQL Server >> SQL Server Integration Services...) Click on the SQL Server part of that tree to see the full list of forums related to SQL Server.

I'd suggest trying the disaster recovery forums.|||This thread was originally posted in SSIS forum...moved to Disaster Recovery and Availability|||

By default, SQL backups are restored to the same path as the original database.

In your case, you want to have the same content in different files, so you'll need to use the WITH MOVE clause:

RESTORE DATABASE ePosNew FROM ePosTest1

WITH MOVE 'ePos2006' TO 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\ePosNew.mdf' ,

MOVE 'ePos2006_log' TO 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\ePosNew_log.ldf'

go

You'll have to verify the logical names of your data and log files, but this is the technique.