What is SQL 2000 mode in SQL 2005 Server?

I have a application which will work in SQL 2000 (literally). I am upgrading my SQL server to 2005 from 2000. I want to know how to make SQL 2005 to function as SQL 2000 so that my application will continu working with 2005 too..?
In other words where is the option as "Run this program in compatibility mode for" like we have in Windows?
I appreciate all your help.
Ping me in Yahoo IM : rajeshtheodore too

Which Oracle product? You've only mentioned two Microsoft products and an unnamed application so far.
In other words where is the option as "Run this program in compatibility mode for" like we have in Windows?Do you mean an option in this application that works on SQL Server, or an option in SQL Server 2005? Why would we know anything about either of those?
~Edited by: William Robertson on Sep 23, 2008 7:25 AM~

Similar Messages

Sql 2000 Database upgrade to 2005

Hello,
Our active SAP system works on MS SQL Server 2000 Databases. Will
there be a trouble if we set up Solution Manager 4.0 directly on MS SQL
Server 2005 whose SQL servers versions are different? Can I learn your
suggestions?
Secondly, we are planning to upgrade SQL Server 2000 system to MS SQL
Server 2005 in 2 weeks. I would be glad if you could advise me any
document about this upgrading process.
Note: All systems are working Windows Server 2003 x64 platform.
Best regards
ismail Karayaka

I would be glad if you could advise me any document about this upgrading process.
Hello,
there is a document available called Upgrade to and Installation of SQL
Server 2005 in an SAP Environment
To get it go to
-> http://service.sap.com/instguides
-> on the left Other Documentation
-> Database Upgrades
-> MS SQL Server
-> Upgrade to and Installation of SQL Server 2005 for SAP
Hope it helps.
Regards,
Norman

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

Steps to install SAP 4.7 EE with MS SQL 2000: URGENT

Hi all Basis Guru's
We are planning to install SAP 4.7 EE with DB: MS SQL 2000 on our new IBM server, we are already running a SAP server on our OLD SERVER and we just want to install the same in the NEW IBM SERVER for which i am seeking some expert help.
I wanted a document which can show me the steps to install SAP 4.7 and also MS SQL 2000,
I have pdfs released by SAP which i got from service market place under instguides section, but they are not soo helpful as i am a jr consultant the termninology used by them is not in my understanding..
So i request all, to send in a document which can easily assist me in installing SAP 4.7 and Ms SQL 2000 in step by step process
Also is it neessary for me to install the SP3 for Ms SQL 2000.
Reward points for sure...
Plz do help me in this as, this task has to be completed by 03-08-07 EOD.
Million Thanks in Advance
Regards
Hari Haran.V

Hi Juan,
I have done all the pre-installation steps accoring to the SAP released doc from the service market place...
but i get an error during the installation of the CI...(this is happening at the time of EXTRA SAP SYSTEM KERNAL ARCHIVES)
Here is the detailed LOG of the error.....
INFO 2007-08-02 18:50:39
Processing of host operation t_HostInfo_SHARED succeeded.
INFO 2007-08-02 18:50:47
The 'saploc' share exists at directory 'C:\usr\sap'. Choosing drive C: as SAP System drive.
INFO 2007-08-02 18:51:13
Successfully connected to PDPLMAIN\PDPLMAIN
INFO 2007-08-02 18:51:13
Executing check Product Version ...
INFO 2007-08-02 18:51:13
Script "Product Version" successfully executed
INFO 2007-08-02 18:51:13
Executing check Product Patch ...
INFO 2007-08-02 18:51:13
Script "Product Patch" successfully executed
INFO 2007-08-02 18:51:13
Executing check Product Edition ...
INFO 2007-08-02 18:51:13
Script "Product Edition" successfully executed
INFO 2007-08-02 18:51:13
Executing check Collation ...
INFO 2007-08-02 18:51:13
Script "Collation" successfully executed
INFO 2007-08-02 18:51:13
Executing check SysAdmin Rights ...
INFO 2007-08-02 18:51:13
Script "SysAdmin Rights" successfully executed
INFO 2007-08-02 18:51:13
Successfully connected to PDPLMAIN\PDPLMAIN
INFO 2007-08-02 18:51:13
Executing check Database existance ...
INFO 2007-08-02 18:51:13
Script "Database existance" successfully executed
INFO[E] 2007-08-02 18:51:36
Account group="pdplmain\SAP_LDAP" does not exist. <#1>
INFO[E] 2007-08-02 18:51:37
Account group="ORA_PD0_DBA" does not exist. <#1>
INFO[E] 2007-08-02 18:51:37
Account group="ORA_PD0_OPER" does not exist. <#1>
INFO[E] 2007-08-02 18:51:49
Account group="pdplmain\dbpd0ctl" does not exist. <#1>
PHASE 2007-08-02 18:57:16
SAP Web Application Server
PHASE 2007-08-02 18:57:16
Request common parameters of SAP System
PHASE 2007-08-02 18:57:17
Collecting information on database configuration
PHASE 2007-08-02 18:57:17
Create operating system accounts
INFO 2007-08-02 18:57:17
Copying file C:/SAPinst MSSQL SAPINST/keydb.xml to: C:/SAPinst MSSQL SAPINST/keydb.1.xml.
INFO 2007-08-02 18:57:17
Creating file C:\SAPinst MSSQL SAPINST\keydb.1.xml.
INFO 2007-08-02 18:57:18
Copying file C:/SAPinst MSSQL SAPINST/product.xml to: C:/SAPinst MSSQL SAPINST/product.1.xml.
INFO 2007-08-02 18:57:18
Creating file C:\SAPinst MSSQL SAPINST\product.1.xml.
PHASE 2007-08-02 18:57:33
Preparing OS account for MCOD installation
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:33
Request operating system user information
PHASE 2007-08-02 18:57:34
Request operating system user information
PHASE 2007-08-02 18:57:34
Request operating system user information
PHASE 2007-08-02 18:57:34
Request operating system user information
PHASE 2007-08-02 18:57:34
Request operating system user information
INFO 2007-08-02 18:57:35
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1801674531-606747145-839522115-500' on host 'pdplmain'!
INFO 2007-08-02 18:57:35
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1801674531-606747145-839522115-500' on host 'pdplmain'!
INFO 2007-08-02 18:57:35
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1801674531-606747145-839522115-500' on host 'pdplmain'!
INFO 2007-08-02 18:57:36
Evaluating all 'tNT_RegistryEntries' table rows succeeded.
PHASE 2007-08-02 18:57:38
Preparing DBMS-specific environment variables
WARNING 2007-08-02 18:57:38
Error 1332 (No mapping between account names and security IDs was done.
) in execution of a 'SetEntriesInAcl' function, line (661), with parameter ().
INFO 2007-08-02 18:57:38
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:39
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:41
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:42
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:44
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:45
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:46
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:47
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:48
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:49
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:50
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:51
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:51
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:52
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:53
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:53
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:54
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-08-02 18:57:55
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
PHASE 2007-08-02 18:57:55
Adapt filesystem
PHASE 2007-08-02 18:57:55
Prepare check/adapt SAP instance filesystem
INFO 2007-08-02 18:57:55
Processing of all file system node operations of table t_SAPComponent_Filesystem_Action_SHARED succeeded.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/prfclog exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0 exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00 exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00/data exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00/data/cache exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00/exe exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00/log exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00/sec exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/DVEBMGS00/work exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/exe exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/exe/opt exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/exe/dbg exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/exe/run exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/gen exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/gen/dbg exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/gen/opt exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/global exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/profile exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/PD0/SYS/src exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap/tmp exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/tmp exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/EPS exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/EPS/in exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/EPS/out exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/EPS/log exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/bin exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/buffer exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/cofiles exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/data exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/etc exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/log exists already. Nothing to do.
INFO 2007-08-02 18:57:56
File system node C:\usr\sap\trans/sapnames exists already. Nothing to do.
INFO 2007-08-02 18:57:56
Copying file H:/sapinst_mssql/NT/I386/UNINSAP.EXE to: C:\usr\sap\PD0\SYS\exe\run\..\UNINSTSAP.EXE.
INFO 2007-08-02 18:57:56
Copying file system node H:/sapinst_mssql\NT\I386\UNINSAP.EXE with type NODE to C:\usr\sap\PD0\SYS\exe\run\..\UNINSTSAP.EXE succeeded.
INFO 2007-08-02 18:57:56
Processing of all file system node operations of table t_SAPComponent_Filesystem_Action_SHARED succeeded.
INFO 2007-08-02 18:57:57
Processing of all file system node operations of table t_SAPComponent_Filesystem_Action_SHARED succeeded.
INFO 2007-08-02 18:57:58
Creating of all NT shares while processing the table 'tNT_SHARE' succeeded.
INFO 2007-08-02 18:57:58
Creating of all NT shares while processing the table 'tNT_SHARE' succeeded.
WARNING 2007-08-02 18:57:59
The specified service does not exist as an installed service.
! Error in execution of a 'OpenService' function, line (286), with parameter(s) (SAPPD0_00).
WARNING 2007-08-02 18:57:59
The specified service does not exist as an installed service.
! Error in execution of a 'OpenService' function, line (286), with parameter(s) (SAPOsCol).
PHASE 2007-08-02 18:57:59
Extract archives
INFO 2007-08-02 18:58:00
Processing of all file system node operations of table t_SAPComponent_Archives_FORMS_SHARED succeeded.
PHASE 2007-08-02 18:58:01
Extract SAP System kernel archives
INFO 2007-08-02 18:58:01
Creating file C:\SAPinst MSSQL SAPINST\SAPEXE.SAR.log.
ERROR 2007-08-02 18:58:01
MOS-01021 PROBLEM: .\sapcar.exe -xvgf H:\SAP_KERNEL_MSSQL_IA64/NT/I386/SAPEXE.SAR, -R C:\usr\sap\PD0\SYS\exe\run returned with '29'. CAUSE: See output './SAPEXE.SAR.log'. SOLUTION: Solve the CAUSE and retry.
ERROR 2007-08-02 18:58:01
FJS-00012 Error when executing script.
Waiting to hear from at the earliest
Regards
Hari haran.v

SQL 2012 Linked Server connection from SQL 2000

Hi,
Does anyone know if it's possible to create a linked server connection in SQL 2000 to a SQL 2012 instance?
If so, which provider should I use?
Many Thanks,
Phil

Hi Shanky,
I'm afraid you misunderstood my Q. The above posts show how to create a linked server connection FROM SQL2012 --> SQL 2000.
I'm trying to create a linked server connection FROM SQL 2000 --> SQL 2012.
Does anyone know if it's possible?
Many Thanks,
Phil
I guess you dont read posts patiently below link ,which i also posted in my first reply, has details about the same
http://social.msdn.microsoft.com/Forums/en-US/2e02c603-e28d-49eb-b073-548c59732b5d/linked-server-from-sql2012-to-sql2000?forum=sqlsetupandupgrade
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL 2000 XML Support

I have a simple SQL from which i get XML data from the SQL 2000 Database.
SQL :
select * from customer for xml auto
I would like to execute the SQL thru JDBC, but i am getting the following error
java.sql.SQLException: [MERANT][SequeLink JDBC Driver][SQL Server]The FOR XML clause is not allowed in a CURSOR statement.
Note : I am using merant driver.
Any info on this is greatly appreciated.
Thanks in advance

Get rid of the selectMethod=cursor from your connection Url
eg. if you have a Connection String like
jdbc:microsoft:sqlserver://yourserver:portnum;database=mydatabae;selectMethod=cursor;

Database in Suspect Mode in SQL Server 2000 Log Shipping Environment

Hi All
We have movement of SQL Server 2000 at physical level. We have disable jobs and stop Agent and SQL Server services.
After moved the server we have started the server and then start SQL Server 2000 services.
All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance

All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance
Hello,
Did you made sure no transactions like restore logs were running when you stopped SQL server service or agent .I have seen in SQL 2000 an abrupt stop of SQL Server agent when its doing a process can sometimes force database in suspect mode.
I would like you to get your disk analyzed by vendor ASAP for any fault in disk at first go it seems to me an underlying hardware issue.
Please can you check errorlog and event viewer to find out any possible cause for database going into suspect mode
I always suggest to use Backup and restore method of recovery to get out from suspect database problem.If you dont have then you can move with DBCC Checkdb and various repair options but be sure
DATA LOSS might be possible when you use repair allow data loss and repair_rebuild removes constraints.
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Custom DTS package migration from BPC 4.2 ,SQL 2000 to BPC 7.0 M , SQL 2005

Is there any changes required in the custom dts package when migration from BPC 4.2 , sql 2000 Environment to bpc 7.0 , SQL 2005/2008 Environment.
or
Please suggest process for migrating custom dts package from BPC 4.2 ,SQL 2000 Envirnment to BPC 7.0 ,SQL 2005/2008 Environment

When you say "custom dts package" that can mean many different things. What type of customization has been done?
There are a few BPC-related features which changed from 4.2, which must be manually adjusted, if you're using those features.
But SQL itself also changed dramatically in moving from SQL 2000 to 2005. So if your customer's packages are heavily customized around SQL 2000, this may require substantial re-work.
The only migration process for custom DTS packages -- that I'm aware of -- is to use the SQL 2005 migration tool in SSIS, see how much it messed up, and then fix everything else that's still broken.
But there also may be opportunities to improve the package overall. SQL 2005 has a lot of great new features in SSIS, over what was there in SQL 2000.
I haven't started working with SQL 2008 yet, so I can't say what complexity there is in upgrading DTS packages from 2005 to 2008. From what I read in the BPC 7 release notes, it sounds like it's a very minor upgrade, compared to the jump from 2000 to 2005.

SQL 2000 or SQL 2005

Dear All,
I want to know which SQL database you think is secure and safe for SAP Business One 2005B.
Should the client install SQL 2000 or SQl 2005. What is your exprience for it.
Regards

I would say more than Security, SQL Server 2005 is recommended for SBO2005.
Please read documentation available on this Page.
https://websmp108.sap-ag.de/smb/sbo/documentation
Suda

Full list of MS SQL 2000 features that are supported in compatibilty 80 mode but not available in 2008 R2 compatibility 100

Hello Everyone,
Could you possibly suggest where I can find a full list MS SQL 2000 features that are supported in 2008 R2 compatibilty 80 mode but not available in compatibility 100?
Thanks
SSIS question

Hi Tom,
What you are saying makes sense, if the compatibility level is 90 then the old ANSI joins are expected to be rectified.
I wrote a script to check - it's an easy exercise, all you need is to loop through the catalog views and for each SP or scalar function run this command:
set fmtonly on exec <object> set fmtonly on and in the catch block handle the error related to compatibility.
For checkign the views similar thing set noexec on <select top 1 * from view> set noexec off.
This works very fast as none of the code is actually executed.
Caveat thought triggers and table functions. I could not find the way how to check them. so will have to extract the DDLs and just check the text for old ansi joins. Not very reliable, but that's all I can think of at the moment.
Any chance you know how to compile a trigger or table function without running.
For table functions when I tried set noexec on they still asked for parameters, something I was trying to avoid.
Thanks
SSIS question

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.

Can SQL 2000 and SQL 2005 drivers co-exist in PI?

Hi,
Currently in our PI environment, we have JDBC Adapter connections to SQL 2000 database servers for which the Driver has already been installed.
For connecting to new SQL 2005 database servers, I understand that we have to install the SQL 2005 drivers. I also came to know that SQL 2005 Driver is backward compatible and supports JDBC connection to SQL 2000 server.
But the question I have is whether both the SQL 2000 and SQL 2005 drivers can be installed together in a way that connection to SQL 2000 use the 2000 driver and the connection to 2005 uses 2005 Driver.
(They have different connection strings)
Many thanks in advance,
Regards,
Rosie Sasidharan

The SQL Server 2005 JDBC driver is far better than the SQL Server 2000 JDBC driver. The 2005 JDBC driver primarily consists for one file, sqljdbc.jar. ( if you want to use windows authentication there is another file you would need based on your platform x64 vs x86 called sqljdbc_auth.dll. If in the connect string you list ;integratedSecurity=true which means integrated security would be used and this second file would be required. The 2000 driver did not support integrated security.
The SQL 2000 JDBC driver was made up of the 3 jar files:
msbase.jar,mssqlserver.jar and msutil.jar.
If you want to use a Microsoft JDBC driver to connect to SQL Server 2005, than you should use the 2005 driver, sqljdbc.jar.
Follow the instructions in point 1 of the note #831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter questions 1 and 13.
Since the jar are different I assume you can use the both drivers, but it doesnt make sense.

Database restore from SQL 2000 to SQL 2005 for SBO 2005B

Hi Everyone,
I am facing some problems in regards to the restore of SBO Database from SQL 2000 to SQL 2005.
Let me explain you the problem.
See I am using SAP B1 2005B with patch level 38 in my laptop with SQL 2000. I have made an company in this and done work in it as a production company and now I want to restore this company in the server which has SQL 2005. How to do it.
I have taken a backup in my laptop from SAP B1 Server Suite Manager which has SQL 2000 and sucessfully backed up but when I am trying to restore in the server which has SQL 2005 I am getting the following error in SQL 2005 in server :-
Restore failed for Server 'DXBAP001'. (Microsoft.SqlServer.Smo)
System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program Files\Microsoft SQL Server\MSSQL\data\SBO_DCHAR.mdf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Smo)
Please let me know the solution for it.
Thanks in Advance.
Regards,
Kawish Junaid Mazhari

Hi,
In SQL 2005 create a database and name as the 200 one was (though any name would do). when you create the database note the location of the .mdb and .ldf file.
once this had created right click on your new database > tasks > restore database
in the new window select from device and point it to your .bak file created from your 2000 system, ensure you put a tick in the restore box on the new line.
in the options tab tick overwrite database, and, change the file locations in the restore as directory to the file locations of the new database. the file names must be the same too.
you can change the original file names after the restore.
that should do the trick.
thanks,
mike

Installation of Golf Program requires uninstalling Microsoft SQL 2005 and installing SQL 2000

I am running Win 7 and about to purchased a new computer with Win 8.1.
The USGA wrote a Tournament Program which is used nationwide called TPP (Tournament Pairing Program). It was developed prior to XP but it is updated every time you run the update. It runs on XP without any adjustments. To load the program
on Win 7 or Win 8 you are instructed to remove Microsoft SQL Server 2005, which I did. The program loads SQL 2000 when it is installed. I am concerned when I uninstall the TPP program that it will also uninstall SQL 2000 (which it installed) and
then there will be no SQL server on my Win 7.
I was going to make sure that I could install the TPP program on Win 8 (before buying another computer) by installing it on a friends new Win 8.1 computer. But I am concerned about removing the preinstalled SQL Server program.
1) How does one get the original Microsoft SQL Server back once it has been removed and the recycle bin has been emptied? Does the SQL program even get sent to the recycle bin when it is removed?
2) Is there any harm done by removing the original SQL program be it 2005 or a new one?

SQL 2000 is not supported on Windows 7.
http://support.microsoft.com/kb/2028963/en-us
whenever you uninstall SQL Server, databases files are not deleted. So you can move them to safe location. if they are delete by you then you have very less chances to recover the data.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

SQL 2000 AND SQL 2005 ON THE SAME SERVER

Hi all ,
I have an installation of SAP4.7SR1 /MSSQL2000 on a windows 2003 server.
I want to install SAP SOLUTION MANAGER 4.0 /MSSQL2005 on the same server ... it is possible that two version of SQL ( 2000 and 2005 ) coexists on the same server ? It's sufficent to install SQL into two different directory ?
Thank's a lot.
Antonio Voce.

Hi,
yes it is possible to install SQL2000 and SQL2005 on same server but there are certain special considerations that you should be aware of
look at following blog
http://blogs.msdn.com/sqlblog/archive/2006/09/27/co-existence-of-sql-2005-with-sql-2000.aspx
also look http://msdn2.microsoft.com/en-us/library/ms143694.aspx
but in case of SAP Installation i prefered that to upgarde SQL2000 to SQL2005 then install solman 4.0
regards,
kaushal

What is SQL 2000 mode in SQL 2005 Server?

Similar Messages

Maybe you are looking for