Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Friday, March 30, 2012

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

Wednesday, March 28, 2012

Mirror Disconnected - Database Upgraded

Hi

While a database upgrade schema changes were being made the Mirror became disconnected will this recover itself when it reconnects or will it be the case that we will have to copy the db files to the Mirror and set it up from scratch.

It was set up as a synchronise mirror

Hi Jasonmr,

What sort fo changes were you running.

What errors are logged in the error log of the mirror and principal?

regards

Jag

|||

What kind of DB mirror mode you are running?

If in high availability mode then the committed transactions will be available on Mirror provided the redo queue has been applied there, if not until unless the transaction is written to disk and tranasfered to mirror it will not be available on other server.

Friday, March 23, 2012

Minimun SP Level for Cluster Upgrade

I'm upgrading MSSQL2000 (RTM) cluster to 2005. I haven't seen any information regarding a minimum service pack level for 2000. This upgrade just makes me overly caution.

To upgrade to SQL 2005, you need to be running SQL 2000 SP3(or SP3a) at a minimum.

Thanks,

Sam Lester (MSFT)

|||

Here's the link from Books Online:

http://msdn2.microsoft.com/en-us/library/ms144245.aspx

Sam

Wednesday, March 21, 2012

Minimum config to upgrade 2000 to 2005?

I am trying to upgrade from SQL Server 2000 Developer Edition (SP4) to SQL Server 2005 Developer Edition. I want to be able to use Reporting Services in the 2005 version. But the 2005 Upgrade Advisor says:

Reporting Services is either not installed or is installed incorrectly.
- Virtual directory settings do not match the default configuration
- Custom virtual directory settings block edition upgrades
- Custom extensions are deployed on the report server
- ASP.NET account information is encrypted

What do I need to install from the 2000 product in order to be able to upgrade to the 2005 version?

You should only get this warning if one of these conditions is true. Have you verfied each one?

Here is how to check:

1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

2) Did you modify the config file to add any custom extensions?

3) Is your machine.config file set to encrypt the asp.net account password?

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

|||

Daniel, thanks for your help. I'm on the (very) low end of experience with all this.

>1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

I uninstalled all SQL Server components (both 2005 and 2000) and then reinstalled 2000, 2000 SP4 and 2005. So, it seems like the answer here is no.

>2) Did you modify the config file to add any custom extensions?

I don't think so. Where should I look?

>3) Is your machine.config file set to encrypt the asp.net account password?

Where should I look for this file? (I guess the fact that I'm even asking this implies I have not messed with it ... but don't assume too much.)

>If you check all of this and still can't find the issue, you can always uninstall RS

I don't think it was ever installed in the first place.

|||It sounds like you are just trying to install RS2005. You do not need to install RS 2000 to get RS2005. Just install 2005.|||

Daniel Reib wrote:

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

I have a case where I need to upgrade both the DB and the RS from 2000 to 2005. The procedure above seem to work great except from one thing - I don't know how to transfer the encryption keys. I have made the keyfile with rskeymgmt but in the 2005 config screen i get an error when trying to restore the encryption keys:

ReportServicesConfigUI.WMIProvider.WMIProviderException: Could not find stored procedure 'SetKeysForInstallation'.
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.RestoreEncryptionKey(Byte[] encryptedBytes, String password)

Anyone knows what this means?

Regards,

|||This procedure was added for RS2005. It appears like you are still pointing to your RS 2000 db or it has not upgraded correctly.|||

Still pointing to the RS 2000 db, isn't that what you say we should do? And RS 2005 will upgrade the schema? That step reported no errors whatsoever..

|||When you point to the 2000 DB the config tool should tell you that it is upgrading. If it did not you can always script the upgrade (using the config tool) and then just run the scripts.|||

That step didn't report any errors, it worked out great. The only config step I still have problems with is Encryption Keys (which reports the error I posted earlier) and Initialization (reports an x in the icon, and I'm not able to click it. It's grayed out).

I tried the following now:

C:\Documents and Settings\Administrator>rskeymgmt -a -fdesktop\keys.snk -ppassword

Could not find stored procedure 'SetKeysForInstallation'.

C:\Documents and Settings\Administrator>


Which is basicly the same error as I posted earlier... any idea of what step I've missed that can cause this? I see that it's true.. there is no sp names SetKeysForInstallation in the db..

Minimum config to upgrade 2000 to 2005?

I am trying to upgrade from SQL Server 2000 Developer Edition (SP4) to SQL Server 2005 Developer Edition. I want to be able to use Reporting Services in the 2005 version. But the 2005 Upgrade Advisor says:

Reporting Services is either not installed or is installed incorrectly.
- Virtual directory settings do not match the default configuration
- Custom virtual directory settings block edition upgrades
- Custom extensions are deployed on the report server
- ASP.NET account information is encrypted

What do I need to install from the 2000 product in order to be able to upgrade to the 2005 version?

You should only get this warning if one of these conditions is true. Have you verfied each one?

Here is how to check:

1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

2) Did you modify the config file to add any custom extensions?

3) Is your machine.config file set to encrypt the asp.net account password?

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

|||

Daniel, thanks for your help. I'm on the (very) low end of experience with all this.

>1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

I uninstalled all SQL Server components (both 2005 and 2000) and then reinstalled 2000, 2000 SP4 and 2005. So, it seems like the answer here is no.

>2) Did you modify the config file to add any custom extensions?

I don't think so. Where should I look?

>3) Is your machine.config file set to encrypt the asp.net account password?

Where should I look for this file? (I guess the fact that I'm even asking this implies I have not messed with it ... but don't assume too much.)

>If you check all of this and still can't find the issue, you can always uninstall RS

I don't think it was ever installed in the first place.

|||It sounds like you are just trying to install RS2005. You do not need to install RS 2000 to get RS2005. Just install 2005.|||

Daniel Reib wrote:

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

I have a case where I need to upgrade both the DB and the RS from 2000 to 2005. The procedure above seem to work great except from one thing - I don't know how to transfer the encryption keys. I have made the keyfile with rskeymgmt but in the 2005 config screen i get an error when trying to restore the encryption keys:

ReportServicesConfigUI.WMIProvider.WMIProviderException: Could not find stored procedure 'SetKeysForInstallation'.
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.RestoreEncryptionKey(Byte[] encryptedBytes, String password)

Anyone knows what this means?

Regards,

|||This procedure was added for RS2005. It appears like you are still pointing to your RS 2000 db or it has not upgraded correctly.|||

Still pointing to the RS 2000 db, isn't that what you say we should do? And RS 2005 will upgrade the schema? That step reported no errors whatsoever..

|||When you point to the 2000 DB the config tool should tell you that it is upgrading. If it did not you can always script the upgrade (using the config tool) and then just run the scripts.|||

That step didn't report any errors, it worked out great. The only config step I still have problems with is Encryption Keys (which reports the error I posted earlier) and Initialization (reports an x in the icon, and I'm not able to click it. It's grayed out).

I tried the following now:

C:\Documents and Settings\Administrator>rskeymgmt -a -fdesktop\keys.snk -ppassword

Could not find stored procedure 'SetKeysForInstallation'.

C:\Documents and Settings\Administrator>


Which is basicly the same error as I posted earlier... any idea of what step I've missed that can cause this? I see that it's true.. there is no sp names SetKeysForInstallation in the db..

sql

Friday, March 9, 2012

migration sql Server 2000 to sqlServer2005

hi,

i must convert my SqlServer2000 to SqlServer2005. I just do it on my Computer and i run a component "SQL Server upgrade wizard" it convert my SQLServer.
But now i must do it on my Server Web and if i run that component it give me an error : "must run SQL 6.5" and i don't installed it.

Can i download it with all right migration?

thank you

If you get such error you may have inherited a database upgraded from 6.5 to 2000 with a wizard that could be a problem because I always advice 6.5 migration should be manual done by a skilled SQL Server expert. So create a blank database and run the SSIS(sql server integration services) and the error will go away. Hope this helps.

Migration of Sql Server 7

Hi All,
Greetings,

We have
sql server 7
Sqlserver ServicePack SP3
Sort Order = 32
BuildNumber 7.00.961

on Windows NT,Now we are planning to upgrade operating system from win NT machine to windows 2000.
Please let me know what and all precausion do i need to take what and what all backup should be done apart from user database.
How do i take care of the users,logins,roles, DTS Job and Replication.

Please help me in this and also any links if u have on this topic

Waiting for reply
TIA
AdilWill you also be upgrading to SQL 2000 ?

When I moved to a new machine, we shut down SQL Server on both boxes, copied the database files to the new server and then started SQL Server. Because you are moving master you get all the login id's, etc. Just make sure you are running the same version of SQL server, otherwise it can get complicated.|||yes we are running the same version of SQL server.
pls suggest how do i go about it.

Thanks for ur reply

TIA
Adil

Wednesday, March 7, 2012

Migration from SQL 2000 to 2005

Hi

We are going to upgrade from SQL 2002 to 2005. We have approx. 100m
rows of data on the main table and hand of stored procs and views.

What we had in mind was that we would dts the data out, script the
stored procs and view out and import the it back into SQL 2005.

Is there smarter way of doing this?
The key thing is that the data must be clean

ThanksHi,

Why can't you just backup and restore the database in 2005? You can
change the compatibility level there to 90

I have done this before on dev databases and things seemed fine.

Kart

rc@.!die!.spammer.bhfshops.org.uk wrote:

Quote:

Originally Posted by

Hi
>
We are going to upgrade from SQL 2002 to 2005. We have approx. 100m
rows of data on the main table and hand of stored procs and views.
>
What we had in mind was that we would dts the data out, script the
stored procs and view out and import the it back into SQL 2005.
>
Is there smarter way of doing this?
The key thing is that the data must be clean
>
Thanks

|||I have "detached" the database on SQL 2000 and "re-attached" on SQL 2005
with no problems. You have to create the user logins and do the
sp_change_users_login.

<rc@.!die!.spammer.bhfshops.org.ukwrote in message
news:5rccj217fl7r2g5ijhh4hj4ha0nb308uvo@.4ax.com...

Quote:

Originally Posted by

Hi
>
We are going to upgrade from SQL 2002 to 2005. We have approx. 100m
rows of data on the main table and hand of stored procs and views.
>
What we had in mind was that we would dts the data out, script the
stored procs and view out and import the it back into SQL 2005.
>
Is there smarter way of doing this?
The key thing is that the data must be clean
>
Thanks

Saturday, February 25, 2012

migration from 32 bit to 64 bit

Hi, I want to upgrade a server from a 32 bit system to a 64 bit system, will
i be able to use my same license with the new server or should i need to buy
a new license for the 64 bit server?
Thanks in advance for the help.
Regards,> Hi, I want to upgrade a server from a 32 bit system to a 64 bit system,
> will
> i be able to use my same license with the new server or should i need to
> buy
> a new license for the 64 bit server?
<Excerpt href="http://links.10026.com/?link=">http://www.microsoft.com/sql/howtobuy/default.mspx">
While you should choose the platform that matches your current hardware (in
order to obtain the appropriate media), SQL Server licenses are not platform
specific. For example, if you currently have a 32-bit server and plan to
upgrade the hardware to 64 bit in the future, you can purchase a 32-bit SKU
today, and later switch to 64 bit without having to
purchase an additional license.
</Excerpt>
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Frivas" <Frivas@.discussions.microsoft.com> wrote in message
news:E1927DBA-0E12-47D1-AC7C-2A132DFFC626@.microsoft.com...
> Hi, I want to upgrade a server from a 32 bit system to a 64 bit system,
> will
> i be able to use my same license with the new server or should i need to
> buy
> a new license for the 64 bit server?
> Thanks in advance for the help.
> Regards,
>

Migration data from SQL 7.0 to SQL 2005

I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
on to of the existing 7.0 instance and perfrom a full system upgrade. What I
don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
import the SQL 7.0 database and convert it for use inder 2005? I don't want
to burn my tracks by upgrdaing the existing server. If the install goes bad,
I can't fall back if nercessary. The books online for the lates preview don't
indicate the abaility migrate data fromj 7.0 as a stand alone process
sepparate from a full upgrade.
You should be able to detach the database from SQL Server 7.0 and attach it
to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
procedures. For more information about upgrading databases from previous
versions to SQL Server 2005, see SQL Server 2005 Books Online.
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> I know that sQL 2005 support upgrading a SQL 7.0 database if you install
it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
want
> to burn my tracks by upgrdaing the existing server. If the install goes
bad,
> I can't fall back if nercessary. The books online for the lates preview
don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.
|||I have read the books online and I don't get the impression that you can
either directly attach a 7.0 database or alternatively, use the "copy
database wizard". Attempts to directly attach a SQL 7.0 database have failed
when initiated by scripts generated using the new scripting wizard. The “copy
database wizard” clearly states in its opening text that it can only be used
when copying SQL 2000 or 2005 data. There is no mention of copying SQL 7.0
data at all.
The books online recommend not using “sp_attach_db” command since it will no
longer be supported in the future. They suggest using the “CREAT DATABASE”
command in its place which is what the script generated by the wizard used.
In eaither case, the action failed.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>
|||OK, I got it to work. For some reason, scheduling the script to run via the
agent causes it to fail when executed. However, when I copied the script to
the query analyzer and executed it from there, it worked correctly.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>
|||For additional help with upgrading to SQL Server 2005 from earlier versions
of SQL Server, you may be interested in the SQL Server 2005 Upgrade Advisor:
http://www.microsoft.com/downloads/d...DisplayLang=en
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
>I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> I can't fall back if nercessary. The books online for the lates preview
> don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.

Migration data from SQL 7.0 to SQL 2005

I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
on to of the existing 7.0 instance and perfrom a full system upgrade. What I
don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
import the SQL 7.0 database and convert it for use inder 2005? I don't want
to burn my tracks by upgrdaing the existing server. If the install goes bad,
I can't fall back if nercessary. The books online for the lates preview don't
indicate the abaility migrate data fromj 7.0 as a stand alone process
sepparate from a full upgrade.You should be able to detach the database from SQL Server 7.0 and attach it
to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
procedures. For more information about upgrading databases from previous
versions to SQL Server 2005, see SQL Server 2005 Books Online.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> I know that sQL 2005 support upgrading a SQL 7.0 database if you install
it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
want
> to burn my tracks by upgrdaing the existing server. If the install goes
bad,
> I can't fall back if nercessary. The books online for the lates preview
don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.|||I have read the books online and I don't get the impression that you can
either directly attach a 7.0 database or alternatively, use the "copy
database wizard". Attempts to directly attach a SQL 7.0 database have failed
when initiated by scripts generated using the new scripting wizard. The â'copy
database wizardâ' clearly states in its opening text that it can only be used
when copying SQL 2000 or 2005 data. There is no mention of copying SQL 7.0
data at all.
The books online recommend not using â'sp_attach_dbâ' command since it will no
longer be supported in the future. They suggest using the â'CREAT DATABASEâ'
command in its place which is what the script generated by the wizard used.
In eaither case, the action failed.
"Narayana Vyas Kondreddi" wrote:
> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> > I know that sQL 2005 support upgrading a SQL 7.0 database if you install
> it
> > on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> > don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> > import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> > to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> > I can't fall back if nercessary. The books online for the lates preview
> don't
> > indicate the abaility migrate data fromj 7.0 as a stand alone process
> > sepparate from a full upgrade.
>
>|||OK, I got it to work. For some reason, scheduling the script to run via the
agent causes it to fail when executed. However, when I copied the script to
the query analyzer and executed it from there, it worked correctly.
"Narayana Vyas Kondreddi" wrote:
> You should be able to detach the database from SQL Server 7.0 and attach it
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> > I know that sQL 2005 support upgrading a SQL 7.0 database if you install
> it
> > on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> > don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> > import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> > to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> > I can't fall back if nercessary. The books online for the lates preview
> don't
> > indicate the abaility migrate data fromj 7.0 as a stand alone process
> > sepparate from a full upgrade.
>
>|||For additional help with upgrading to SQL Server 2005 from earlier versions
of SQL Server, you may be interested in the SQL Server 2005 Upgrade Advisor:
http://www.microsoft.com/downloads/details.aspx?FamilyID=cf28daf9-182e-4ac2-8e88-f2e936558bf2&DisplayLang=en
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
>I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> I can't fall back if nercessary. The books online for the lates preview
> don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.

Migration data from SQL 7.0 to SQL 2005

I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
on to of the existing 7.0 instance and perfrom a full system upgrade. What I
don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
import the SQL 7.0 database and convert it for use inder 2005? I don't want
to burn my tracks by upgrdaing the existing server. If the install goes bad,
I can't fall back if nercessary. The books online for the lates preview don'
t
indicate the abaility migrate data fromj 7.0 as a stand alone process
sepparate from a full upgrade.You should be able to detach the database from SQL Server 7.0 and attach it
to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
procedures. For more information about upgrading databases from previous
versions to SQL Server 2005, see SQL Server 2005 Books Online.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> I know that sQL 2005 support upgrading a SQL 7.0 database if you install
it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
want
> to burn my tracks by upgrdaing the existing server. If the install goes
bad,
> I can't fall back if nercessary. The books online for the lates preview
don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.|||I have read the books online and I don't get the impression that you can
either directly attach a 7.0 database or alternatively, use the "copy
database wizard". Attempts to directly attach a SQL 7.0 database have failed
when initiated by scripts generated using the new scripting wizard. The “c
opy
database wizard” clearly states in its opening text that it can only be us
ed
when copying SQL 2000 or 2005 data. There is no mention of copying SQL 7.0
data at all.
The books online recommend not using “sp_attach_db” command since it wil
l no
longer be supported in the future. They suggest using the “CREAT DATABASE
command in its place which is what the script generated by the wizard used.
In eaither case, the action failed.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach i
t
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>|||OK, I got it to work. For some reason, scheduling the script to run via the
agent causes it to fail when executed. However, when I copied the script to
the query analyzer and executed it from there, it worked correctly.
"Narayana Vyas Kondreddi" wrote:

> You should be able to detach the database from SQL Server 7.0 and attach i
t
> to SQL Server 2005 using sp_detach_db and sp_attach_db system stored
> procedures. For more information about upgrading databases from previous
> versions to SQL Server 2005, see SQL Server 2005 Books Online.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AJStein" <AJStein@.discussions.microsoft.com> wrote in message
> news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
> it
> I
> want
> bad,
> don't
>
>|||For additional help with upgrading to SQL Server 2005 from earlier versions
of SQL Server, you may be interested in the SQL Server 2005 Upgrade Advisor:
http://www.microsoft.com/downloads/...&DisplayLang=en
"AJStein" <AJStein@.discussions.microsoft.com> wrote in message
news:520F2B5E-6ECA-4EC3-90CD-643348C44A80@.microsoft.com...
>I know that sQL 2005 support upgrading a SQL 7.0 database if you install it
> on to of the existing 7.0 instance and perfrom a full system upgrade. What
> I
> don'y know is, if I set up a sepparate SQL 2005 server, is there a way to
> import the SQL 7.0 database and convert it for use inder 2005? I don't
> want
> to burn my tracks by upgrdaing the existing server. If the install goes
> bad,
> I can't fall back if nercessary. The books online for the lates preview
> don't
> indicate the abaility migrate data fromj 7.0 as a stand alone process
> sepparate from a full upgrade.

Migrating VS 2003 -> 2005

Hello all,
I'd like to upgrade VS and also SQL server with RS. I just want make
sure, if I backup all databases, uninstall SQL2000, install SQL2005,
install VS 2005 with RS - if everything will be OK.
I tried to find how to proper upgrade RS2000 to RS2005, but I dont
find anything, and I just want to be sure...
Thanks for any help!Actually you don't have to uninstall your 2000, when your run 2005 Setup on
the computer hosting the report server. it detects your existing 2000 server
and provides you with the options to upgrade.
But it's more than a good idea to backup everything before processing
Have also a look to this
http://msdn2.microsoft.com/en-us/library/ms143747(en-us,SQL.90).aspx
Med Bouchenafa
"Brano" <2ge@.2NOgeSPAM.us> wrote in message
news:27981190.20051223134023@.ble.com...
> Hello all,
> I'd like to upgrade VS and also SQL server with RS. I just want make
> sure, if I backup all databases, uninstall SQL2000, install SQL2005,
> install VS 2005 with RS - if everything will be OK.
> I tried to find how to proper upgrade RS2000 to RS2005, but I dont
> find anything, and I just want to be sure...
> Thanks for any help!
>|||Hello Med,
Friday, December 23, 2005, 3:23:44 PM, you wrote:
> Actually you don't have to uninstall your 2000, when your run 2005 Setup on
> the computer hosting the report server. it detects your existing 2000 server
> and provides you with the options to upgrade.
> But it's more than a good idea to backup everything before processing
> Have also a look to this
> http://msdn2.microsoft.com/en-us/library/ms143747(en-us,SQL.90).aspx
thanks very much for answer! I wish you everything you like :)
--
Best regards,
Brano mailto:2ge@.2NOgeSPAM.us