MS SQL 2005 clustered database instance.

Short Text
MS SQL cluster database instance - ONLY!
Long Text
Hi,
If possible could you please confirm that our planned landscape
migration is supported by SAP.
At present our PRD SAP system is a standalone instance that consists of
the database & central instance running on the same "HOST".
Current SAP PRD version:
ERP 2004 ECC 5.0 32 bit
MS SQL 2000 32 bit
both running on same host with OS Windows 2003 32 bit
We plan to upgrade/migrate our PRD SAP system to new 64 bit hardware
AND to move to a "Distributed" landscape installation i.e. database
instance & central instance installed on different HOSTS. Also, the
database instance WILL be clustered but the central instance will NOT
be clustered. There are also multiple NON-SAP MS SQL databases that
will run in the same cluster as the PRD SAP database instance.
SAP PRD version after migration:
SAP ERP 2004 ECC 5.0 64bit (running on X86_64 AMD64 hardware) on HOST'X'
MS SQL 2005 64 bit (running on IA64 hardware) on clustered HOST'Y'
Both running on Windows 2003 64 bit
My questions are:
1) Does SAP support a clustered MS SQL 2005 database instance that is
running on a clustered HOST along with NON-SAP MS SQL databases?
2)During the migration our PRD SAP MS SQL database will be upgraded
from MS SQL 2000 32 bit to MS SQL 2005 64 bit IA64, is this also
supported in a clustered istallation (database instance ONLY)?
3) The central PRD SAP instance will be running on x86_64 AMD64
hardware & the database instance will be running on 64 bit IA64
hardware. Is this configuration supported?
Thanking you inadvance.

Hi Greg,
Have you figured out the answer? We are trying do the exactly the same thing -- Move our SAP WAS 6.40 clustered central instance to a 64-bit hardware/SQL 2005/Clustered system. And this system has several non-SAP database on there. The biggest concern we have is whether SAP support this architecture. I posted a message here last year and several experts like Clas Hortien, N. P. C, in this form suggest NOT go to this architecture because SAP will not support it. One example, is that SAP/SQL requires server collation setting to SQL_Latin1_General_CP850_BIN2 and other databases may work on different collations.
Migrate SAP SQL Server database to co-exist with others
Anyway, if you or anyone in this form have some more information please share here.
Thanks,
Yujun Ran

Similar Messages

SQL 2005 with database compatibiltiy level set to 80

I am working with a new client transferred to us and they have been having performance issues, particularly with an add-on solution. I have been looking as some of the database settings and noticed that the database compatibility level was set to 80 - SQL 2000 when they are running on SQL 2005 with SAP B1 2007, PL 44. Would having this set to 80 have any impact on performance? Is it suggested to absolutely set the compatibility level to 90?.
Thanks to all

Hi,
As per the SQL Administration guide, you have to choose collation setting of: SQL_Latin1_General_CP1_CI_AS when installing MSSQL 2005 Server.
In order to check what the collation is set to in your server, please run the following query:
select SERVERPROPERTY ('collation')
(This query gets the collation settings of MSSQL Server's System Database "Master")
Expected answer : SQL_Latin1_General_CP1_CI_AS
As MSSQL 2005 Server is already installed with collation SQL_Latin1_General_CP850_CI_AS, kindly follow the steps below:
Change your server collation to SQL_Latin1_General_CP1_CI_AS
You can find Microsoft's instructions for changing an SQL server collation here:
http://msdn2.microsoft.com/en-us/library/ms179254.aspx
Note: The collation settings of Database "Master" needs to be changed only. All SAP Business One Databases must not be changed! They must remain on SQL_Latin1_General_CP850_CI_AS.
If you need any clarifications with this process please refer to an Expert Empowerment Session "SQL 2005 Server Collation settings" at https://websmp203.sap-ag.de/~sapidb/011000358700000050892007E/ or http://service.sap.com/smb/sbo/support -> Archive: Empowerment Sessions.
If you have any Service pack for MSSQL Server installed, but the Service pack is not included into your DVD MSSQL Server, do as follows:
1. Uninstall Service pack
2. Change Collation Settings as per Expert Empowerment Session
3. Install Service pack again
Hope this is helpful!

SQL referencing Two database instances

I have searched through most of the posts regarding this subject so please bear with me.
I have created two views in two database instances. Dev and prd.
I am attempting to execute a simple query from Dev within TOAD.
select * from [view_Name]
minus
select * from [view_Name]@PRD
When I execute this I receive an error that the remote connection cannot be found.
Do I have to create a database link using the TNS connection string, or is there another way to reference another database instance within the SQL?
Any help is appreciated.

You need to create a database link (see [url http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5005.htm#i2061505]Oracle® Database SQL Reference).
But I would not refer to other database objects directly like that. Should the link name change, or the remote object name's change, then each and every reference to those needs to be updated in all SQL and PL/SQL code.
When dealing with foreign databases (like Informix for example), objects are case sensitive. Which means ample use of quotes to enforce case on the Oracle side.
All this gets to be quite messy - especially during the maintenance of the code.
Thus, instead of "hard references", use "soft references". Create local views on remote objects. Use those local views in all SQL and PL/SQL code. Any change to database link or remote object now only requires the applicable view to be updated - no hunting for code that needs to be changed.

SQL 2005 and Database Refreshes

We have 2 NW2004S systems both with ABAP+Java. When we copy one database over from one system (A) to another (B), we've noticed that the schema attached to all of the tables in on the B system are now A.
Using the SQL Tools application from SAP, we were able to fix the ABAP tables, but are unsure as to how to convert Java Tables from A back to B. As a result of this database copy, the Java instance (including configtool) won't start.
Re-installing the Java DB instance did correct the DB schema error, and configtool did run as a result, although the Java CI failed to load.
Any suggestions?

Try to use the script below.
The last line is the script is what you need to change with appropriate database IDs. Look for <tags> to replace appropriately.
Also ensure you create the user SAP<NEWDB>DB already in the database. (specifically in Management->Security ... you know what I mean !!??)
++++++++++++++++++++++++++++++++++++
use <NEWDB_SID>
go
if object_id('sp_change_sapuser') is not null
 drop procedure sp_change_sapuser
go
create procedure sp_change_sapuser @oldid sysname, @newid sysname
as begin
declare @oldid_uid smallint
declare @newid_uid smallint
declare @object sysname
declare @object_full nvarchar(999)
set @oldid_uid = user_id(@oldid)
set @newid_uid = user_id(@newid)
if @oldid_uid is not null and @newid_uid is not null
 begin
 declare object_cursor cursor local for
 select name
 from sysobjects
 where
 ( (xtype='U' and name <> 'dtproperties')
 or (xtype='V' and name not in ('syssegments','sysconstraints'))
 or (xtype='P' and name not like 'dt_%')
 or (xtype='D' and name not like 'DF__dtpropert%')
 or (xtype in ('FN','TF','IF'))
 ) and @oldid_uid = uid
 open object_cursor
 fetch next from object_cursor into @object
 while @@fetch_status=0
 begin
 set @object_full = user_name(@oldid_uid) + '.' + @object
 exec sp_changeobjectowner @object_full, @newid
 fetch next from object_cursor into @object
 end
 end
else
 if @oldid_uid is null
 begin
 print '*** old database user does not exist ***'
 end
 if @newid_uid is null
 begin
 print '*** new database user does not exist ***'
 end
end
go
exec sp_change_sapuser 'SAP<OLDSID>DB', 'SAP<NEWDB>DB'
go
++++++++++++++++++++++++++++++++++++

SQL 2005 and Database Restores

We have 2 NW2004S systems both with ABAP+Java. When we copy one database over from one system (A) to another (B), we've noticed that the schema attached to all of the tables in on the B system are now A.
Using the SQL Tools application from SAP, we were able to fix the ABAP tables, but are unsure as to how to convert Java Tables from A back to B. As a result of this database copy, the Java instance (including configtool) won't start. Re-installing the Java DB instance did correct the DB schema error, and configtool did run as a result, although the Java CI failed to load.
Any suggestions?

Hi, Michael!
I think your post will be better answered in "SAP on SQL Server"-Forum.
Regards,
Thomas

ADMIRAL database on SQL 2008 R2 Named Instance

Hi,
we are running TES 6.1.0.133 (test Master) upon a remote SQL 2005 SP4 named instance database, all is right.
I need to move the ADMIRAL database to an SQL 2008 R2 SP1 named instance.
What JDBC, JRE and connection string do I need to succeed ?
The versions are JRE 1.6.0.30, Microsoft JDBC 4.0.
thank in advance you for your experience,
Frederic

You should probably ask Cisco to help you through this they can likely provide you with an updated document and jar file
You will need to update your master.props settings.
You will need potentially need a new jar
Perform on a maintenance weekend with a maximum amount of recovery time
I have a Cisco doc and Zip files from 2010 when we did this but it is likely a different JAR that you would want to apply now.
What I would think are the Sequence of events (disclaimer Cisco would be best source of sequence, order, etc)
set system queue to zero
close all client sessions
stop master services
kill all connections to Admiral database
backup admiral database
set database offline and rename
Restore admiral database backup to new target SQL server 2008 instances
Creare a backup of master.props
Apply Jar to update master / SQL scripts (if supplied by Cisco)
Update master.props with new settings
JdbcURL=jdbc:sqlserver://:;selectMethod=cursor;databaseName=Admiral (or Admiral DB name)
There could be other setting that may also need to chance
Start Tidal Master make sure it is running
Connect Client
Verify Connections
Turn on System Queue slowly ramp up from a few to your standard level

IPC 4.0 Standalone with SQL 2005 Express as a database

Hello,
I am trying to setup IPC 4.0 standalone up for a training class on a XP laptop with SQL 2005 Express as the database. I keep getting login errors connecting the IPC admin.bat tool to the sql database. And yes, I know this is not 'officially' supported by SAP, but I see no technical reason why it shouldn't work and yes my port is correct. My entries are as such:
Alias: 00_230
Server: localhost
System: Microsoft SQL Server
Database Name: 00_230
port: 1433
User: ipc
password: hidden
client: 230
Is everything I entered correct? Am I missing anything that I need?
Thanks!

Hi Jeff.
You will probably have problems with the database subsystem, when you upgrade to UccX7.0.1 if the 3rd party database is af SQL2k5 server.
There is a fix for that problem, check below :
Upgrading UCCX to 7.0(1)Sr4 is failing ODBC connection to SQL 2005.
Symptom:
Upgrading the UCCX server to 7.0(1) Sr4 and OS to 2003.1.4a SR11 is failing the ODBC connection to SQL 2005 external database. (also a problem in new installations)
The error generated when trying to setup a ODBC connection to SQL 2005 database is
======
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
=======
Conditions:
Upgrade to UCCX 7.0(1) Sr3 or 4 and OS upgrade to 2003.1.4a SR11
Workaround:
Work around:
a) In UCCX SQL Server 2000 - Start the Client Network Utility. (cliconfg.exe is used from MSDE versions of UccX)
b) On the General tab, add TCP/IP in the list under Enabled protocols by order. (make sure its first)
c) Click the Alias tab, and then click Add. Under Network libraries, select TCP/IP.
d) In the Server name text box, type the IP address of the server that is running SQL Server
2005.
Note:
If port other that 1433 is being used Click the check box to clear the Dynamically determine port option, and then type the port number of the instance of SQL Server 2005 in the Port number text box.
Regards
\Søren Lavard

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

IPCC 4.0(5) with Sql 2005 Enterprise DB

Hello,
I currently have IPCC 4.0(5) (no SR) doing with an ODBC connection to a SQL 2000 server. I am preparing to upgrade the SQL 2000 server to SQL 2005 (only upgrading a SQL server, not touching SQL 2000 running on IPCC).
According to the document in the link below, support for SQL 2005 as an enterprise db was not posted until IPCC 4.0(5) SR2. I will be upgrading to IPCC 7.x very soon, but need to buy time and avoid touching IPCC 4.0(5). Does anyone know if the ODBC connection from IPCC 4.0(5) will connect to a SQL 2005 server?
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crsmatrxeol.pdf
Thanks,
Jeff

Hi Jeff.
You will probably have problems with the database subsystem, when you upgrade to UccX7.0.1 if the 3rd party database is af SQL2k5 server.
There is a fix for that problem, check below :
Upgrading UCCX to 7.0(1)Sr4 is failing ODBC connection to SQL 2005.
Symptom:
Upgrading the UCCX server to 7.0(1) Sr4 and OS to 2003.1.4a SR11 is failing the ODBC connection to SQL 2005 external database. (also a problem in new installations)
The error generated when trying to setup a ODBC connection to SQL 2005 database is
======
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
=======
Conditions:
Upgrade to UCCX 7.0(1) Sr3 or 4 and OS upgrade to 2003.1.4a SR11
Workaround:
Work around:
a) In UCCX SQL Server 2000 - Start the Client Network Utility. (cliconfg.exe is used from MSDE versions of UccX)
b) On the General tab, add TCP/IP in the list under Enabled protocols by order. (make sure its first)
c) Click the Alias tab, and then click Add. Under Network libraries, select TCP/IP.
d) In the Server name text box, type the IP address of the server that is running SQL Server
2005.
Note:
If port other that 1433 is being used Click the check box to clear the Dynamically determine port option, and then type the port number of the instance of SQL Server 2005 in the Port number text box.
Regards
\Søren Lavard

Upgrade sql 2000 win xp to sql 2005 win2003 server

Hi,
We had installed sap b1 2005b on winxp and database as sql 2000.
Now ,we want to install sap b1 2007b on win 2003 and database as sql 2005.
Can the sql 2000 winxp database backup be restored on sql 2005 win2003 database.
Since both the OS are different can the backup be restored .
Pls let me know about the same.
Regards,
Rajeev

Hi Rajeev
step 1) Install SQL Server 2005.
step 2) Install [SAP Business One|http://www.brio.co.in/products/sap-business-one/] 2005
step 3) Get the new license key for your windows 2003 server if you dont have
step 4) Create a company with same name and database name this will create a company record in SBOCommon database
step 5) Take the backup of the database of the company in MS SQL 2000.
step 6) Restore it on your windows 2003 and sql server 2005 system
step 7) Download an upgrade for 2005 to 2007 from software download center
step 8) Run the upgrade exe
THATS IT, YOU ARE ON YOUR NEW SYSTEM.
Regards
[Abdul Muneem|http://www.brio.co.in]
Edited by: Muneem Abdul on Nov 22, 2010 12:22 PM

Invoke sql 2005 native web services

Dear all,
I am trying to invoke from sap ecc 6.0 a native web services written in sql 2005.
For instance the web service path is something like http://10.1.0.197:8080/EmployeeXml?wsdl .
The web method is GetEmployeesXml
If I try to consume via custom .net application, it works but when I try to do the same in sap
following this guide
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/802edea6-274e-2e10-fd95-e5e1a8bc0892?QuickLink=index&overridelayout=true
I get the error http not supported.
The differnce between an asp.net web services (where everythings works) and this one is regarding the autentication.
For the first one it is possible to specify anonymous login for second it is necessary to specify the username and password.
I kindly ask you to give any help to solve this issue, or is there a manual for sm59?
Thank you very much

Try with the following:
<xsd:complexType name="SqlResultStream">
 <xsd:sequence>
 <xsd:element name="SqlRowSet" type="sqlsoaptypes:SqlRowSet" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="SqlXml" type="sqlsoaptypes:SqlXml" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="SqlMessage" type="sqlmessage:SqlMessage" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="SqlRowCount" type="sqlrowcount:SqlRowCount" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="SqlResultCode" type="sqlsoaptypes:SqlResultCode" minOccurs="0" maxOccurs="unbounded"/>
 <xsd:element name="SqlTransaction" type="sqltransaction:SqlTransaction" minOccurs="0" maxOccurs="unbounded"/>
 </xsd:sequence>
</xsd:complexType>
You also have to know that this is not a perfect equivalent, as no tag can replace the xsd:choice. The xsd:choice means that only one of the elements can occur, while in xsd:sequence any of the elements can occur. But you should be able to achieve the same with a properly built mapping: create only one of the fields, and leave the rest empty - this is possible thanks to minOccurs="0".
Hope this helps,
Greg

SQL 2005 Databases not Discovered

We have a SQL 2005 server, where the DB instance itself has been discovered but the SQL DBs themselves have not. Any way to understand / troubleshoot why not. Other instances work just fine.

The account is just fine, and it is a sysadmin on the server. It discovered the instance even, unlike by my other post:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/7da4b442-c9e4-4aac-9cb9-d2af0b1ffbaa/clustered-database-engine-not-discovered?forum=operationsmanagermgmtpacks&prof=required
That said, it doesn't discover DBs. I haven't seen any errors in the event log pertaining to the discovery. The bug fix posted above also hasn't helped me.
When trying to run this MP script manually it also returns XML:
http://blogs.technet.com/b/jimmyharper/archive/2009/06/11/sql-database-properties-not-discovered.aspx
So, I'm not really sure that is going on here. What is the expected return I am supposed to get.

SAP IDES ECC5.0 (SQL 2005 Database) installation Error at Database instan.

At the time IDES ECC 5.0 installation (SQL 2005 database), I was copy all DVD on Hard drive and start setup then at installation of database instance, following Errors are occured. so I cant continue with the installation, if anyone have installation guide/or solve the following error please mail me at [email protected]
from Log file SAPCLUST
Interface access functions from dynamic library dbmssslib.dll loaded.myCluster
(3.5.Imp): 613: error when retrieving table description for physical table AABLG.
myCluster (3.5.Imp): 614: return code received from nametab is 32
myCluster (3.5.Imp): 296: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: code page conversion failed
rc = 2
from sappool.log
Interface access functions from dynamic library dbmssslib.dll loaded.failed to read short nametab of table ARCH_NUM (rc=32)conversion failed for row 0 of table VARKEY = ⁘
(CNV) ERROR: code page conversion failed
So please send me solution/ or any configuration need for SQL 2005 / installation guide thanks

This may be hard disk problem, some file not able to write on HDD.
Regards
Rajnish

Run Reporting services 2005 with databases housed on SQL Server 2012?

Hi, I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade DB server to 2012 and would like to keep SSRS as 2005.As a second phase I will upgrade SSRS2005
to SSRS 2008. So I would be running something like this:
Server A: SQL 2005 Reporting Services
Server B: SQL 2012 database engine - housing ReportServer and ReportServerTempDB
Is this configuration supported?

Hello,
According to the
BOL, Report Server service checks the database version at startup. If the report server is connected to a database that is an earlier version, the report server will update the database during startup.If you have a newer report server database, you
cannot use it with an earlier version of a report server instances.
In that case, the earlier versions of SQL Server Database Engine that can be used to host the SSRS report server databases. For example, In SQL Server 2005 Reporting Services, we can use either SQL Server 2000 or SQL Server 2005 to host the databases, for
SSRS 2012, we can use SQL Server 2012,2008 R2,2008,2005.
Based on my test, In the Reporting Services 2005 Configure Manager, we can create a new database on a remote SQL Server 2012 database engine and the Initialization is successful.
In this way, the databases are created from the script file which installed with the Reporting Services instance, you can find the Catalog.sql and CatalogTempDB.sql under folder C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer.
However, when upgrade the existing ReportServer database and ReportServerTempDB database on the SQL Server 2012 by restore from a backup, we cannot use this existing database for Reporting Services 2005 and get the following message:
The database version (162) does not match your reporting serivces installation.And the initialization failed.
In your case, you can host the ReportServer database and ReportServerTempDB database of SSRS 2005 on SQL Server 2012 database enginer by create a new database from Reporting Services 2005 Configure Manager. But you cannot use the existing
database which upgrade to SQL Server 2012.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

JDBC - MS SQL Server 2005 with multible instances

I want to get data from a Microsoft SQL Server via JDBC. We have such a scenario and till now it works fine. Now we have a second instance at the sql server and we want to connect to this instance. I've found the following MSD article:
http://msdn2.microsoft.com/en-us/library/ms378428.aspx
SQL Server 2000 and SQL Server 2005 allow for the installation of multiple database instances per server. Each instance is identified by a specific name. To connect to a named instance of SQL Server, you can either specify the port number of the named instance (preferred), or you can specify the instance name as a JDBC URL property or a datasource property. If no instance name or port number property is specified, a connection to the default instance is created. See the following examples:
To use a port number, do the following:
jdbc:sqlserver://localhost:1433;integratedSecurity=true;<more properties as required>;
To use a JDBC URL property, do the following:
jdbc:sqlserver://localhost;instanceName=instance1;integratedSecurity=true;<more properties as required>;
Because the named instance has no explicit port I've tried to use the second one but this doesn't work. I've tried all possible combinations of these parameters but either I get an error or my adapter connects to the first instance
Any idea how I can connect to the second named instance?

We have also a SQL server 2000 instance at the same server. Yesterday I have spoken with the sql server admin and he told me that he has disconnect the sql server 2000 databases whatever this means. :-D
Now all works fine. Thank you for your help
BTW I use the following connection string:
jdbc:sqlserver://my_db_server;instanceName=my_instance_name;DatabaseName=my_db_name

MS SQL 2005 clustered database instance.

Similar Messages

Maybe you are looking for