SQL SERVER 2005 Upgrade

Hello every one:
I am going to upgrade our database across environment from SQL server 2000 to 2005. We use Brightstor as backup application.
Dose any one know what if any changes needs to be done with Brightstor application?
Best Regards
KG

contact Brightstor to make sure that your backup client is fully compatible with ms-sql 2005.
Backups are too important to take a decision based on a public forum.

Similar Messages

SQL Server 2005 upgrade & migrate to 2012 method

Hi,
The situation is like this:
Currently I have SQL Server 2005 on an old Windows Server 2003. The target is to let SQL Server 2012 on Windows Server 2012 with the databases migrated over. The new server with Windows Server 2012 was prepared.
Originally my plan is to install SQL Server 2005 on the new Windows Sever 2012 first, migrate the database from old server to here, then upgrade SQL Server to 2012. Then found out this method cannot be used due to SQL Server 2005 is not compatible with Windows
Server 2012.
Alternative suggestions are appreciated.

SQL Server 2012 supports upgrade from the following versions of SQL Server:
SQL Server 2005 SP4 or later
SQL Server 2008 SP2 or later
SQL Server 2008 R2 SP1 or late
So please make sure that your existing sql server 2005 is upgraded to SP4 or later.
Then best way is use side by side.
Windows Sever 2012 on you new machine and sql server 2012.
Then use side by side method to migrate your old sql 2005 to new version 2012, ( moving backups and restore, logins, jobs, packages, configurations, maintenance plans,
linked server details and more. )
If you use in-place the in case of any issues we cant do anything to bring back the server to old version or fixing the issue may take lot of time. side by side its matter of navigating the connection and changing the connection setting for application and
putting databases for use ( online from single user or may be from online to online )
Raju Rasagounder MSSQL DBA

Restoring a SQL Server 2005 DB to a SQL Server 2014 install, is there any way to prevent it from being upgraded

Does anyone know if there is a flag I can use to prevent a SQL Server 2005 database from being upgraded to SQL 2014 when it is restored to a 2014 instance?
Don't ask why, I just need to know if this is possible or if 2005/8 DB's are required to be upgraded if they are going to run on SQL 2012/2014 instances. The documentation seems to say this is so, I just want to verify that.

First: You cannot directly restore a 2005 database to
2014. MS supports migration over 3 SQL Server version steps; means you can restore 2005 to 2008/2008R2/2012, but not to 2014. You have to do a migration step between.
Olaf I was looking for this today, because I'm working with a new customer that have SQL 2005 and I have SQL 2014. And needed to restore a backup form the production server in my test server.
When I read what you write I think, oh no!! I have to install SQL 2012 in my server. But that it's not an option for me, and I say let me try to restore the DB first in 2014 and if not work install 2012.
You can restore a 2005 database to 2014 directly, and it works.
For reference the version number in the servers 2005 (9.0.4035 SP3) and 2014 (12.0.2000 RTM)
This is not related in any way to the original question that you answered (the file format will be upgraded to the new motor, that is sure).
I put this lines because in the future there will be some people searching about if possible to restore a 2005 DB to 2014, and like me will read your lines and think it's not possible and that can make a decision to buy 2012 and not 2014 to that new server they
will migrate.
Don't forget to mark the best replies as answers!

I plan to upgrade the SSRS 2005 SP2 enterprise edition in our internal web server to 2005 SP4, the Reporting server database is hosted in another sql server in sql server 2005 SP4. Do I need to do anything on the reporting server database side?

My question is what the steps do I need to take to upgrade SSRS from 2005 SP2 to SP4. The web server that host the SSRS is in 2005 SP2, and the OS is in window 2003.
Our SSRS report server and report server database are in different servers. The SSRS in the web server is in 2005 SP2 enterprise edition, the report server database is in sql server 2005 SP4 enterprise edition.
To upgrade the SSRS in web server from 2005 sp2 to sp4, do I need to backup/restore the encryption key? Nothing will be changed in the report server database. We will still pointing to the same database in the current server, all
I wanted to do is performing a inplace upgrade of SSRS from 2005 SP2 to SP4.
Any response will be greate appreciated. Thank you!
Li-hui Chen

Hi Lihui Chen,
According to your description, you want to install the Services Pack 4 for SQL Server. Right?
In SQL Server, Services Packs are used for fixing issues of current version product. It's not an Upgrade, you don't have to backup/restore your encryption key. You just need to download the Service Pack 4 on:
Microsoft SQL Server 2005 Service Pack 4 RTM . Please make sure you have administrative rights on the computer to install SQL Server 2005 SP4. For more information, see links below:
How to obtain the latest service pack for SQL Server 2005
List of the issues that are fixed in SQL Server 2005 Service Pack 4
SQL Server 2005 SP4, KBA 2463332, Installation Issues
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Error when upgrading from SQL Server 2005 to SQL Server 2014

Hello everyone,
Could you help me, i have an error when i try to upgrade my SQL Server 2005 Enterprise Edition to SQL Server 2014 Enterprise Edition,
All of prerequisits are available and i dont have a problem,
before the end of migration process, i have this error: The group name could not be found (0x84BB0001)
File log:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Best regards,
Guiga Hafedh

There are more detailed logs for the various components. The one of interesting is the one for the engine or possibly the one for full-text.
These logs are extremely verbose, and the errors are rarely crystal clear, but at least give them a try. If you have problems, find a place to upload them (Dropbox, Skrydrive etc), so that we can look.
The closest at hand is that "group" that cannot be found is an AD group.
Erland Sommarskog, SQL Server MVP, [email protected]

Upgrade to SQL Server 2005 media

I am trying to find out if SAP provides a DVD with the SQL Server 2005 software for upgrade/installation as it did for 2000. I have found references in notes to using the DVD provided by SAP and a SQL4SAP vb script to run to do the install. And in other docs I see references to using the setup.exe provided on the media disk (I'm assuming here it is the MS media for SQL Server).
Is there a SAP disk for upgrading SQL Server? If so where can I find it.
If I can't locate this are there any issues to be aware of if I use the MS provided install disks for SQL Server 2005 to perform an upgrade?
Thanks
Laurie

Hi Laurie,
DVD 51032641 is the SQL 2005 installation DVD for SAP.
You cannot download it from service.sap.com, you have to order SAP standard software (SAP NetWeaver, SAP ERP, etc).
Best regards,
Victor

Upgrade SQL Server 2000to SQL Server 2005 in an SAP environment

Hi,
I have a scenario in which we are going to upgrade SQL server 2000 to SQL server 2005 in SAP an environment.
Now SQL server has a concept of In-Place Upgrade and Side-by-Side Migration Process.I want to know what does both of these mean.
We have an SAP note(799058.It talks about the upgrade in Step II.Is it the same as In-Place Upgrade concept in SQL?
What is step III in the note talking about? Is it talking about Side-by-Side Migration?
It would be of gr8 help if someone could provide the conceptual knowledge on these and what does the note mentioned above talks.

Hello
Please review my post on SQL upgrade.
SAP on SQL Server
You may also like to review
http://www.microsoft.ie/downloads/itprosql-90.ppt#568,17,Demo
Can you please advise your DB size and the max. amount of downtime your business can afford?
I will check, but I am almost sure that a side-by-side SQL upgrade is not appropriate for SAP systems.
Thanks
N.P.C

Upgrade from SQL Server 2005 to SQL Server Express 2014 Enterprise

I was just wondering if it is possible to upgrade from SQL Server 2005 to SQL Server Express or will I have to build the environment and then migrate the database?
Thanks for any help

Hi Lance_Romance,
As others’ posts, you don’t have to build new environment and then migrate databases between SQL Server instances, you can use the in-place upgrade strategy to upgrade from SQL Server 2005 to SQL Server 2014 .Please note that SQL Server 2005 SP4 is required
in this case.
Before upgrading , I recommend you to use
upgrade advisor, it can help to analyze your existing SQL Server deployment and inform you of issues that need to be addressed. In addition, please perform a full server backup prior to performing the in-place upgrade, which will be an important way
to revert your SQL Server to its previous state if the upgrade does not go as planned. For more details, please review this blog:
Upgrading to SQL Server 2014: A Dozen Things to Check.
Thanks,
Lydia Zhang

Upgrade data base from sql server 2005 to sql server2008

Hi guys,
What is the best way for upgrade my SQL Server 2005 data base to SQL 2008?

It depends on how you want migrate, in-place or side-by-side?
In-place: Run a backup of all databases and then install the new SQL Server version
Side-by-side: Install the new SQL Server, backup all database of old SQL Server and restore them on the new one. Then copy all logins from old to new server.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Upgrading from SQL Server 2005 Compact Edition [ENU] to SQL Server 2008 Express Edition OR HIGHER for Microsoft Security Compliance Manager

I have downloaded the MS Security Compliance Manager, which is in two parts: MS SQL Server 2008 Express Edition & the SCM. The install instructions state the the server needs to be install before the SCM. So as the install continues I get
an error message, which cancels the installation. So, I am trying to install SQL 2008 EE separate from SCM. My question is:
Can I upgrade from my current SQL Server 2005 Compact Edition [ENU]
directly to SQL Server 2008 Express Edition (or higher)?

So as the install continues I get an error message, which cancels the installation.
And which error message did you got?
SQL Server Compact Edition is something different then SQL Server Express (or Standard) Edition, you can't upgrade it as you asked for,.
Olaf Helper
[ Blog] [ Xing] [ MVP]

DB upgrade ms sql server 2005 to sysbase

Hi Team,
I am in new to upgrade the db, going to db upgrade ms sql server 2005 to sysbase.
Give the screen shots step by step how to upgrade.and notes.Kindly help me.
Regards,
A.SITHANANDAN

Hi
This is Database migration from MS Sql to Sybae, So you have to refer the SAP System copy Heterogeneous method, Kindly refer the SAP links and Notes
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00f3087e-2620-2b10-d58a-c50b66c1578e?QuickLink=index&…
82478 - SAP system OS/DB migration
680803 - SYB: Migration to SAP Adaptive Server Enterprise - Best Practice
1591424 - SYB: NW 7.02 system copy with target SAP Sybase ASE
1554717 - SYB: Planning information for SAP on ASE
Regards
Sriram

Upgrade to SQL server 2005 - Point Production Environment to New Server?

We have Essbase, Workspace, EAS, EIS, FR, WA environment in Production, supporting SQL server databases are on ServerA which has all these databases in SQL server 2000. The corporate standard is moving to SQL server 2005, and the SQL server DBA has copied the supporting dbs to ServerB for testing.
Is "pointing" to ServerB an option, or do the BI+ components have to be redeployed? Any help or pointing in the right direction would be appreciated.

Stephanie,
There could be schema changes between 2000 and 2005 you may want to check the support matrix to ensure your version of Hyperion is supported with SQL 2005.
Best bet is to back up the business rules, fr reports and then configure the system to the new databases on the SQL 2005 box then reimport the items.
JTS

Crystal Reports 9 and SQL Server 2005 default parameter values

We're using Crystal Reports 9 and upgraded from SQL Server 2000 to SQL Server 2005.
I'm noticing a very weird problem which I wonder if anyone else has experienced (and hopefully found a resolution for). It appears that in using Crystal with SQL Server 2005 stored procedures, if we have default parameter values in the stored procedures, the default parameter values get completely ignored if you pass in a NULL value from Crystal!
For example, if you have a stored procedure that begins like this:
ALTER Procedure [dbo].[StoredProcedure]
@Param1 VarChar(200) = '',
@Param2 VarChar(200) = ''
AS ...
both @Param1 and @Param2 have a default value of an empty string, and therefore should become empty strings if nothing (NULL values) gets passed in for them.
But, like I said, what I'm finding is that with Crystal calling the stored procedure with NULL @Param1 and @Param2 values, they never become empty strings, but rather remain as NULLs.
This was never a problem with SQL 2000.
Very perplexing. Anyone else every experience this?
Thank you.

Please ignore my earlier post -- answered my own question.
NULL parameter values do not get replaced by default values in SQL -- that is normal behavior in both SQL 2000 and SQL 2005. Just goes to show, that no many how many years programming experience you have, you can still get tripped up sometimes : (

Error While Installing IDES ECC6 with SQL Server 2005

Dear Experts,
I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
I herewith pasted hereunder log files information
Regards,
B.Sudharsan
ERROR 2008-01-17 18:38:47
FCO-00011 The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
INFO 2008-01-17 18:40:05
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
ERROR 2008-01-17 18:38:47
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

Sudarshan,
Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade.

B1 with SQL Server 2008 and SEC with SQL Server 2005

Hi,
we are currently upgrading from B1 2005 to B1 2007. With B1 2007 we could use MS SQL Server 2008. In parallel we have a SEC implementation (which uses SQL Server 2005).
Would there be any issues with the integration of B1 and SEC although they run on with different SQL Server products?
Thanks
Olaf

Hi
By creating two different instances you can run both simultaneouly. But pls do check whether SEC will run on 2008 or not ?
Ashish Gupte

SQL SERVER 2005 Upgrade

Similar Messages

Maybe you are looking for