Re: Migrating logs to SAN
- From: GJP, NY <GJPNY@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 7 May 2008 12:44:12 -0700
Sorry: I should have specified that we're running SQL 2000. Any thoughts there?
Also, could you amplify how database IDs might come into play?
"Hilary Cotter" wrote:
In SQL 2008 full-text catalogs can be log shipped or mirrored..
In SQL 2005 this might work as long as the same drive structure is observed,
and you have the same database IDs.
"GJP, NY" <GJP, NY@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A9D4934-F197-4460-8061-E64E39A5A052@xxxxxxxxxxxxxxxx
Our IT department wants to achieve automatic server replication for our
SQL
Server host via SAN.
As our server is now configured, all logs are on a local drive, which
creates replicability problems. The server is running dozens of databases
with many, many full-text indexes. We'd like migrate the logs from the
local
drive to a SAN device without having to rebuild/repopulate the FTIs, which
would not be a trivial undertaking.
I'm wondering if subscribers to this group have any insight into whether
it
would be feasible to:
1) Stop the SQL server
2) Do a bit-level copy of the local drive containing the logs to a SAN
drive
3) Assign the local drive a new ID.
4) Assign the SAN device the drive letter previously claimed by the local
drive
5) Start SQL server
It seems that this would be a way to enable SAN-based SQL server
replication
without having to tear down and rebuild all our indexes.
- References:
- Re: Migrating logs to SAN
- From: Hilary Cotter
- Re: Migrating logs to SAN
- Prev by Date: RE: Data Replication Options (SQL Server 2005)
- Next by Date: Add Article and Snapshot Just That One Article to Subscriber
- Previous by thread: Re: Migrating logs to SAN
- Next by thread: Syncronization job
- Index(es):
Relevant Pages
|
