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!

Similar Messages

Error export from my database sql 2005 with Windows 2003 abap+java

Hi all
I'm trying to create an Export from my database sql 2005 with Windows 2003, but SAPINST starts with an error. ABAP+JAVA stack
While running the export preparation, I am getting the following error;
INFO 2010-09-08 12:12:43
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key is written to the logfile C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log.
WARNING 2010-09-08 12:12:46
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key" finished with return code 64. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
ERROR 2010-09-08 12:12:46
CJS-30071 Execution of UTL tool 'C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key' aborts due to database connection error with return code 64. DIAGNOSIS: The connection parameters are wrong or the database server is shutdown. SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log' for more information.
ERROR 2010-09-08 12:12:46
FCO-00011 The step getUsageTypes with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_Java_Prepare_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
Could anyone please help me out on this, if possible?
Thanks
JM

Hi,
please ensure that you use a SAP supported JDK as below:
716604 for the Sun JDK (Windows, Linux, Solaris)
709140 Recommended JDK and VM Settings for the WebAS630/640/7.0
And the re try the export pls.
Regards,
Snow

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

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

SQL 2005 with ERP2005 (ECC 6.0) Unicode

Hi All,
I need a few questions to be answered.
Can anybody tell me as to what would be the initial size of the database after an installation of ECC 6.0 Unicode with database as SQL 2005.
Is there any minimum hardware requirements that would have to be taken into consideration before an installation is planned.
Can anyone help me in deciding whether MSCS services or Manual Log shipping would be preferred for Failovers.....
Regards
Anand

Sizing
Hardware sizing should be completed by your SAP partner. Its based on many things. Users, modules, storage volumes, peek, BP, workloads etc etc.
You can do the 'noddy' version with the sapsize on OSS. The output from this is in 'SAPs' you could look up std systems bench marks and get something 'like' it. Else submit the results to the hardware vendor of your choice and they will do it for you.
System Redundancy
Depends what you are trying to do.
MSCS is a fail over HARDWARE only solution. ie if you want to patch or take a node out of service you can by 'failing over' the services on it to the other node. If you get a DB problem MSCS can not help you at all.
Log shipping gives you 'rapid' recovery options for SQL(and there in SAP). The way this normally works is via either manual or automatic log-shipping to a 'standby' system with SQL/SAP loaded on it that can be brought online if you get a problem with the main system.
A well planned system will have fail-over and recovery capabilities, ie it will use BOTH.

Back-up SQL 2005 with NTBACKUP and Volume Shadow Copy

Hi everybody,
I want to make a snapshot backup of a SQL 2005 database with SAP ECC6.
I want to use NTBACKUP to make the snapshot.
Does the database freeze at the moment of the snapshot?
Does anybody use this method?
Thanks in advanche.
Kind regards,
Klaas van Deelen

NTbackup uses VSS to create the copy of FILES.
VSS is not designed to replace your current backup strategy,
VSS will copy a data file, then another, then another etc - heres the problem sapdata1 and sapdata2 will be backed up at DIFFERENT times. if you tried to restore the DB, it would NOT be consistent.If VSS backed up the files OFFLINE - np, it will work.
VSS cache is also on the system (default) as the original data - not really a smart idea for a backup solution.
Use either the SQL tools to backup online to tape/external storage or get the symantec backupexec with the SQL agent to allow for online backups again to tape or nearline storage.

SQL 2005 with BRIO Inelligence

We are using Brio Intelligence Version 6.6 and we are getting aSQL 2005 server. Will we be able to connect to thisserver.

It depends on what you are using the SQL Server 2005 for. If youare trying to query the SQL 2005 data using standard ODBC compliantdrivers, I think it should work (I haven't tested). But if you areusing the SQL 2005 database as a repository database, it is notsupported per the platform matrix.

How to Install SQL 2005 with command MS SQL 2005.

Hello All,
Where can I get the guide for installaling ECC 6.0+MS SQL 2005/2008 from command prompt.
I checked the standard work guides at market place but no hint found for command line installation.
Please help me.
Thanks,
Anu

Wrong subject line

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

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

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

SQL 2005 fixed memory

Hi ,
I have SAP 47X200 on SQL2005 64-bit installed on Windows enterprise edition X64.
I have installed database software using SQL4SAP.vbs as decrived in the installation guide : all OK , all work fine.
But , I want to use SQL 2005 with fixed memory as descrived in the article http://msdn.microsoft.com/en-us/library/ms191144.aspx
but in the server page proprierties box Memory i don't have the flag box Dynamic memory configuration but only Minimum server memory and Maximum server memory : if I set this two last value the same , the minimum server memory real is under this parameter.
So anyone know whi ? How to set fixed server memory ? Whi I don't have this flag?
thks Antonio Voce
Reward point for you.

Hi ,
I set as you tell and now in database server proprierties under memory box i have this value :
Minimum server memory : 12000
Maximum server memory : 12000
Index creation memory : 12000
I have rebooted the server , starded SAP but in st04 I still see that the database memory is dynamically assigned :
Microsoft SQL Server 2005 - 9.00.3054.00 (X64) ##M Enterprise Edition
Windows NT 5.2 (Build 3790: Service Pack 2)
Database    R3A        Schema r3a                     Time of analysis   13.06.2008 16:38:46
DB Server   SAPPONE                                   DB startup         06/13/2008 16:35:38
CPUs available for SQL Server 16 of 16               Physical memory MB              32.765
Trace flag                                                                   SAP release 620
Memory Usage
Current memory      KB              600.320    Total SQL connections                    61
Maximum memory      KB           12.288.000          R/3 connections                    60
Memory setting                         RANGE   Free pages                              675
Procedure cache     KB               58.163    Data cache size     KB              534.274
      hit ratio      %                   87          hit ratio      %                   93

ALUI 6.x SQL 2005 SP3

Is anyone running ALUI 6.x on MS SQL Server 2005 SP3?
We are being told my Microsoft that we need to apply SP3 to our SQL servers by the end of the year to maintain support.
Oracle is telling us that ALUI 6.x is not certified on SP3. I would think with Applications Unlimited Oracle would want to certify applications on newer database levels.
ALUI 6.1 - MS SQL Server 2005
ALUI 6.1 MP1 - MS SQL Server 2005 SP2
ALUI 6.5 and 6.5 MP1 - MS SQL Server 2005 SP2
WCI 10.3.0 - MS SQL Server 2005 SP2 and higher

Hi Tim,
To argument what Mike stated....
Take a look at the interoperability matrix here:
[http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/BIDExtInteroSupportMatrix3.xls#PortalWksheet|http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/BIDExtInteroSupportMatrix3.xls#PortalWksheet]
This is considered the most up-to-date document on supported configurations against the Web Center Interaction product line.
You can see here for for WCI 10.3.0.0 the product is certified against SQL 2005 with SP2^. The symbol ^ next to SP2, indicates we support Service pack 2 or higher (ie SP3). Keep in mind with all SQL server 2005 databases we still require them to run in SQL 2000 compatibility level.
6.5 and 6.5mp1 it is certified against SQL 2005 SP2 (but not SP3).
6.1 MP1 is certified against SQL 2005 SP2 (but not SP3).
6.1 is certified against SQL 2005
6.0.x is not certfied against SQL 2005
By certified this means that these products have had full test cycles against these versions of the database.
While support will attempt to assist you with technical issues, if your 6.x alui portal is installed against an uncertfied version of SQL server, and it comes down to the problem being caused by you being on that uncertfied version of db, then you might need to downgrade your database to a certified release. And I would think this would be unlikely, but it's good to be aware of.
The recommendation would be for you to work towards upgrading your portal from 6.x to 10.3 which is supported against SQL 2005 SP3.
Hope that clarifies things.
Regards,
RyanO
WCI Support

SQL 2005 SAP R/3 4.6C - DBSL error RC=99 on import of Basis 4.6C SP 39

Hi,
I have just built a R/3 4.6C system on SQL 2005 with 4.6D_EXT kernel. The build was done using R3load to export from the 4.6C/SQL 2000/32bit system and import to 4.6C/SQL 2005/64bit system. The source 4.6C system only had Basis support package 37 applied, and I am trying to apply Basis 4.6C 38-57 on the 4.6C/SQL 2005/64bit system (in preparation for an ECC6 upgrade) and I get the following error:
EXEC SQL: SELECT ID,OBJECT,LANGU,TYP,VERSION FROM DOKIL WHERE (LANGU IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,
[developertra,00000] ExecuteAndFlush return code: 0x80040e10 Stmt: [CREATE PROCEDURE ##Y8IBASAPDEIBD00000025600000000006164133 @P
 99972 0.099972
[developertra,00000] MapHr:80040E10 DB_E_PARAMNOTOPTIONAL 43 0.100015
[developertra,00000] HandleOledbError [ExecuteAndFlush,line 33423]: Error/Message: (err 0, sev 0), No value given for one or more
 96 0.100111
[developertra,00000] DbSlPrepare - Error 99 (dbcode -2147217904) on proc. creation
56 0.100167
[developertra,00000] DbSlPrepare - <CREATE PROCEDURE ##Y8IBASAPDEIBD00000025600000000006164133 @P000 varchar(3072) = ' ', @P001 v
 105 0.100272
[developertra,00000] 1 times error (0,0) in sequence 30 0.100302
[developertra,00000] dbdsmss: DBSL99 SQL0 27 0.100329
[developertra,00000] No value given for one or more required parameters.
62 0.100391
[dbds ,00589] ***LOG BY2=>sql error 0 performing FET
66 0.100457
[dbds ,00589] ***LOG BY0=>No value given for one or more required parameters.
I have checked the collation setting in SQL 2005 and it is:
select serverproperty('collation')
SQL_Latin1_General_CP850_BIN2
There are 97000 odd entries in DOKIL, so I don't think that is the problem.
Would appreciate any assistance.
Kind regards,
Sheryl.

Hi ,
Instead of doing the build with export import, you can try to do the same with backup restore,,
But remember your sql2000 should be on bin2... then you can take backup and restore.
Since it is from 2000 to 2005 the restore would happen and it will work fine.
Try this and check out, since the error you have pasted is not clearly giving any picture...
Regards,
Ravi.

SQL 2005 with database compatibiltiy level set to 80

Similar Messages

Maybe you are looking for