SQL Server Upgrade

Hi all,
We are running B1 2005B PL6 on MSSQL Enterprise 2005 with SP1. I know that the SQL server has other product levels SP2 and SP3. Is it necessary to upgrade it to highest product level? If yes, is there any areas required to pay attention? And I am going to upgrade B1 to 2005B PL48 or PL49. Any impact without upgrade the SQL server?
Please advise.
Regards,
Eric

Hi Eric,
The answer to your question can be found [_here_|https://websmp108.sap-ag.de/~sapidb/011000358700001241092005E]: service.sap.com/smb/sbocustomer -> Solution Overview. Then expand "SAP Business One 2005" and click on 'Supported Platforms'. Scrolling to the bottom of that page you will find the following statement:
"Effective immediately, SAP will test only major versions of Microsoft's operating systems, databases and Office software products. Service Packs delivered by Microsoft in the course of a product's lifecycle will no longer be tested separately, but will automatically be officially supported for SAP Business One.
If a customer or partner encounters an issue with any of the Microsoft product Service Packs, SAP will solve this issue on a case-by-case basis as a bug (historically low rate of occurrence)."
So there is no need to update the SQL Server to the highest SP, however I'd recommend to do it.
Kind regards
Mario

Similar Messages

SQL Server Upgrade Advisor 2014 - Database Compatibility Level checking

I have the following scenario... I have a database server running SQL Server 2008 R2 (10.50.4260). On that server I restored a database from SQL Server 2005. Looking at the compatibility level through the properties of the database (using SSMS) and
by querying against sys.databases, I can see the database has the compatibility level of 90, which is what I expected.
In looking to bring this database over to a SQL Server 2014 database server, I have run the SQL Server Upgrade Advisor 2014 tool as well as the SQL Server Upgrade Advisor 2012 tool. With the 2014 tool, my expectation would be that it would warn me
that the compatibility level will be upgraded to 10 (or something), however, I received no such warning. I ran the 2012 version of the tool as well, expecting that I might get a deprecation warning (or something), no such luck. I have run the 2014
tool from my computer and from another one, same results.
Does the upgrade advisor not check for the compatibility level? Or does my configuration maybe have something to do with it (having it on a 2008 R2 server)? From looking at screenshots of when other people have ran the tool, I was under the impression
it checked this. See the link below for an example...
http://blogs.msdn.com/b/mspfe/archive/2012/12/06/sql-server-upgrade-advisor-considerations-when-upgrading-from-sql-2000-to-sql-2012.aspx
Thoughts anyone?

Lydia,
I agree with regards to the 2012 version. However, in SQL Server 2014, upgrading a database with a compatibility level of 90 sets
the database to compatibility level 100. See link below...
https://technet.microsoft.com/en-us/library/bb510680.aspx
Shouldn't the 2014 version of the advisor tool issue the same warning seen in the screenshot of the msdn blog post we both mentioned? As in... "After upgrade, compatibility levels <list of levels>, will be set to 100".
Hi JJordheim,
According to my test, SQL Server 2014 Upgrade Advisor also only raise warning when database compatibility level is less than 90 in the “SQL Server Parameters” page.
From your description, when database compatibility level is set to 90, SQL Server 2014 Upgrade Advisor should also raise warning, right? If so , this is a design issue of SQL Server 2014 Upgrade Advisor, personally, I recommend you
submit a feedback to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback . Your feedback enables Microsoft to offer the best software and deliver superior services.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Ms access to SQL server upgrade

hello there
I am using e-test suite 8.5 an sql server 2000. Although I upgraded ms acces to SQL server for e-load succesfully, I coulndt upgraded for e-manager.
inputs:
1- Clean setup of e-test suite is done
2- New ODBC data source for sql server is created
3- New SQL database created by Oracle Test Manager Database Configuration Tool unsuccessfuly
Error :
"Error creating executing SQL in database 'EManagerDB' on TESTSERVER
Foreign key "FK_Mail_Setting_Details_Roles' references invalid column ' IdRole' in referenced table 'Roles'
Could not create constraints. See previous errors
After this error, if I select "use existing database" option, unsuccesfully created Sql server database is added to my "databases" panel. tried several times but no way to login by emanager
İf this problem fixed, next issue will be data migration tool. It seems to convert acces db to sql server db but it has designed for only to import to oracle databases(needs port number and credentials
Please advice
thanks

thanks for the quick response,
What you suggest for this issue? I preferred sql server 2000 due to mentioned in user guide, I can change to SQL server 2005 no matter.
What would I except to happen if sql db creation went successfully? now just tables are created somehow, both tables and domain values will be created?
thanks

SQL Server upgrade to 12.00.2000

I am getting below error when I try to restore from a backup file. It seems backup is taken using 12.00.2000 version and my target DB is 11.00.3401 of SQL Server 2012.
Since my server changed, it got it auto upgraded, now my other servers are having older version of sql server
Please help to get my 11.00.3401 upgraded to 12.00.2000. From where I can get the upgrade setup?
Error:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 12.00.2000. That version is incompatible with this server, which is running version 11.00.3401. Either restore the database on a server that supports the backup, or use
a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)

I am getting below error when I try to restore from a backup file. It seems backup is taken using 12.00.2000 version and my target DB is 11.00.3401 of SQL Server 2012.
Since my server changed, it got it auto upgraded, now my other servers are having older version of sql server
Please help to get my 11.00.3401 upgraded to 12.00.2000. From where I can get the upgrade setup?
Error:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 12.00.2000. That version is incompatible with this server, which is running version 11.00.3401. Either restore the database on a server that supports the backup, or use
a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
I am looking for some setup file or way to upgrade my SQL server from 11.00.3401 to 12.00.2000.
You can go for free
SQl Server 2014 evaluation edition. It has enterprise features and can be used for 180 days after that you have to upgrade it to licensed version.
You cannot upgrade from SQl server 2012 to 2014 evaluation edition by inplace upgarde you need to do side by side upgrade. Backup database on 2012 and restore it on 2014 move logins and jobs and other objects by taking out script and running in SQL Server
2014
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Side effect of SQl server upgrade from 2008 R2 to Server 2012, logical name of log file changed for one database

I came to know that name has changed when I tried to shrink the file. Here is the error message I got:
Shrink failed for LogFile "Tfs_TESTTFS_Log'. (Microsoft.SqlServer.Smo)
Additonal information
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.COnnectionInfo)
Could not locate file 'Tfs_TESTTFS_Log' for database 'Tfs_TESTTFS' in sys.database_files. The file
either does not exist, or was dropped. (Microsoft Sql Server, Error: 8995)
This is test environment upgrade and I checked on production environment which is still on SQL 2008R2, shrink works fine.
Please help.

I did in place Upgrade.
Before Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: Tfs_TESTTFS_Log
After Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: TfsVersionControl_Log
Thx

SQL Server upgrade with merge replication

We are planning to upgrade SQL Server 2005 to SQL Server 2012 and both the databases will be hosted on two different servers. SQL Server 2005 has around 25 merge publication and have around 400 laptops that subscribe to these publications. The new SQL server
2012 will also have same replication setup as the old server. The data base size on the existing server is 66 GB and takes about 1.5 hrs for initial sync up.
Due to various business constraints we can't move over to new server in a single switch. Instead we need to keep both the servers running for a month or two. During this process, we need to replicate (uni-directional) data from SQL server 2005 to SQL server
2012 on a daily basis. To achieve this we have tried the following approaches so far:
DB backup and restore from SQL 2005 to SQL 2012 server - In this approach, the publications are dropped by SQL 2012 after we restore.
SQL native replication - Could not setup Transactional, Merge and Snapshot replication due SQL server constraints. Cannot setup merge replication between SQL 2005(publisher) and SQL 2012(subscriber)
Microsoft Sync framework – Sync fwk expects identify column or primary key for the sync to work but database has 76 tables without any primary key
SSIS – DB consists of 170 tables and will require significant effort to write and maintain the package to sync update and delete operations on the DB. Insert operations on the other hand are easy to support.
We are looking for different options to setup server to server replication with given constraints.

You will need to use some form of change tracking to gather the changes up and replay them on the SQL 2012 server.
You can hack into the msmerge_Contents and msmerge_tombstone to do this. It will be fairly laborious to set up, but it is doable. You can do this as a batch operation so you can run it nightly to do your syncs.
A lower tech way of doing it would be to run tablediff between the two servers and then replay the script nightly.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

SQL SERVER Upgrade using different Language Media

Hi
I have a doubt.
OS is Windows 2003 Server ( Japanese Version )
SAP - ERP6.0 SR3 ( EN + JA Installed)
My customer is having SQL Server 2000. ( Japanese Version ). While upgrading the SQL Server to 2005, can we use a English Version Media to upgrade the same.
Thanking you in anticipation.
Best Regards
L Raghunahth.

Lydia,
I agree with regards to the 2012 version. However, in SQL Server 2014, upgrading a database with a compatibility level of 90 sets
the database to compatibility level 100. See link below...
https://technet.microsoft.com/en-us/library/bb510680.aspx
Shouldn't the 2014 version of the advisor tool issue the same warning seen in the screenshot of the msdn blog post we both mentioned? As in... "After upgrade, compatibility levels <list of levels>, will be set to 100".
Hi JJordheim,
According to my test, SQL Server 2014 Upgrade Advisor also only raise warning when database compatibility level is less than 90 in the “SQL Server Parameters” page.
From your description, when database compatibility level is set to 90, SQL Server 2014 Upgrade Advisor should also raise warning, right? If so , this is a design issue of SQL Server 2014 Upgrade Advisor, personally, I recommend you
submit a feedback to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback . Your feedback enables Microsoft to offer the best software and deliver superior services.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SQL Server upgradation Issue : 2012 to 2014. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job.

Message
Executed as user: CORPTST\XXXXX. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job. The error information returned
by PowerShell is: 'Security error. '. Process Exit Code -1. The step failed.
I receive this error during the sql server job 'syspolicy_purge_history' execution when sql server got upgraded form SQL Server 2008 to 2014.

Hi Vishnu,
According to the error message, it also occurs in SQL Server 2012. Here is a feedback about the error in the link below.
https://connect.microsoft.com/SQLServer/feedback/details/754063/sql-server-2012-syspolicy-purge-history-job-step-3-fails-with-security-error
To resolve this issue, please change the value of the following registry key from ‘RemoteSigned’ to ‘Unrestricted’. For more details, you can review this similar
blog.
HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps120\ExecutionPolicy
Thanks,
Lydia Zhang

MS SQL Server upgrade from 2000 to 2005

I'm running SAP Tools for MsSQL server and my database version that is running on my system is 8, I'm getting an error saying that the SAP tools can only work with version 9.
Is there an older version of SAP Tools to work with MS SQL Server version 8 ?
Thanks.
George

Hi,
what is the version of the Sap tools ? generally all sap executables are downward compatible.
Regards,
Siddhesh

Performance Issue on REISBP since SQL Server upgrade to 2005

We recently upgrade our database from 2000 to 2005, using ECC5 (that didn't change). Since the upgrade one transaction in particular has taken a big hit... REISBP. It can range from seconds to 15+ minutes now to complete, which didn't happen before. the underlying table is BUT000.
Has anyone experienced this? Or other significant slowdowns after an upgrade.
(on a 32 bit Windows NT server - can't do anything about that for now.)
Thanks
Laurie

I did run the STO5 sql trace and the issue is with the vibpobjrel table part query. There are no further indexes to put on that table tho help out, based on how the users are accessing the report. Based on how they are using the report, several thousand records can be returned, which are then parsed as parms in the next part of the report where a "for all entries" clause is used... causing many union all statements.
What I don't understand is why the average execution time was much less, using the same criteria, in SQL 2000.
At this time we've instructed the users to not use a text criteria in the name field if at all possible, as this forces reading the entire BUT000 table, multiple times based on the return from vibpobjrel.
Perhaps this is just a taste of the 2005 performance on our systems. I do see some increased times for other transaction over the previous version, but none stand out as much as this one.
Thanks,
Laurie

Software licensing service won't start after sql server upgrade

having issues with windows server 2008 sp2 64 bit OS where the software license service do not start. and see the server as not genuine. when i run net start slsvc, I got a system error has occurred. system error 34 has occurred. the wrong diskette
is in the drive. insert *** (volume Serial Number: ***) into drive ***.
I try chkdsk and sfc/scannow. nothing seems to work.
thank you for your help

Hi,
Please try the steps below to resolve the issue:
1.net stop slsvc (select yes) in my case it was already stopped.
2.in command prompt type:
3.cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing
4.rename the tokens.dat file: ren tokens.dat tokens.old
5.still in the command prompt type cd %windir%\system32
6.type net start slsvc
7.type cscript slmgr.vbs -rilc (this may take a long time)
8.Then reboot the machine twice !!!
9.slmgr.vbs –ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (assuming you have a MAK key, not a KMS key)
10.To activate your OS, just type: slmgr.vbs –ato
If there any other error message? You could refer to the article below to troubleshoot the issue:
How to troubleshoot Volume Activation error codes in Windows 7, in Windows Server 2008, and in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;938450
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Rule "SQL Server 2012 feature Upgrade" Failed

I am doing an in-place upgrade of SQL Server 2008 R2 SP2 > SQL Server 2012 SP1, both 64-bit, installed on Windows Server 2008 R2.
I ran the SQL Server Upgrade Advisor tool prior to upgrade which reported no issues.
The error I am getting is:
In the detailed.txt log I can see the following:
(11) 2013-12-29 12:28:10 Slp: Initializing rule      : SQL Server 2012 Feature Upgrade
(11) 2013-12-29 12:28:10 Slp: Rule is will be executed : True
(11) 2013-12-29 12:28:10 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Found feature package 'sql_as_ctp6_Cpu64' with SkuValue=ENTERPRISE (Enterprise) ProductVersion=10.52.4000.0
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition ENTERPRISE for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=ENTERPRISE (Enterprise) sourceArchitecture=X64 targetEdition=STANDARD (Standard) targetArchitecture=X64
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' is blocking upgrade.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
(11) 2013-12-29 12:28:10 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
(11) 2013-12-29 12:28:10 Slp: Rule running on machine: TAUPE-SERVER
(11) 2013-12-29 12:28:10 Slp: Rule evaluation done   : Failed
(11) 2013-12-29 12:28:10 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
(11) 2013-12-29 12:28:10 Slp: Send result to channel : RulesEngineNotificationChannel
Prior to upgrade:
From Summary.txt file:
Overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Start time:                    2013-12-29 12:04:28
End time:                      2013-12-29 12:08:02
Requested action:              RunRules
Machine Properties:
Machine name:                  TAUPE-SERVER
Machine processor count:       1
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services - Native
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete              1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Enterprise Edition   10.52.4000.0
No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition:          Standard
Slipstream:                    True
User Input Settings:
ACTION:                        RunRules
CONFIGURATIONFILE:
ENU:                           true
FEATURES:
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTANCENAME:                  <empty>
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
RULES:                         GlobalRules
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\SystemConfigurationCheck_Report.htm
As far as I'm aware, the upgrade path I am following is a supported one, any suggestions will be much appreciated!
Thank you.

Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services - Native
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete              1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Enterprise Edition   10.52.4000.0
No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition:          Standard
Slipstream:                    True
User Input
Hello ,
You are trying to upgrade to SQL 2012 standard edition which is not supported .you can only upgrade from SQL server 2008 R2 Sp2 Enterprise edition to SQL 2012 Enterprise or business intellgience. see below link for supported upgrade paths
http://technet.microsoft.com/en-us/library/ms143393.aspx
If you want to move ahead you should try Side by side approach.Create new SQL server 2012 box and restore backup.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Does it need effort to upgrade SSRS from SQL Server 2005 to 2014?

Hi,
i have a customer who wants to upgrade the their system. for SQL Server part, the current version is 2005, they want to upgrade to 2014. is it possible that don't change any code for SSRS? if have to change, what's the estimated effort? the total RDL files
are more than 200.

Hi dingsheng,
In this scenario, you don't need to change code for Reporting Services. Those reports can be still available. Please run SQL Server Upgrade Advisor on the report server computer to determine any issues that might prevent you from successfully upgrading.
For more information, please see:
Upgrade and Migrate Reporting Services
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Pointers for upgrading to new version of SQL Server?

We're running SAP Business One 2007 A (8.00.181) SP:00 PL:49
At the moment we have a dedicated server computer to host the SQL databases for this product. The server computer is 32-bit Windows Server 2003. The database server is SQL Server 2005 32-bit. This server was purchased in fall 2006 and had a fast disk subsystem for its day: 5x 15K UltraSCSI hard drives in RAID5.
We have several company databases, some of which are in the 12 - 13GB range in size. There are occasions where two or more of these large-ish databases may be in use simultaneously. Since SQL Server on the current server limits itself to 2GB RAM usage, I suspect there is a lot of paging to disk when multiple company databases are open, with a major hit on performance.
Windows Server 2003 goes end-of-life on July 15, 2015. SQL Server 2005 end-of-life is April 14, 2016. As part of a refresh of company IT infrastructure, we're considering replacing various physical servers with virtual servers. Ideally, we'd like to migrate the backend to a current version of SQL Server on a current Windows server OS, and also move to a 64-bit platform so we can allocate more RAM to SQL Server. We may also host virtual hard drive file(s) on SSD if/where that makes sense.
What I've found so far:
All the current SAP databases are Compatibility Level 90 (native SQL Server 2005)
The latest version of SQL Server that supports Compatibility Level 90 is SQL Server 2012. SQL Server 2014 drops support for 90. I assume it's a bad idea to change the database compatibility level?
If for any reason we have to stick with SQL Server 2005, the latest version of Windows that supports that is Server 2008 R2. That's not ideal, since in a perfect world we would want all virtual machines running Server 2012 R2
Moving to a 64-bit version of SQL Server requires a so-called "side-by-side" upgrade, it's not possible to use a SQL Server upgrade wizard
The VAR we used to install and configure the product in 2006 is no longer in business so we'd like (if possible) to do this ourselves. I'm a software developer familiar with client-server development, SSMS etc. so I feel reasonably confident in undertaking a side-by-side upgrade.
So, assuming we'd like to migrate the backend to 64-bit SQL Server 2012, can anyone offer any pointers, experiences, or things to watch out for?
There are also some services running on the current server computer, which I'm assuming will also need to be migrated:
SAP Business One Integration Service
SAP Business One License Manager 2007
SAP Business One Messaging Service
I get the feeling other people may have asked similar questions before, but I couldn't find any relevant posts.
Thanks in advance for any help.

You probably need to do an installer file clean up for Apple Software Update with the Microsoft Installer Cleanup Utility.
Here is a method for removal and clean up of iTunes and related programs. You might get away with just doing the Apple Software Update part rather than the whole thing. I would try just removing and cleaning ASU first.
Download a fresh copy of iTunes and the stand alone version of Quicktime (the one without iTunes)
http://www.apple.com/quicktime/download/win.html
http://www.apple.com/itunes/download/
Download and install Microsoft Installer cleanup utility, there are instructions on the page as well as the download. Note that what you download is the installer not the program – you have to run it to install the program.
To run the program – All Programs>>Windows Install Cleanup
http://support.microsoft.com/kb/290301/
Now use the following method to remove iTunes and its components:
XP
http://support.apple.com/kb/HT1925
Vista
http://support.apple.com/kb/HT1923
*If you hit a problem with one of the uninstalls don't worry*, carry on with the deleting of files and folders as directed in the method.
When you get to deleting Quicktime files in the system32 folder as advised in the method, you can delete any file or folder with Quicktime in the name.
Restart your PC.
Run the Microsoft Installer Cleanup Utility. (Start > All Programs > Windows Install Clean Up)
Remove any references you find to the programs you removed - strictly speaking you only need to worry about those programs where the uninstall failed.
If you don’t see an entry for one of the programs that did not uninstall, look out for blank entries or numeric entries that look like version numbers e.g. 7.x for Quicktime or 1.x for Bonjour.
restart your PC
Install the stand alone Quicktime and check that it works.
If it does, install iTunes.

Install SQL Server 2008 R2 in Windows Server 2012 using SQL4SAP Script

Hi guys,
Since we are performing a SAP System Migration from older releases of Windows/SQL Server, as detailed on SAP Note
1780433 - System copy of SAP systems on Windows 2012 : SQL Server
We need to install SQL Server 2008 R2 before upgrading the system
When running SQL4SAP Script it states the following
17/03/2014 08:13:44 p.m.
Message Box "Windows version error"
OS Family "WindowsNT6.3" is not supported by this script.
Result: vbOK
On Windows 2012 should i run the SETUP instead the script?
Thanks!

Hi Sunny
Im following SAP Note 1780433 - System copy of SAP systems on Windows 2012 : SQL Server
in order to migrate a SAP 640 system from Windows 2003/SQL Server 2005 to Windows 2012/ SQL Server 2012
Reason and Prerequisites
This note describes how to migrate the mentioned SAP products to Windows 2012/SQL Server 2008 R2,
in order to prepare an upgrade to SAP releases based on NW 7.0 and higher.
Note, that only SAP upgrade paths are supported, that are supported by the SUM tool. For more
information about the upgrade paths supported by SUM, read the Central SUM Note referred to at
http://www.service.sap.com/SLToolset.
Immediately after the SAP upgrade, your database has to be upgraded to SQL Server 2012. SAP does in general not support SQL Server releases prior to SQL Server 2012 on Windows 2012.
I understand this is not supported from Productive system, we are performing this on a Development system for test purposes.
Nevertheless on the note says Install First SQL Server 2008 R2 and after SAP upgrade, perform upgrade of SQL Server Upgrade, so there is misleasing information.
Im not sure if a 640 System would be able to copied and upgraded in Windows 2012/SQL Server 2012
It doesnt mention that 640_EX2 Kernel Support SQL Server 2012 to install the system.
How would yo recommend a system copy restoring database on these conditions?
640 System (SQL Server 2005,Win 2003) --> 640 System (SQL Server 2012, Win 2012)
(and then Upgrading to 740)
Thanks

SQL Server Upgrade

Similar Messages

Maybe you are looking for