Migrating databases SQL 2000 to SQL 2005

What sort of problems can I expect when moving my SQL 2000 databases to the
SQL 2005 platform?
Must there be an adaption of code for some of the objects (sp, view, udf
etc), or will it work fine when I put the database compatibility level to 8.0?
MCDBA 2000
MCSE 2000
Everything that you need to know about upgrade issues with an existing
database can be found in the Upgrade Advisor. Download it, point it at your
SQL Server 2000 database, and have it scan it. The report and documentation
are very comprehensive.
http://www.microsoft.com/downloads/d...displaylang=en
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"G Brander" <GBrander@.discussions.microsoft.com> wrote in message
news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> What sort of problems can I expect when moving my SQL 2000 databases to
> the
> SQL 2005 platform?
> Must there be an adaption of code for some of the objects (sp, view, udf
> etc), or will it work fine when I put the database compatibility level to
> 8.0?
> --
> MCDBA 2000
> MCSE 2000
>
|||Thanks for your answer, but I am not talking about instances, but databases.
I want to migrate several SQL Server 2000 databases to a SQL Server 2005
database server. I do not want to upgrade my SQL Server 2000 instance tot SQL
Server 2005.
MCDBA 2000
MCSE 2000
"Michael Hotek" wrote:

> Everything that you need to know about upgrade issues with an existing
> database can be found in the Upgrade Advisor. Download it, point it at your
> SQL Server 2000 database, and have it scan it. The report and documentation
> are very comprehensive.
> http://www.microsoft.com/downloads/d...displaylang=en
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
> news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
>
>
|||On Mon, 13 Feb 2006 04:26:16 -0800, G Brander wrote:

>What sort of problems can I expect when moving my SQL 2000 databases to the
>SQL 2005 platform?
>Must there be an adaption of code for some of the objects (sp, view, udf
>etc), or will it work fine when I put the database compatibility level to 8.0?
Hi G,
I just posted a reply to your question in the Dutch group
microsoft.public.nl.sql.
Hugo Kornelis, SQL Server MVP

Migrating databases SQL 2000 to SQL 2005

What sort of problems can I expect when moving my SQL 2000 databases to the
SQL 2005 platform?
Must there be an adaption of code for some of the objects (sp, view, udf
etc), or will it work fine when I put the database compatibility level to 8.0?
--
MCDBA 2000
MCSE 2000Everything that you need to know about upgrade issues with an existing
database can be found in the Upgrade Advisor. Download it, point it at your
SQL Server 2000 database, and have it scan it. The report and documentation
are very comprehensive.
http://www.microsoft.com/downloads/details.aspx?familyid=451FBF81-AB07-4CCB-A18B-DA38F6BCF484&displaylang=en
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> What sort of problems can I expect when moving my SQL 2000 databases to
> the
> SQL 2005 platform?
> Must there be an adaption of code for some of the objects (sp, view, udf
> etc), or will it work fine when I put the database compatibility level to
> 8.0?
> --
> MCDBA 2000
> MCSE 2000
>|||Thanks for your answer, but I am not talking about instances, but databases.
I want to migrate several SQL Server 2000 databases to a SQL Server 2005
database server. I do not want to upgrade my SQL Server 2000 instance tot SQL
Server 2005.
--
MCDBA 2000
MCSE 2000
"Michael Hotek" wrote:
> Everything that you need to know about upgrade issues with an existing
> database can be found in the Upgrade Advisor. Download it, point it at your
> SQL Server 2000 database, and have it scan it. The report and documentation
> are very comprehensive.
> http://www.microsoft.com/downloads/details.aspx?familyid=451FBF81-AB07-4CCB-A18B-DA38F6BCF484&displaylang=en
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
> news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> > What sort of problems can I expect when moving my SQL 2000 databases to
> > the
> > SQL 2005 platform?
> >
> > Must there be an adaption of code for some of the objects (sp, view, udf
> > etc), or will it work fine when I put the database compatibility level to
> > 8.0?
> > --
> > MCDBA 2000
> > MCSE 2000
> >
>
>|||On Mon, 13 Feb 2006 04:26:16 -0800, Gé Brander wrote:
>What sort of problems can I expect when moving my SQL 2000 databases to the
>SQL 2005 platform?
>Must there be an adaption of code for some of the objects (sp, view, udf
>etc), or will it work fine when I put the database compatibility level to 8.0?
Hi Gé,
I just posted a reply to your question in the Dutch group
microsoft.public.nl.sql.
--
Hugo Kornelis, SQL Server MVP

Migrating databases SQL 2000 to SQL 2005

What sort of problems can I expect when moving my SQL 2000 databases to the
SQL 2005 platform?
Must there be an adaption of code for some of the objects (sp, view, udf
etc), or will it work fine when I put the database compatibility level to 8.
0?
--
MCDBA 2000
MCSE 2000Everything that you need to know about upgrade issues with an existing
database can be found in the Upgrade Advisor. Download it, point it at your
SQL Server 2000 database, and have it scan it. The report and documentation
are very comprehensive.
http://www.microsoft.com/downloads/...&displaylang=en
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"G Brander" <GBrander@.discussions.microsoft.com> wrote in message
news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> What sort of problems can I expect when moving my SQL 2000 databases to
> the
> SQL 2005 platform?
> Must there be an adaption of code for some of the objects (sp, view, udf
> etc), or will it work fine when I put the database compatibility level to
> 8.0?
> --
> MCDBA 2000
> MCSE 2000
>|||Thanks for your answer, but I am not talking about instances, but databases.
I want to migrate several SQL Server 2000 databases to a SQL Server 2005
database server. I do not want to upgrade my SQL Server 2000 instance tot SQ
L
Server 2005.
--
MCDBA 2000
MCSE 2000
"Michael Hotek" wrote:

> Everything that you need to know about upgrade issues with an existing
> database can be found in the Upgrade Advisor. Download it, point it at yo
ur
> SQL Server 2000 database, and have it scan it. The report and documentati
on
> are very comprehensive.
> http://www.microsoft.com/downloads/...&displaylang=en
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
> news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
>
>|||On Mon, 13 Feb 2006 04:26:16 -0800, G Brander wrote:
[vbcol=seagreen]
>What sort of problems can I expect when moving my SQL 2000 databases to the
>SQL 2005 platform?
>Must there be an adaption of code for some of the objects (sp, view, udf
>etc), or will it work fine when I put the database compatibility level to 8.0?[/vbc
ol]
Hi G,
I just posted a reply to your question in the Dutch group
microsoft.public.nl.sql.
Hugo Kornelis, SQL Server MVP

Migrating AS/400 DB2 to SQL Server

The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
Thx
You're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:

> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx

Migrating AS/400 DB2 to SQL Server

The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx

Migrating AS/400 DB2 to SQL Server

The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving year
s
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same a
s
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It wa
s
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:

> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 o
n
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving ye
ars
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should kn
ow
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in t
he
> 400. Each of those contain files and logicals. Files look to be the same
as
> a tables and logicals look to be the same as views.
> Thx

migrate report history to another server

All,
I'm looking into the ability to move a report and it's history from one
reporting server to another. Moving the reporting is no problem, but I am
not having any luck in finding a way to move the associated historical
reports. I have used RSScripter to move reports, but the history does not
migrate. I was hoping to migrate the report history programmatically, but
I'm not seeing anything that suggests it is possible short of moving the
entire Reporting Services database. Has anyone moved historical reports
between Reporting Service servers?
Thanks,
RobertRMac,
There is a way to do this, I have done it. It involves creating some DTS
Packages though. Here are the steps that I did and it worked great:
First thing you need to do is go into the Catalog Table in the ReportServer
database and find the report that you are working with (the one that has all
of the history). This report will have an 'ItemID'. You will need this
ItemID to use in queries in the DTS packages.
Once you have the ItemID you can run a query against the History Table to
find all of the SnapShotDataID's, like this:
select * from dbo.history
where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}'
Create a DTS Package, using this query, to export the history items from the
old server to the new one. Your history records will now be in the new
server History table.
Next, create another DTS Package, using a query similar to this one:
select * from dbo.SnapShotData
where snapshotdataid in
(select snapshotdataid from dbo.history
where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
With this DTS package you are going to export out all of the SnapShotData
Table information from the old server to the new one.
Next DTS package will use a query similar to this one:
select * from dbo.ChunkData
where snapshotdataid in
(select snapshotdataid from dbo.history
where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
The ChunkData table is the table that actually contains the image files (or
snapshots) of the reports. Once you have the History table, SnapShotData
table and ChunkData table information moved over. You will need to run an
update query on the new server like this:
update dbo.History
set reportid = '(your new itemid from the new server catalog table)'
where reportid = '(your old itemid from the old server}'
You will need the new itemid for this previous query. Once you have
deployed the report to the new server, just go out to the Catalog table and
find the new item id. Use that in the update query above.
It sounds a lot harder than it really is. But, I have done it and this does
work.
"RMac" wrote:
> All,
> I'm looking into the ability to move a report and it's history from one
> reporting server to another. Moving the reporting is no problem, but I am
> not having any luck in finding a way to move the associated historical
> reports. I have used RSScripter to move reports, but the history does not
> migrate. I was hoping to migrate the report history programmatically, but
> I'm not seeing anything that suggests it is possible short of moving the
> entire Reporting Services database. Has anyone moved historical reports
> between Reporting Service servers?
> Thanks,
> Robert|||SandiB, this works like a champ. Thanks much!
"SandiB" wrote:
> RMac,
> There is a way to do this, I have done it. It involves creating some DTS
> Packages though. Here are the steps that I did and it worked great:
> First thing you need to do is go into the Catalog Table in the ReportServer
> database and find the report that you are working with (the one that has all
> of the history). This report will have an 'ItemID'. You will need this
> ItemID to use in queries in the DTS packages.
> Once you have the ItemID you can run a query against the History Table to
> find all of the SnapShotDataID's, like this:
> select * from dbo.history
> where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}'
> Create a DTS Package, using this query, to export the history items from the
> old server to the new one. Your history records will now be in the new
> server History table.
> Next, create another DTS Package, using a query similar to this one:
> select * from dbo.SnapShotData
> where snapshotdataid in
> (select snapshotdataid from dbo.history
> where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
> With this DTS package you are going to export out all of the SnapShotData
> Table information from the old server to the new one.
> Next DTS package will use a query similar to this one:
> select * from dbo.ChunkData
> where snapshotdataid in
> (select snapshotdataid from dbo.history
> where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
> The ChunkData table is the table that actually contains the image files (or
> snapshots) of the reports. Once you have the History table, SnapShotData
> table and ChunkData table information moved over. You will need to run an
> update query on the new server like this:
> update dbo.History
> set reportid = '(your new itemid from the new server catalog table)'
> where reportid = '(your old itemid from the old server}'
> You will need the new itemid for this previous query. Once you have
> deployed the report to the new server, just go out to the Catalog table and
> find the new item id. Use that in the update query above.
> It sounds a lot harder than it really is. But, I have done it and this does
> work.
>
> "RMac" wrote:
> > All,
> > I'm looking into the ability to move a report and it's history from one
> > reporting server to another. Moving the reporting is no problem, but I am
> > not having any luck in finding a way to move the associated historical
> > reports. I have used RSScripter to move reports, but the history does not
> > migrate. I was hoping to migrate the report history programmatically, but
> > I'm not seeing anything that suggests it is possible short of moving the
> > entire Reporting Services database. Has anyone moved historical reports
> > between Reporting Service servers?
> > Thanks,
> > Robert

migrate linked servers

Hello everyone,
I'd like to learn how I should go about moving my linked servers from on sql
server to another sql server. Has anyone done this before?
Thanks
Chieko
Hi,
Execute the script in query analyzer with text output and copy the result to
destination server and execute it.
(Script from old post)
select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
'')+char(10)+'go'
from master..sysservers
This will help you to move the linked servers, but the security credentials
you need to define manually.
Thanks
Hari
MCDBA
"Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> Hello everyone,
> I'd like to learn how I should go about moving my linked servers from on
sql
> server to another sql server. Has anyone done this before?
> Thanks
> Chieko
>
|||Thanks, I figure out that if I backed up the master database on the old
server and restored it on the new server the linked servers were add during
the restore process.
Chieko
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eDRLL3vTEHA.504@.TK2MSFTNGP11.phx.gbl...
> Hi,
>
> Execute the script in query analyzer with text output and copy the result
to
> destination server and execute it.
> (Script from old post)
> select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
> isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
> isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
> isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
> '')+char(10)+'go'
> from master..sysservers
> This will help you to move the linked servers, but the security
credentials
> you need to define manually.
> Thanks
> Hari
> MCDBA
> "Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
> news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> sql
>
|||Hi,
OK, That is also a approch. I was under the impression that you just need to
move Linked servers only.
If you restore the Master database, it will load all logins, databases,
configurations,....If
your destination server is of same configuration as source then your
solution will work well.
If the configurations is different then the restore will cause the database
to go to suspect status and
might cause the service startup failure.
Since it works fine, no need to worry.
Thanks
Hari
MCDBA
"Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
news:u#D4GAxTEHA.156@.TK2MSFTNGP12.phx.gbl...
> Thanks, I figure out that if I backed up the master database on the old
> server and restored it on the new server the linked servers were add
during[vbcol=seagreen]
> the restore process.
> Chieko
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:eDRLL3vTEHA.504@.TK2MSFTNGP11.phx.gbl...
result[vbcol=seagreen]
> to
> credentials
on
>
sql

migrate linked servers

Hello everyone,
I'd like to learn how I should go about moving my linked servers from on sql
server to another sql server. Has anyone done this before?
Thanks
ChiekoHi,
Execute the script in query analyzer with text output and copy the result to
destination server and execute it.
(Script from old post)
select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
'')+char(10)+'go'
from master..sysservers
This will help you to move the linked servers, but the security credentials
you need to define manually.
Thanks
Hari
MCDBA
"Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> Hello everyone,
> I'd like to learn how I should go about moving my linked servers from on
sql
> server to another sql server. Has anyone done this before?
> Thanks
> Chieko
>|||Thanks, I figure out that if I backed up the master database on the old
server and restored it on the new server the linked servers were add during
the restore process.
Chieko
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eDRLL3vTEHA.504@.TK2MSFTNGP11.phx.gbl...
> Hi,
>
> Execute the script in query analyzer with text output and copy the result
to
> destination server and execute it.
> (Script from old post)
> select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
> isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
> isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
> isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
> '')+char(10)+'go'
> from master..sysservers
> This will help you to move the linked servers, but the security
credentials
> you need to define manually.
> Thanks
> Hari
> MCDBA
> "Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
> news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> > Hello everyone,
> > I'd like to learn how I should go about moving my linked servers from on
> sql
> > server to another sql server. Has anyone done this before?
> > Thanks
> > Chieko
> >
> >
>|||Hi,
OK, That is also a approch. I was under the impression that you just need to
move Linked servers only.
If you restore the Master database, it will load all logins, databases,
configurations,....If
your destination server is of same configuration as source then your
solution will work well.
If the configurations is different then the restore will cause the database
to go to suspect status and
might cause the service startup failure.
Since it works fine, no need to worry.
--
Thanks
Hari
MCDBA
"Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
news:u#D4GAxTEHA.156@.TK2MSFTNGP12.phx.gbl...
> Thanks, I figure out that if I backed up the master database on the old
> server and restored it on the new server the linked servers were add
during
> the restore process.
> Chieko
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:eDRLL3vTEHA.504@.TK2MSFTNGP11.phx.gbl...
> > Hi,
> >
> >
> > Execute the script in query analyzer with text output and copy the
result
> to
> > destination server and execute it.
> >
> > (Script from old post)
> >
> > select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
> > isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
> > isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
> > isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
> > '')+char(10)+'go'
> > from master..sysservers
> >
> > This will help you to move the linked servers, but the security
> credentials
> > you need to define manually.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> > "Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
> > news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> > > Hello everyone,
> > > I'd like to learn how I should go about moving my linked servers from
on
> > sql
> > > server to another sql server. Has anyone done this before?
> > > Thanks
> > > Chieko
> > >
> > >
> >
> >
>

migrate linked servers

Hello everyone,
I'd like to learn how I should go about moving my linked servers from on sql
server to another sql server. Has anyone done this before?
Thanks
ChiekoHi,
Execute the script in query analyzer with text output and copy the result to
destination server and execute it.
(Script from old post)
select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
'')+char(10)+'go'
from master..sysservers
This will help you to move the linked servers, but the security credentials
you need to define manually.
Thanks
Hari
MCDBA
"Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> Hello everyone,
> I'd like to learn how I should go about moving my linked servers from on
sql
> server to another sql server. Has anyone done this before?
> Thanks
> Chieko
>|||Thanks, I figure out that if I backed up the master database on the old
server and restored it on the new server the linked servers were add during
the restore process.
Chieko
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eDRLL3vTEHA.504@.TK2MSFTNGP11.phx.gbl...
> Hi,
>
> Execute the script in query analyzer with text output and copy the result
to
> destination server and execute it.
> (Script from old post)
> select 'exec sp_addlinkedserver @.server=''' + srvname + '''' +
> isnull(', @.srvproduct=''' + nullif(srvproduct, '')+ '''', '') +
> isnull(', @.provider=''' + nullif(providername, '')+ '''', '') +
> isnull(', @.datasrc=''' + nullif(datasource, '')+ '''',
> '')+char(10)+'go'
> from master..sysservers
> This will help you to move the linked servers, but the security
credentials
> you need to define manually.
> Thanks
> Hari
> MCDBA
> "Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
> news:#o#bX8uTEHA.1244@.TK2MSFTNGP10.phx.gbl...
> sql
>|||Hi,
OK, That is also a approch. I was under the impression that you just need to
move Linked servers only.
If you restore the Master database, it will load all logins, databases,
configurations,....If
your destination server is of same configuration as source then your
solution will work well.
If the configurations is different then the restore will cause the database
to go to suspect status and
might cause the service startup failure.
Since it works fine, no need to worry.
Thanks
Hari
MCDBA
"Chieko Kuroda" <ckuroda@.unch.unc.edu> wrote in message
news:u#D4GAxTEHA.156@.TK2MSFTNGP12.phx.gbl...
> Thanks, I figure out that if I backed up the master database on the old
> server and restored it on the new server the linked servers were add
during
> the restore process.
> Chieko
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:eDRLL3vTEHA.504@.TK2MSFTNGP11.phx.gbl...
result[vbcol=seagreen]
> to
> credentials
on[vbcol=seagreen]
>

Migrate from Sql Server 2005 to Sql Server 2000

We are moving from 2000 to 2005 .And I have to come up with an escape
route if after a week or two it is decided performance/other issues
are worse.
..SSIS transfer sql server objects does not cut it for some unknown
reason with one error after the other...
Thanks for your time
massa
Just detach the database from the SQL 2000 server and then attach it to the
SQL 2005 server.
Do NOT change the database compatibility level until you are certain that
you will not move it back to the SQL 2000 server.
After attaching, update statistics and re-index.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegro ups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>
|||The database will be upgraded to the SQL 2005 on-disk format when attached
to the SQL 2005 instance. Consequently, it can't be attached back to the
SQL 2000 regardless of the database compatibility level.
Hope this helps.
Dan Guzman
SQL Server MVP
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:O$edDtE2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> Just detach the database from the SQL 2000 server and then attach it to
> the SQL 2005 server.
> Do NOT change the database compatibility level until you are certain that
> you will not move it back to the SQL 2000 server.
> After attaching, update statistics and re-index.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Massa Batheli" <mngong@.gmail.com> wrote in message
> news:1158271663.636547.75900@.b28g2000cwb.googlegro ups.com...
>
|||> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
That's the way to go back to SQL 2000. There should be a way to get more
details about the errors. Are you logging errors in your package?
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegro ups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>

Migrate from Sql Server 2005 to Sql Server 2000

We are moving from 2000 to 2005 .And I have to come up with an escape
route if after a week or two it is decided performance/other issues
are worse.
.SSIS transfer sql server objects does not cut it for some unknown
reason with one error after the other...
Thanks for your time
massaJust detach the database from the SQL 2000 server and then attach it to the
SQL 2005 server.
Do NOT change the database compatibility level until you are certain that
you will not move it back to the SQL 2000 server.
After attaching, update statistics and re-index.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>|||The database will be upgraded to the SQL 2005 on-disk format when attached
to the SQL 2005 instance. Consequently, it can't be attached back to the
SQL 2000 regardless of the database compatibility level.
Hope this helps.
Dan Guzman
SQL Server MVP
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:O$edDtE2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> Just detach the database from the SQL 2000 server and then attach it to
> the SQL 2005 server.
> Do NOT change the database compatibility level until you are certain that
> you will not move it back to the SQL 2000 server.
> After attaching, update statistics and re-index.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Massa Batheli" <mngong@.gmail.com> wrote in message
> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>>
>> We are moving from 2000 to 2005 .And I have to come up with an escape
>> route if after a week or two it is decided performance/other issues
>> are worse.
>> .SSIS transfer sql server objects does not cut it for some unknown
>> reason with one error after the other...
>>
>> Thanks for your time
>> massa
>|||> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
That's the way to go back to SQL 2000. There should be a way to get more
details about the errors. Are you logging errors in your package?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>|||Dan Guzman wrote:
> > .SSIS transfer sql server objects does not cut it for some unknown
> > reason with one error after the other...
> That's the way to go back to SQL 2000. There should be a way to get more
> details about the errors. Are you logging errors in your package?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Massa Batheli" <mngong@.gmail.com> wrote in message
> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
> >
> >
> > We are moving from 2000 to 2005 .And I have to come up with an escape
> > route if after a week or two it is decided performance/other issues
> > are worse.
> > .SSIS transfer sql server objects does not cut it for some unknown
> > reason with one error after the other...
> >
> >
> > Thanks for your time
> > massa
> >
let me attach the error if do not mind
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80040E37 Description: "Invalid object name
'dbo.qs_globals'.".
helpFile=dtsmsg.rll helpContext=0
idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
Task failed: Transfer SQL Server Objects Task
SSIS package "Package.dtsx" finished: Success.
It seems to have trouble recreating any tables not owned by dbo. when
that is deselected from the list it then has trouble copying any
table...
Thanks again for your time|||> It seems to have trouble recreating any tables not owned by dbo. when
> that is deselected from the list it then has trouble copying any
> table...
You might try creating SQL 2000 database users for non-dbo SQL 2005 schema
before the transfer. I'm not sure how the Transfer SQL Server Objects Task
handles schema-->owner translation when you copy from SQL 2005 to 2000.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158320760.263256.231650@.h48g2000cwc.googlegroups.com...
> Dan Guzman wrote:
>> > .SSIS transfer sql server objects does not cut it for some unknown
>> > reason with one error after the other...
>> That's the way to go back to SQL 2000. There should be a way to get more
>> details about the errors. Are you logging errors in your package?
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Massa Batheli" <mngong@.gmail.com> wrote in message
>> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>> >
>> >
>> > We are moving from 2000 to 2005 .And I have to come up with an escape
>> > route if after a week or two it is decided performance/other issues
>> > are worse.
>> > .SSIS transfer sql server objects does not cut it for some unknown
>> > reason with one error after the other...
>> >
>> >
>> > Thanks for your time
>> > massa
>> >
> let me attach the error if do not mind
> An OLE DB record is available. Source: "Microsoft SQL Native Client"
> Hresult: 0x80040E37 Description: "Invalid object name
> 'dbo.qs_globals'.".
> helpFile=dtsmsg.rll helpContext=0
> idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
> Task failed: Transfer SQL Server Objects Task
> SSIS package "Package.dtsx" finished: Success.
> It seems to have trouble recreating any tables not owned by dbo. when
> that is deselected from the list it then has trouble copying any
> table...
>
> Thanks again for your time
>|||Dan Guzman wrote:
> > It seems to have trouble recreating any tables not owned by dbo. when
> > that is deselected from the list it then has trouble copying any
> > table...
> You might try creating SQL 2000 database users for non-dbo SQL 2005 schema
> before the transfer. I'm not sure how the Transfer SQL Server Objects Task
> handles schema-->owner translation when you copy from SQL 2005 to 2000.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Massa Batheli" <mngong@.gmail.com> wrote in message
> news:1158320760.263256.231650@.h48g2000cwc.googlegroups.com...
> >
> > Dan Guzman wrote:
> >> > .SSIS transfer sql server objects does not cut it for some unknown
> >> > reason with one error after the other...
> >>
> >> That's the way to go back to SQL 2000. There should be a way to get more
> >> details about the errors. Are you logging errors in your package?
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Massa Batheli" <mngong@.gmail.com> wrote in message
> >> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
> >> >
> >> >
> >> > We are moving from 2000 to 2005 .And I have to come up with an escape
> >> > route if after a week or two it is decided performance/other issues
> >> > are worse.
> >> > .SSIS transfer sql server objects does not cut it for some unknown
> >> > reason with one error after the other...
> >> >
> >> >
> >> > Thanks for your time
> >> > massa
> >> >
> >
> > let me attach the error if do not mind
> >
> > An OLE DB record is available. Source: "Microsoft SQL Native Client"
> > Hresult: 0x80040E37 Description: "Invalid object name
> > 'dbo.qs_globals'.".
> > helpFile=dtsmsg.rll helpContext=0
> > idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
> > Task failed: Transfer SQL Server Objects Task
> > SSIS package "Package.dtsx" finished: Success.
> > It seems to have trouble recreating any tables not owned by dbo. when
> > that is deselected from the list it then has trouble copying any
> > table...
> >
> >
That was quicker than any reply I have ever had (Thanks)
I will continue to persue that path though we are migrating tomorrow .
Are you aware of any other feasible method...|||> Are you aware of any other feasible method...
Not really, but it should be reasonably easy to fall back by keeping the
original SQL 2000 database around. Script out the original database foreign
keys and truncate tables. If you make schema changes, apply the scripts to
both SQL 2000 and SQL 2005 database to keep them in sync. To revert back,
copy data back and recreate foreign keys via script.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158324606.863195.166810@.m73g2000cwd.googlegroups.com...
> Dan Guzman wrote:
>> > It seems to have trouble recreating any tables not owned by dbo. when
>> > that is deselected from the list it then has trouble copying any
>> > table...
>> You might try creating SQL 2000 database users for non-dbo SQL 2005
>> schema
>> before the transfer. I'm not sure how the Transfer SQL Server Objects
>> Task
>> handles schema-->owner translation when you copy from SQL 2005 to 2000.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Massa Batheli" <mngong@.gmail.com> wrote in message
>> news:1158320760.263256.231650@.h48g2000cwc.googlegroups.com...
>> >
>> > Dan Guzman wrote:
>> >> > .SSIS transfer sql server objects does not cut it for some
>> >> > unknown
>> >> > reason with one error after the other...
>> >>
>> >> That's the way to go back to SQL 2000. There should be a way to get
>> >> more
>> >> details about the errors. Are you logging errors in your package?
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Dan Guzman
>> >> SQL Server MVP
>> >>
>> >> "Massa Batheli" <mngong@.gmail.com> wrote in message
>> >> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>> >> >
>> >> >
>> >> > We are moving from 2000 to 2005 .And I have to come up with an
>> >> > escape
>> >> > route if after a week or two it is decided performance/other issues
>> >> > are worse.
>> >> > .SSIS transfer sql server objects does not cut it for some
>> >> > unknown
>> >> > reason with one error after the other...
>> >> >
>> >> >
>> >> > Thanks for your time
>> >> > massa
>> >> >
>> >
>> > let me attach the error if do not mind
>> >
>> > An OLE DB record is available. Source: "Microsoft SQL Native Client"
>> > Hresult: 0x80040E37 Description: "Invalid object name
>> > 'dbo.qs_globals'.".
>> > helpFile=dtsmsg.rll helpContext=0
>> > idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
>> > Task failed: Transfer SQL Server Objects Task
>> > SSIS package "Package.dtsx" finished: Success.
>> > It seems to have trouble recreating any tables not owned by dbo. when
>> > that is deselected from the list it then has trouble copying any
>> > table...
>> >
>> >
> That was quicker than any reply I have ever had (Thanks)
> I will continue to persue that path though we are migrating tomorrow .
> Are you aware of any other feasible method...
>

Migrate from Sql Server 2005 to Sql Server 2000

We are moving from 2000 to 2005 .And I have to come up with an escape
route if after a week or two it is decided performance/other issues
are worse.
.SSIS transfer sql server objects does not cut it for some unknown
reason with one error after the other...
Thanks for your time
massaJust detach the database from the SQL 2000 server and then attach it to the
SQL 2005 server.
Do NOT change the database compatibility level until you are certain that
you will not move it back to the SQL 2000 server.
After attaching, update statistics and re-index.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>|||The database will be upgraded to the SQL 2005 on-disk format when attached
to the SQL 2005 instance. Consequently, it can't be attached back to the
SQL 2000 regardless of the database compatibility level.
Hope this helps.
Dan Guzman
SQL Server MVP
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:O$edDtE2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> Just detach the database from the SQL 2000 server and then attach it to
> the SQL 2005 server.
> Do NOT change the database compatibility level until you are certain that
> you will not move it back to the SQL 2000 server.
> After attaching, update statistics and re-index.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Massa Batheli" <mngong@.gmail.com> wrote in message
> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>|||> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
That's the way to go back to SQL 2000. There should be a way to get more
details about the errors. Are you logging errors in your package?
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>

Migiration of DB from one storage sub system to another vendor

DB is 150GB and I cannot take it offline long enough to apply logs to a back up.
I am moving from one sub storage system to another.
Any mirroring ideas?
ThanksNot sure what you mean by applying the logs? You don't need to take sql
server offline to do backups. Mabye these will help:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"eudamon" <max789@.yahoo.com> wrote in message
news:cf4ef727.0401071937.136fb59d@.posting.google.com...
> DB is 150GB and I cannot take it offline long enough to apply logs to a
back up.
> I am moving from one sub storage system to another.
> Any mirroring ideas?
> Thanks|||Standard backs would work, but then I have a existing transactions on one server with sub storage system and a restored back up to a new sub storage system DB. Plus the time is takes to copy a couple 100gb. I was hoping for some way to mirror the existing DB to a new copy on the seperate storage subsystem. Hope this makes sense|||Are you talking about just a one shot deal or do you want to keep the two up
to sync all the time? If so you can use Log Shipping or replication but in
either case you need to get the whole DB there to start and that usually
involves a copy or some sort.
--
Andrew J. Kelly SQL MVP
"eudamon" <anonymous@.discussions.microsoft.com> wrote in message
news:7E1B5A95-DFC2-4A52-958D-3F411F824569@.microsoft.com...
> Standard backs would work, but then I have a existing transactions on one
server with sub storage system and a restored back up to a new sub storage
system DB. Plus the time is takes to copy a couple 100gb. I was hoping for
some way to mirror the existing DB to a new copy on the seperate storage
subsystem. Hope this makes sense|||If your're trying to move the DB files to a new storage system on the same
server then your best bet is to detach/move/re-attach the DB. If you aren't
able to be down long enough to be able to do this I think your only option
is to mess around with filegroups. Create new file(s) in an existing
filegroup on the storage system and use DBCC SHRINKFILE('file_name',
EMPTYFILE) which will move the data from that file to other files in the
filegroup. Or create a new filegroup with new file(s) on the new storage
system and rebuild clustered indexes specifying the new filegroup, which
will cause the table to be moved. You'll actually have to rebuild all
indexes specifying ON 'filegroup' if you use this method.
I don't believe there are any options for mirroring in SQL Server. Maybe a
third-party like Veritas has something that could mirror/unmirror live
volumes.
Mike Kruchten
"eudamon" <max789@.yahoo.com> wrote in message
news:cf4ef727.0401071937.136fb59d@.posting.google.com...
> DB is 150GB and I cannot take it offline long enough to apply logs to a
back up.
> I am moving from one sub storage system to another.
> Any mirroring ideas?
> Thanks