Mirroring between SP1 and SP2 for rolling upgrade

Is database mirroring compatible between SQL Server 2005 (Standard Edition) SP1 and SP2? I currently run SP1, and will shortly be introducing a failover partner. I'd like to have the failover partner installed as SP2, start the mirroring, manually failover, then upgrade the existing server to SP2 as well.

Is this a supported upgrade method, or will I need to upgrade the existing server to SP2 before setting up database mirroring? The SP2 installation instructions and readme file don't appear to mention mirroring at all (at least not that I can find).

Many thanks for any assistance.

Yes it will work, but for better practice can you mention what is reason for not applying SP2 on principal server?|||The intention is to upgrade the principal server to SP2 once the database has failed over to the mirror. This particular database server is constrained by SLAs for downtime (including scheduled downtime), so I would far prefer to failover to the new mirror running SP2, and then upgrade the existing server to SP2.|||

How to install service packs and hotfixes on an instance of SQL Server 2005 that is configured to use database mirroring

http://support.microsoft.com/kb/926824

Hope this helps
Vishal

Migration from 7 to 2000

Hello,
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
Arto Ylikotila arto.ylikotila@.santamargarita.fiThere is always a possibility, but it is unlikely that you need to do any si
gnificant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converte
d the constant side to the column
side. Today, SQL Server does the conversions according to the documented "da
tatype precedence" in Books
Online.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books[vbcol=seagreen]
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...|||Hi,
SQL 7.0 Backups are fully compatible with SQL 2000.
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends
MDAC versions > 2.6x.
We had several problems with clients that has mdac versions < 2.6x (speciall
y sql servers with multiple instances and also have some localization probl
ems).
Regards..

Migration from 7 to 2000

Hello,
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
Arto Ylikotila arto.ylikotila@.santamargarita.fi
There is always a possibility, but it is unlikely that you need to do any significant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converted the constant side to the column
side. Today, SQL Server does the conversions according to the documented "datatype precedence" in Books
Online.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>
|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books[vbcol=seagreen]
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
|||Hi,
SQL 7.0 Backups are fully compatible with SQL 2000.
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends MDAC versions > 2.6x.
We had several problems with clients that has mdac versions < 2.6x (specially sql servers with multiple instances and also have some localization problems).
Regards..

Migration from 7 to 2000

Hello,
How compatible is database Backup from MSSQL 7 to 2000?
Database has a lot of Procedures. Can there be syntax Problems?
Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
Regards,
Arto
--
Arto Ylikotila arto.ylikotila@.santamargarita.fiThere is always a possibility, but it is unlikely that you need to do any significant code changes, if at all.
One thing is datatype comparisons in WHERE clause, where SQL Server converted the constant side to the column
side. Today, SQL Server does the conversions according to the documented "datatype precedence" in Books
Online.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How compatible is database Backup from MSSQL 7 to 2000?
> Database has a lot of Procedures. Can there be syntax Problems?
> Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)
> Regards,
> Arto
> --
> Arto Ylikotila arto.ylikotila@.santamargarita.fi
>|||Another issue I know is replacement of all SUSER_NAME calls with
SUSER_SNAME; if you use direct queries to syslogins and sysusers system
tables then you should replace joins made by id with joins made by sid (but
better use system procedures instead)
Database backup from MSSQL7 fully compatible with 2000... moreover you may
attach DB from MSSQL7 directly to MSSQL2000, and all the needed internal
changes will be made by MSSQL2000 itself. Note that you won't be able to
attach DB back onto MSSQL7 after using it as 2000's DB. Same thing with
2000's backups - they can't be restored with MSSQL7 engine
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u5QWmD0NEHA.680@.TK2MSFTNGP11.phx.gbl...
> There is always a possibility, but it is unlikely that you need to do any
significant code changes, if at all.
> One thing is datatype comparisons in WHERE clause, where SQL Server
converted the constant side to the column
> side. Today, SQL Server does the conversions according to the documented
"datatype precedence" in Books
> Online.
> "Arto Ylikotila" <arto.ylikotila@.santamargarita.fi> wrote in message
> news:%23GX1XB0NEHA.3380@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > How compatible is database Backup from MSSQL 7 to 2000?
> > Database has a lot of Procedures. Can there be syntax Problems?
> >
> > Should I change ODBC 3.70 to ODBC 2000 (Sql server versions)|||Hi
SQL 7.0 Backups are fully compatible with SQL 2000
For SQL 2000 (I assume that SP3a and post fixes are applied ) MS recommends MDAC versions > 2.6x
We had several problems with clients that has mdac versions < 2.6x (specially sql servers with multiple instances and also have some localization problems)
Regards.