Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time o
f
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) o
r
maybe exist a better way to do it.
What can you advice me?
Thanks
RodrigoBackups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
David Portas
SQL Server MVP
--|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:

> Have a look at this article: http://vyaskn.tripod.com/moving_sql...skn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in messag
e
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
>
>sql

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time of
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) or
maybe exist a better way to do it.
What can you advice me?
Thanks
Rodrigo
Backups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
David Portas
SQL Server MVP
|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo
|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:

> Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
>
>

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time of
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) or
maybe exist a better way to do it.
What can you advice me?
Thanks
RodrigoBackups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
--
David Portas
SQL Server MVP
--|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:
> Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> > Hello.
> >
> > I'm going to migrate an entrie SQL Server to a new box. The original plan
> > was to backup and restore all DBs on the new server, but due the long time
> > of
> > the backup I'd like to try other way.
> >
> > I'm thinking of simply offline->copy->attach .MDF to the new server, but
> > as
> > the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> > a
> > simple attach is risk-free (basically in terms of systables/sysprocedures)
> > or
> > maybe exist a better way to do it.
> >
> > What can you advice me?
> >
> > Thanks
> > Rodrigo
>
>sql

Database Maintenence Plan Error

When trying to setup a Database Maintenence Plan, it does not give me
an option for amount of days to keep before deleting, the dropdown box
is empty. also, I set the UNC path and when I go out and come back
into the plan, this is empty, but the backup runs with 17055 errors.
How can I find out how to correct this?
RickRick,
What build of SQL2005 are you running?
Chris
"Rick" <drummer10980@.gmail.com> wrote in message
news:1189777049.876020.129450@.y42g2000hsy.googlegroups.com...
> When trying to setup a Database Maintenence Plan, it does not give me
> an option for amount of days to keep before deleting, the dropdown box
> is empty. also, I set the UNC path and when I go out and come back
> into the plan, this is empty, but the backup runs with 17055 errors.
> How can I find out how to correct this?
> Rick
>|||Actually running MSDE
Rick
On Sep 14, 9:52 am, "Chris Wood" <anonym...@.microsoft.com> wrote:
> Rick,
> What build of SQL2005 are you running?
> Chris
> "Rick" <drummer10...@.gmail.com> wrote in message
> news:1189777049.876020.129450@.y42g2000hsy.googlegroups.com...
>
> > When trying to setup a Database Maintenence Plan, it does not give me
> > an option for amount of days to keep before deleting, the dropdown box
> > is empty. also, I set the UNC path and when I go out and come back
> > into the plan, this is empty, but the backup runs with 17055 errors.
> > How can I find out how to correct this?
> > Rick- Hide quoted text -
> - Show quoted text -

Database Maintenance Planner

RE: Sql Server 2000
I am using the EM DB Maintenance Planner to set up maintenance for several
db's. In the dialog box I have checked 'yes' to 'Reorganize Data and Index
Pages' and 'Check DB Integrity', and also 'yes' to 'Perform these Checks
before doing Backups'. The dialog box then want's a time for doing these 'DB
Inegrity Checks, and I enter an appropriate, daily time.
Question: But later on in the dialog box it also asks for the time to do
daily Backups. Does this mean that I need to schedule enough time between
the 'DB integrity checks' and the 'Backup' to ensure Sql Server has enough
time to do the 'DB ingegrity checks'? Or does Sql Server ignore any time I
have entered for the 'DB Integrity Checks' since I have also checked 'Perform
these Checks before doing Backups'? If there is not enough time for Sql
Server to do the Integrity checks before the backup time, does it interrupt
the integrity checks to do the backup?
Thanks in advance for any clarification you can provide ...
bill
Thank you, Tibor ...
I decided to take your advise and uncheck the option that requires the db
integrity checks before each backup - I still run these checks, but way
ahead of the backups.
Thanks for your help ...
bill
"Tibor Karaszi" wrote:

> I don't think DBCC CHECKDB will block each other if you run two at the same time. But I don't have a
> 2000 instance with a database with enough size to test this (CHECKDB is largely re-written for
> 2005). But you can do that, having two windows size by size and executing at the same time.
> Agent or xp_sqlmaint (sqlmaint.exe) doesn't really care what commands are executed, so don't expect
> any intelligent handling at that level. I don't like the checkdb before backup option. Especially if
> you do log backups - you don't want to run a checkdb every 10 minutes...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "WCM" <WCM@.discussions.microsoft.com> wrote in message
> news:D25BD068-A8F3-440E-BF13-6CAF83DA0EDF@.microsoft.com...
>
>

Database Maintenance Plan - Update Data Optimization

Should we check the box "Reorganize data and index pages" on Database
Maintenance Plan wizard ? What's the benefit ?
Thanks.This will essentially do a DBCC DBREINDEX on each of your tables (assuming a
clustered index exists) and non-clustered indexes. See DBCC DBREINDEX in
BooksOnLine and
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/maintain/Optimize/SS2KIDBP.asp
for more details.
Andrew J. Kelly
SQL Server MVP
"John Smith" <someone@.nospam.com.us> wrote in message
news:Ogr%23fQOnDHA.2268@.TK2MSFTNGP12.phx.gbl...
> Should we check the box "Reorganize data and index pages" on Database
> Maintenance Plan wizard ? What's the benefit ?
> Thanks.
>|||And if you are running a 24x7 critical application that really must be
available all the time, you should be very careful with that check box. DBCC
DBREINDEX is not an 'online' operation (from the end user perspective) -- it
can result in severe blocking on a large table, making the table effectively
not available to the end user.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"John Smith" <someone@.nospam.com.us> wrote in message
news:Ogr%23fQOnDHA.2268@.TK2MSFTNGP12.phx.gbl...
> Should we check the box "Reorganize data and index pages" on Database
> Maintenance Plan wizard ? What's the benefit ?
> Thanks.
>