SQL 2005 Upgrade

Hello all,
I upgraded my UCCE environment to CCE 7.5.5 in May but have not upgraded the Logger, HDS & AW databases to SQL 2005 yet.
Our standard procedure is to give at least 48 hour notice of a potential outage to service and I have missed that deadline due to lab testing and issues.
My question is regarding the 90 day window after the initial upgrade and what effect will it have on my databases if I do not upgrade it by before the 90 days is up?
So far I have not seen any notifications regarding the necessity of an upgrade.
Thanks in advance.
Troy

You should have no issues. 90 days is an official supportability stance. they want you to go to SQL 2005 as soon as possible, but you system will not cease to function after that 90 days expire.
If you were to open a service request they may ask you to upgrade before they perform any troubleshooting on your issue, so it would be in your best interest to upgrade as soon as possible.

Similar Messages

SQL 2005 Upgrade complete! - Post installation tasks questions!

Hi All
I have managed to upgrade our DEV and TST ECC6 systems to SQL2005 (from SQL2000) and so far all seems ok however I have a a few questions and checks I would like some help with. I have included my post installation tasks at the bottom of this post, so you know what I have done.
I have noticed that when I run SGEN I get a short dump LOAD_VERSION_LOST which I am not sure what this means.
If there is anything else I need to do or should do please let me know.
Thanks
Phil
Post Installation Tasks
SQL Queries
exec sp_configure 'show advanced options', 1
reconfigure with override
exec sp_configure 'max degree of parallelism', 1
reconfigure with override
exec sp_configure 'xp_cmdshell', 1
reconfigure with override
alter database <SID> set page_verify checksum
go
alter database <SID> set auto_create_statistics on
go
alter database <SID> set auto_update_statistics on
go
alter database <SID> set auto_update_statistics_async on
go
dbcc updateusage ('<SID>')
go
exec sp_updatestats
go
SAP Tasks
Check SM21/SM50/DB02/ST04/ST22/SICK for any unusual error messages.

Hello,
I want run the below script on SQL 2005, can anyone tell me how I run it in SQL 2005?
exec sp_configure 'xp_cmdshell', 1
reconfigure with override
I need to enable xp_cmdshell in sql 2005
Reg,
SAT

DB02 running very slowly after SQL 2005 Upgrade!

Hi All
I have reciently upgraded our DEV ECC6 system to SQL 2005 and everything seemed ok - no problems really! However when we run DB02, to retrieve DB information it is taking about 4 to 5 mins to appear. This is obviously not good!
Has anyone else had this problem, and if so is there something that needs to be done?
Thanks
Phil

Hi Phil,
Have you ensure that all the standard background job as per note 16083?
Thanks and Regards
Point reward is much appreciated

Re-install after sql 2005 upgrade

Hi all,
I've heard a rumor that after switching to sql 2005 I need to re-install business one.
Is this true?
Should I just schedule an upgrade to the next patch level, or do I need to re-install my current version?
Thanks,
Jim

Hi
There's no reason for upgrade just because SQL upgrade.
The new SQL will need the Native Client for connection (that is the most important check to do), you can connect with the old SQL Server ODBC but it is not recommend
The SAP Note 1015229 mention that and provided the patch to download in case of you did not install it during the SQL installation.
Paulo Calado
SAP Business One Forums Team

Restoration at sql 2005 from sql 2000 backup.

Hi experts,
Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
And how about attaching datafiles of sql2000 into sql 2005 server?
Thanks and Regards,
Amit Jana.

> Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
Yes its possible.
> And how about attaching datafiles of sql2000 into sql 2005 server?
Same method of attach/deattach.
But recommanded you first install 2000 instance restore database and do inplace sql 2005 upgrade.
Why you can't follow recommanded mothed ?
Regards,
Nikunj Thaker

Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005

Dear Experts,
We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware.
I was earlier planning to Upgrade the OS/DB in first Phase moving the same R/3 4.7 on Windows 2003 Server /MS SQL 2005 and then Upgrade it to ECC 6.0 in second phase. But to my surprise when I checked PAM, I found that R/3 4.7 110 is not at all supported on SQL 2005 ( though R/3 4.6 C is)
Now shall I upgrade it to ECC6.0 First with Windows 2003/SQL 2000 ( Because ECC6.0 is supported with MS SQL 2000)and then move to MS SQL 2005 ?
Thanks
Jitendra Tayal

We had the same issue.
So I checked with SAP.
This was their reply.
'SAP R/3 4.7 Ext 110 is supported on SQL 2005. Please refer to the following notes for further information:'
Note 905634 - Release planning for Microsoft SQL Server 2005
Note 799058 - Setting Up Microsoft SQL Server 2005
Note 899111 - Installing R3 4.7SR1 (47X110) on x64 Windows Platform
Note 151603 - Copying an SQL Server database
So feel free to go ahead.
Thanks.
Carl.

SQL Upgrade 2000 to SQL 2005

We are upgrading to new server and installing SQL 2005. Using Crystal Server 10. Where can I find a step by step? Can I just backup Business Objects Database, install the app on the new server, restore the database to SQL 2005?
Thanks,
SS

Hi Samuel
You can refer the below link for more information on SQL Server 2005 upgrade.
[http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx#top]
Regards
Girish.

SSRS 2012 rendering issue/Enabling Anonymous access - Upgraded SSRS from SQL 2005 to SQL 2012.

Hi,
I just recently upgraded SQL 2005 SSRS to SQL 2012 SSRS. Everything is working great other than small issue.
Sounds like some authentication issue. SQL 2005 SSRS - IIS, we enabled anonymous access and we never had this problem. SQL 2012 SSRS /WIN 2008 R2 - I am not sure how to enable anonymous access.
If anyone can help me on this? I really appreciate your help.
Thanks,
Vel
Vel Thavasi

Hi Vel,
According your description, you want to know how the enable anonymous access to SSRS 2012. Right?
In SSRS 2008 or later version, we are not using IIS any more. If we want to configure the authentication, we need to configure in RSReportServer.config. This file locate at:
<drive>:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer
However, in SSRS 2012, Anonymous authentication is not supported on report server. Please see:
Authentication with the Report Server
In this scenario, we need to custom an authentication type to achieve the "Anonymous" goal. Please refer to the link:
Configure Custom or Forms Authentication on the Report Server
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

SQL 2005 discoveries after upgrade to Operations Manager 2012 R2 UR3 upgrade

Hi
We did a (succesfull) upgrade of our SCOM 2012 SP1 environment to 2012 R2 UR3. We noticed after the upgrade that databases of some SQL 2005 clustered instances on Windows 2003 R2 SP2 are no longer discovered. checking the eventlog shows the eventid
21405 on the DiscoverSQL2005DB.vbs disvovery (process exited with 4294967295)
Browsing and checking several webfinds didn't provide a solution yet. Perhaps I overlooked the obvious....
Possible solutions which didn't bring relief yet:
check on SQL SP's
WMI registry settings [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM] ": Low/High Threshold On Events
WMI repair, mofcomp...
Uninstall/Reinstall Monitorring Agent
manual run of the discover script returns all info
The runas discover and monitor account(s) are local admin on the OS and SA on the SQL instances
I'm stuck: right now we wanted to present some distributed applications through LiveMaps in scom to our internal customers and some essential databases are no longer discovered/monitorred.
Any help highly appreciated

I'd just like to add that since upgrading all of our environments to 2012 R2 UR3, we are receiving multiple alerts for multiple script failures - e.g. Events 21404, 21405 to name a couple.
I have logged a few Microsoft Premier Support Calls and they are still working on them.
We get this on all SQL 2005,2008 running on Windows Server 2003. Microsoft's response to this is:
"This is a known bug in the latest SQL MP. This is due to the problem with the DiscoverSQL2008DBEngineDiscovery.vbs and DiscoverSQL2005DBEngineDiscovery.vbs scripts which contains the following line of code :
tcp = oQuery.ItemIndex(0).PropertyStrVal
The issue is the ItemIndex is supported only on Vista+ operating systems. The product group is currently investigating and evaluating the issue and I don’t think the fix will be released recently…"
I guess that meant "any time soon' :)
I should add that we also upgraded the SQL MPs around this time too, to 6.5.1.0.
So as you can appreciate, we just have to put up with this for now!
Cheers

Upgrade Process from SQL 2005 to SQL 2012

Hi All,
I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
Run Upgrade Advisor on the new environment and point to SQL 2005 instance
Find the breaking/discontinued changes to be done before or After Upgrade
<Question>: Over here I would like to know what should be our approach to make the required changes
<Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
<Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
any thoughts on this ?
<Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach
So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
---Umesh

Thanks all for the replies.
I am trying summarize what I have understood here:
Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
Probbaly run SQL Profiler as well to find out the deprecated changes to be done
I should fix all the breaking, discontinued changes on the Test system identified by UA
I should fix all the deprecated changes on the Test system identified by SQL Profiler
Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
<Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
<Question> Ideally I should a restore first in the new environment which has SQL Server 2012
<Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
<Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
<Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
<Question> Perform test again which we ran on SQL Server 2005 Test environment
<Question> These steps should complete the Upgrade process.
Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
Thanks Again ...

Upgrading to SQL 2005 from 2000?

I have a very large database in 2000 and I'm thinking of
requesting that
it be moved to 2005. I've heard that 2005 is faster and I've
seen the
interface for it and it looks like it combines Query analyzer
with the
standard interface tools. Enterprise Manager is just so
limited and clunky.
Do you think I'd run into problems with my site if I had them
update to
a new SQL database? Any pitfalls? Warnings? What should I
look out for?
Is it worth it for the new security and interface features?
Thanks

I would say wait a short while longer and upgrade to SQL
Server 2008. It
seems pointless going through the upgrade now when the next
version is
already on our doorstep.
A word of warning. There is no downgrade option once you have
upgraded so
run the built in Upgrade Advisor before you do anything (if
you have that
option) and also check that all your T-SQL code is ANSI
compliant as
non-ANSI compliant code will not work in SQL 2005 or 2008.
See:
http://www.sql-server-performance.com/faq/query_uses_nonansi_outerjoin_p1.aspx
for more info.
Also, remember that you will not have the option of
scheduling any DTS
packages from 2000 as these will need to be re-built as SSIS
packages if you
want them to run them as Jobs, although you can still execute
them manually
(if that is a feasible option) with the assistance of the DTS
add-on that is
a free download from Microsoft.
Just be very careful that all is in place before you upgrade
and make sure
you take a full database backup before you upgrade (including
system DB's)
in case you need to re-install 2000 and rebuild the
databases.
Pat
"Philo" <[email protected]> wrote in message
news:fr3n35$dsq$[email protected]..
>I use Fluid Hosting and when they changed from 2000 to
2005 I saw no
> differences. I would check the lit on what is new and
more important
> what changed from prior version and determine if any of
it applies to
> your applicaiton.
>
> Art wrote:
>
>> I have a very large database in 2000 and I'm
thinking of requesting
>> that it be moved to 2005. I've heard that 2005 is
faster and I've
>> seen the interface for it and it looks like it
combines Query
>> analyzer with the standard interface tools.
Enterprise Manager is
>> just so limited and clunky.
>>
>> Do you think I'd run into problems with my site if I
had them update
>> to a new SQL database? Any pitfalls? Warnings? What
should I look out
>> for?
>>
>> Is it worth it for the new security and interface
features?
>>
>> Thanks
>
>
>
> --
>

Upgrade windows 2000 t o windows 2005 and sql 2000 to sql 2005

Dear People,
i have not actually done any upgradestill now, i have task where i need to upgrade existing sap system.The sap has already been upgraded, now my task is to upgrade operating system and database
requirement:
windows 2000 to windows 2003
sql 2000 to sql 2005
the above should be done by the procedure recommended by sap only, so im wondering where i can find the information and tools for uprading both O/S and DB.
Help
Raj

I personally would not do a Windows upgrade, Windows can be very picky when it comes to 3rd party SCSI/FC drives you may experience bluescreens during the update after the second boot etc.
I would backup the system and install the operating system from scratch and do a system copy instead.
For your database upgrade, there's a guide at
http://service.sap.com/instguides
--> Other documentation
--> Database upgrades
Markus

Error in Upgrading to MS SQL 2005

i have Nw2004 installed wiht MS SQL 2000 as database.
Iam in the process of upgrading this server to NW2004s.
As a pre-requisite i upgraded the MS SQL 2000 to MS SQL 2005 Server
But after upgradation of MS SQL only(NW2004 is there) when i start the SAP Instance the SAP Instance is starting.
but when i login to SAP and run any transactions it is giving a message
START_CALL_SICK.
Please let me know whether i can run MS SQL 2005 server with NW2004

hello Balaji,
You can ignore this error. Basically just restart the system. I would say reboot the machine. restart database and then SAP. However before that execute the transaction SICK and look for any errors.If there are any error then you need to solve them. May be you can paste them here. MS SQL 2005 is supported with Netwaeaver 04.
Check this:
https://websmp104.sap-ag.de/platforms
Regards.
Ruchit.
Message was edited by:
Ruchit Khushu

Upgrading sql 2005 from sp to sp 3

hi all
i have a question. i need to upgrade my sql 2005 from sp 2 to sp 3 on my live environment because windows7 needs sp3. would there be any issues if i upgrade to sp3?
i just download sp3 into my server and run it?
thanks!
prem

Hi Prem,
Windows7 is not officially supported yet. If you have issue, it must be related to windows7. SP3 should not be an issue.
Thanks,
Gordon

MS SQL 2005 Warning when upgrading 2005A SP01 PL10 to PL34

When attempting the above upgrade I get the following warning during the Upgrade of the Common db.
"Changing any part of an object name could break scripts and stored procedures".
We have version 9.00.1399.06 of SQL 2005. I think this is SP00.
SAP Support advised me to uninstall and re-install SBO bt I got the same error again.
I am considering upgrading SQL 2005 to SP01 or SP02 to try to resolve this issue.
Is SP02 supported for SBO?

Hello,
Based on latest sizing guide file, recommended database servers are :
1. Microsoft SQL Server 2005 Standard or Enterprise Edition
(As of SAP Business One 2005 SP 01 Release and only on Windows 2003 Server operating system.)
2. Microsoft SQL Server 2000 SP4 Standard or Enterprise Edition
3. IBM DB2 Universal Database 8.2.2 FP5 Express Edition
4. Sybase Adaptive Server Enterprise 12.5.3 GA
if you need the file, you could download it from this link :
https://websmp108.sap-ag.de/smb/sbo/documentation
Rgds,
JM
http://groups.yahoo.com/group/SBO_Knowledge_Village
[email protected]

SQL 2005 Upgrade

Similar Messages

Maybe you are looking for