Arc is not implemented for SQL Server 2005 physical model

I added the Arc in my relational model, which is supposed to provide that references are mutually exclusive (so only one refering column can be not null). However there is not any implementation for this in the SQL Server 2005 physical model. The SQL code generated simply ignores the Arc and allows any values for the columns covered by Arc. If we check Oracle physical model. then it generates some trigger, which controls how many columns have values assigned - this is actually an implementation of Arc. But there is nothing of this kind for SQL Server model...
By the way, implementing this Arc by trigger looks like to heavy approach. The very simple table level check constraint will do the same job. But this is a different subject though.
Edited by: Otbl on Nov 3, 2011 7:34 PM

Hi Dmitry,
it's fixed in Data Modeler 3.1 EA2.
Philip

Similar Messages

Non Clustered Indexing not working for SQL server 2005

I have create two non clustered index on two particular tables. Now the problem is its working fine..but after restarting my server its working stop and then again I have to delete that index and recreate it.

try these links
http://blog.sqlauthority.com/2009/02/07/sql-server-introduction-to-force-index-query-hints-index-hint/
http://blog.sqlauthority.com/2009/02/08/sql-server-introduction-to-force-index-query-hints-index-hint-part2/
http://www.brentozar.com/archive/2013/10/index-hints-helpful-or-harmful/
Hope it Helps!!

Deploy JDBC driver for SQL server 2005 on PI 7.1

How to deploy JDBC driver for SQL server 2005 on PI 7.1
We are in SAP NetWeaver 7.1 Oracle 10G
Third party system is SQL server 2005
There are different JDBC versions are available to download for SQL server 2005.
I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
Please help

Hi,
Hope this How to Guide help you.
How To Install and Configure External Drivers for the JDBC & JMS Adapters from
www.sdn.sap.com/irj/sdn/howtoguides
Regards,
Karthick.
Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM

Deploying JDBC driver for SQL Server 2005 on PI 7.1

How to Deploy JDBC driver for SQL Server 2005 on PI 7.1 on Windows 2003 server
We are in NW PI 7.1 and third party db is sql server 05.
Found How-to Guide SAP NetWeaver u201804 but unable to find for NW PI 7.1
Can any one help me on this? (looking for guide step by step procedure)
Regards
Mahesh

Hi,
Check these:
Re: Installing JDBC Drivers for PI 7.1
how to deploy MS Sql Server 2005 and 2008 jdbc driver
Mention of a SAP Note in the first link or refer this note [831162|https://service.sap.com/sap/support/notes/831162]
Regards,
Abhishek.

Error deploying JDBC driver for SQL Server 2005

Hi all
I'm trying to deploy a JDBC driver for MS SQL Server 2005 (downloaded [here|http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en]). When I try to deploy it according to the instructions found [here|http://help.sap.com/saphelp_nwce10/helpdata/en/51/735d4217139041e10000000a1550b0/frameset.htm] it fails.
The error in the logs doesn't give any useful information though. It only says Error occurred while deploying component ".\temp\dbpool\MSSQL2005.sda".
Has anyone else deployed a driver for SQL Server 2005, or perhaps have any suggestions of what else I could try?
Thanks
Stuart

Hi Vladimir
That's excellent news! Thanks for the effort you've put into this. I'm very impressed with how seriously these issues are dealt with, specifically within the Java EE aspects of SAP.
May I make two suggestions on this topic:
1. Given that NWA has such granular security permissions, please could the security error be shown when it is raised? This would help immediately identify that the problem isn't actually a product error, but rather a missing security permission (and thus save us time and reduce your support calls).
2. Please could the role permissions be clearly documented (perhaps they already are, and I just couldn't find the docs?) so we know what is and isn't included in the role. The name is very misleading, as a "superadmin" is generally understood to have no limitation on their rights - so clear documentation on what is in-/excluded would be most helpful.
On a related topic, I came across another issue like this that may warrant your attention (while you're already looking into NWA security issues). I logged a support query about it (ref: 0120025231 0000753421 2008) in case you can retrieve details there (screenshots, logs, etc.). It's basically a similar security constraint when trying to create a Destination. I'm not sure if this is something you would like to include as standard permissions within the NWA_SUPERADMIN role or not, but I think it's worth consideration.
Thanks again for your help!
Cheers
Stuart

HotFix4 for SQL Server 2005 doesn't work

I am having problems getting a machine running SQL Server 2008 R2 (Express) to connect to a SQL Server 2005 (Full Standard Edition) DB on another machine via the LAN. It times out when connecting from a C# application. SSMS on the SQL 2008 machine
connects fine, but SSMS on the 2005 machine (connecting to a copy of the same DB on the 2008 machine) says it isn't supported and I need a hotfix.
I downloaded the hotfix link from Microsoft, but when I paste it into the Browser I get a DNS name failure for the Hotfix4 server. I don't want to paste the full link here because it is not made public by MS and you need to request it. However, the
first part of the URL is: http://hotfix4.microsoft.com/SQL%20Server%202005...etc.
I have checked out all of the obvious things in both instances (2005 AND 2008)... Both instances are configured to accept remote connections, both have TCP/IP and named pipes protocols enabled, both are running fine for local connections, both have the SQL
Browser enabled and the Computer Browser Service running on the network.
As the hot fix doesn't install, I am kind of out of ideas.
Any suggestions?
Thanks,
Pete
I used to write COBOL... now I can do anything.

SQL 2005 is out of
mainstream support:
SQL Server
2005
SP4
04/12/2011
04/12/2016
Technical support continues till 04/12/2016, yet mainstream (hotfix) support ends as of 04/12/2011; options
for hotfix support after 04/12/2011:
ð  Continue
with self-help
ð  Upgrade
to the latest supported service pack for SQL Server 2005 or SQL Server 2008 or SQL Server 2008 R2
ð  Extended
hotfix support agreement
SP4 and CU3 are still available for download, if this helps...
http://support.microsoft.com/kb/2507769
http://www.microsoft.com/en-US/download/details.aspx?id=7218
But you should update your SQL-Server..... SQL 2014 is the latest version

DB mail not working in sql server 2005

Hi,
from today i get following error on sql server 2005
Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException
Message: There was an error on the connection. Reason: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void OpenConnection(Microsoft.SqlServer.Management.Common.SqlConnectionInfo)
I can not send the mail.I am sending the mails same profile that configured.Before it is working perfectly.Today I send the bulk mails(near about 4000-5000 mails) through the java code. And from that time i can not get any mails.
Please tell me how to solve the problem?

Hello,
Please refer to the following thread:
https://social.technet.microsoft.com/Forums/en-US/c8fa3c2d-9e8a-4886-97bf-264c1b8bc31c/throttling-settings-for-sending-more-that-1500-emails-simultaneously-using-sql-job?forum=exchangesvrsecuremessaging
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Agent - Job History not being recorded (SQL Server 2005)

I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
returns an error, detailed below.
Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
Many thanks in advance for anyone's time and help with this issue!
Arthur
The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
===================================
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
Server Name: 127.0.0.1,1344
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
at sqlprov.MainForm.ProvisionTasks()

Hi Rama,
Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
active directory controller, etc) so I don't understand how the Windows login cannot be verified.
Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
Many thanks!
Arthur

Addon in Client is not connecting to SQL Server 2005

Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
Does anyone knows how to fix this issue?
Thanks

Hi Alejandro, thanks for your response.
After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
I had checked the SQL to confirm is was allowing remote connections.
Thank you guys.

How do I install the jdbc driver for sql server 2005, in sql developer 4.0 ?

Hallo together
I need access to tables in a MS SQL Server 2005 database.
One possibility is the JDBC driver.
How do i install this driver ?
Thank you very much for your postings.

Hi,
This is from the documentation -
Database: Third Party JDBC Drivers
The Third Party JDBC Drivers pane specifies drivers to be used for connections to third-party (non-Oracle) databases, such as IBM DB2, MySQL, Microsoft SQL Server, or Sybase Adaptive Server. (You do not need to add a driver for connections to Microsoft Access databases.) To add a driver, click Add Entry and select the path for the driver:
For Microsoft SQL Server or Sybase Adaptive Server: jtds-1.2.jar, which is included in the jtds-1.2-dist.zip download
To find a specific third-party JDBC driver, see the appropriate website (for example, http://www.mysql.com for the MySQL Connector/J JDBC driver for MySQL, http://jtds.sourceforge.net/ for the jTDS driver for Microsoft SQL Server and Sybase Adaptive Server, or search at http://www.teradata.com/ for the JDBC driver for Teradata). For MySQL, use the MySQL 5.0 driver, not 5.1 or later, with SQL Developer release 1.5.
You must specify a third-party JDBC driver or install a driver using the Check for Updates feature before you can create a database connection to a third-party database of that associated type. (See the tabs for creating connections to third-party databases in the Create/Edit/Select Database Connection dialog box.)
Alternative:
As an alternative to using this preference, you can click Help, then Check for Updates to install the JTDS JDBC Driver for Microsoft SQL Server and the MySQL JDBE Driver as extensions.
Regards,
Mike

Security Update for SQL Server 2005 SP3 (KB2494113) failed

Here is the Error, Can't get the update install, please help.
KB Number: KB2494113
Machine: MJA01
OS Version: Server 4.0 Service Pack 1 (Build 7601)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4060
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (BKUPEXEC) ENU SP3 2005.090.4035.00 x86 EXPRESS
SQL Server Tools and Workstation Components 2005 ENU SP2 9.2.3042 x86 EXPRESS
Products Disqualified & Reason
Product Reason
SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 4035 installed. Update 4060 is dependent on prerequisite update 4035. Exit setup and refer to the Knowledge Base article to find the prerequisite
patch. Install the prerequisite and rerun the installation.
Processes Locking Files
Process Name Feature Type User Name PID
Product Installation Status
Product : SQL Server Database Services 2005 (BKUPEXEC)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Product : SQL Server Tools and Workstation Components 2005
Product Version (Previous): 3042
Product Version (Final) :
Status : NA
Log File :
SQL Express Features :
Error Description : The product instance SQL Tools does not have prerequisite update 4035 installed. Update 4060 is dependent on prerequisite update 4035. Exit setup and refer to the Knowledge Base article to find the prerequisite
patch. Install the prerequisite and rerun the installation.
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29528

Hi Bhanu,
I have uninstall the SQL Server Tools and Workstation Components 2005.
But still unable to upg the SQL Server with the KB249411. Any more ideas?
This is the Summary log.
Time: 09/10/2014 11:09:48.218
KB Number: KB2494113
Machine: MJA01
OS Version: Server 4.0 Service Pack 1 (Build 7601)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4060
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (BKUPEXEC) ENU SP3 2005.090.4035.00 x86 EXPRESS
Products Disqualified & Reason
Product Reason
Processes Locking Files
Process Name Feature Type User Name PID
Product Installation Status
Product : SQL Server Database Services 2005 (BKUPEXEC)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29528
Here is what is log in the SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files (x86)\Common Files\
MSI (s) (B8:F0) [11:09:39:826]: Product: Microsoft SQL Server 2005 Express Edition - Update 'GDR 4060 for SQL Server Database Services 2005 ENU (KB2494113)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program
Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log.
MSI (s) (B8:F0) [11:09:39:827]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.3.4035.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: GDR 4060 for SQL Server Database
Services 2005 ENU (KB2494113). Installation success or error status: 1603.
MSI (s) (B8:F0) [11:09:39:828]: Note: 1: 1729
MSI (s) (B8:F0) [11:09:39:828]: Product: Microsoft SQL Server 2005 Express Edition -- Configuration failed.
MSI (s) (B8:F0) [11:09:39:829]: Windows Installer reconfigured the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.3.4035.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error
status: 1603.
MSI (s) (B8:F0) [11:09:39:829]: Attempting to delete file C:\Windows\Installer\63906e.msp
MSI (s) (B8:F0) [11:09:39:829]: Unable to delete the file. LastError = 32
MSI (s) (B8:F0) [11:09:40:092]: Deferring clean up of packages/files, if any exist
MSI (s) (B8:F0) [11:09:40:092]: Attempting to delete file C:\Windows\Installer\63906e.msp
MSI (s) (B8:F0) [11:09:40:094]: MainEngineThread is returning 1603
MSI (s) (B8:6C) [11:09:40:097]: RESTART MANAGER: Session closed.
MSI (s) (B8:6C) [11:09:40:097]: No System Restore sequence number for this installation.
=== Logging stopped: 9/10/2014 11:09:39 ===
MSI (s) (B8:6C) [11:09:40:098]: User policy value 'DisableRollback' is 0
MSI (s) (B8:6C) [11:09:40:098]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:6C) [11:09:40:098]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (B8:6C) [11:09:40:099]: Restoring environment variables
MSI (s) (B8:6C) [11:09:40:099]: Destroying RemoteAPI object.
MSI (s) (B8:30) [11:09:40:099]: Custom Action Manager thread ending.
MSI (c) (FC:60) [11:09:40:100]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (FC:60) [11:09:40:101]: MainEngineThread is returning 1603
Thanks,
Alice

Cannot set up data source for SQL Server 2005

Is it possible to use Microsoft's Beta 2 version of the SQL Server 2005 JDBC driver with WebLogic 9.0? I've downloaded the driver and added it to my server classpath, but when I try to create a new data source using the admin console, the drop-down list for Microsoft SQL Server only contains drivers for the 2000 version. If I select "Other" from the list and try to move on, I get a cryptic, page-long error on the admin console. If I just select the 2000 driver and try to manually modify the parameters on the next set of screens, I still get errors when I try to test the configuration. I've successfully used a third-party driver before, but this one does not seem to be working. Any help would be greatly appreciated.
Regards,
Sabrina

SabrinaL wrote:
Is it possible to use Microsoft's Beta 2 version of the SQL Server 2005 JDBC driver with WebLogic 9.0? I've downloaded the driver and added it to my server classpath, but when I try to create a new data source using the admin console, the drop-down list for Microsoft SQL Server only contains drivers for the 2000 version. If I select "Other" from the list and try to move on, I get a cryptic, page-long error on the admin console. If I just select the 2000 driver and try to manually modify the parameters
on the next set of screens, I still get errors when I try to test the configuration. I've successfully used a third-party driver before, but this one does not seem to be working. Any help would be greatly appreciated.
Regards,
SabrinaHere I describe the steps I took to bypass the console in making a new pool.
1 - Edit the script %DOMAIN_HOME%\bin\startWebLogic.cmd to add a line like this:
set CLASSPATH=%CLASSPATH%;\new_ms_driver\beta2\sqljdbc_1.0\enu\sqljdbc.jar
In other words, you have to explicitly add a third party driver's classes to
the CLASSPATH that will be in effect for the server. Just adding the driver
to your window's class path will do nothing.
2 - Go to the directory %DOMAIN_HOME%\config\jdbc, where you will find
files of the name *-jdbc.xml. Each of these represents a DataSource.
Copy one of them, perhaps either examples-demo-jdbc.xml, or
examples-demoXA-jdbc.xml depending on whether you want to make an XA
or non-XA pool. Make you new file's name like the name of the DataSource,
still ending in -jdbc.xml. Eg: MS_Beta-jdbc.xml
3 - Edit this file to change as much as would be clear for the
driver you want. Eg: change the driver class to the class you want,
the user name, URL, test table etc. Also, change the pool's initial
capacity to 0. This is so the pool can be created without making a
connection. We need that because the password is encrypted, and
there is no manual way for you to add the correct one yet.
4 - go one directory up, and edit the config.xml. Find a
jdbc-system-resource entry corresponding to the original
resource file you copied. Make a new entry in the config file,
like the original, but change the Datasource name to your new one.
5 - If this all went well, reboot your server and go to your data
source in the console, and edit it. Alter the password to what it
really should be, and you can also change whatever else you might
want.
6 - shut down again, and reboot, and you should then be able to go to
your data source in the console and test a connection.
That's it. Here is an example of a jdbc.xml file I made, and
the entry I made in the config.xml:
config/jdbc/newpool-jdbc.xml:
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/domain.xsd">
<name>newpool</name>
<jdbc-driver-params>
<url>jdbc:sqlserver://frogger:1433</url>
<driver-name>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>joe</value>
</property>
</properties>
<password-encrypted>{3DES}cPpx2Z6faqY=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>5</max-capacity>
<capacity-increment>1</capacity-increment>
<shrink-frequency-seconds>900</shrink-frequency-seconds>
<test-connections-on-reserve>true</test-connections-on-reserve>
<test-table-name>SQL select 1</test-table-name>
<profile-type>0</profile-type>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>newpool</jndi-name>
<global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
<jdbc-xa-params></jdbc-xa-params>
</jdbc-data-source>
config.xml entry:
<jdbc-system-resource>
<name>newpool</name>
<target>examplesServer</target>
<descriptor-file-name>jdbc/newpool-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>

Homogeneous system copy for SQL server 2005

Hi All,
I am currently investigating for the method to perform system copy for a PI system with SQL server 2005 database. Using the System Copy for SAP Systems Based on NW 7.0 SR2 ABAP+Java as guide, I can see reference to Note 151603. However, I am unable to get a copy of that note. Searching for the note from the official SAP Notes Search area indicated that it is currenytly only avaiable internally.
Would anyone know where I will be able to get a copy of that note?
Thanks,
Wi

> I am currently investigating for the method to perform system copy for a PI system with SQL server 2005 database. Using the System Copy for SAP Systems Based on NW 7.0 SR2 ABAP+Java as guide, I can see reference to Note 151603. However, I am unable to get a copy of that note. Searching for the note from the official SAP Notes Search area indicated that it is currenytly only avaiable internally.
PI is version 7.1 (not 7.0) - so you need to use a different system copy guide.
Markus

ODBC Drivers for SQL Server 2005 on AIX for OWB connect

Hi All -
I have a problem whereby I am trying to connect OWB with SQL Server 2005. The problem statement follows: -
Infrastructure: -
OWB Server installed on AIX
Oracle Installed on AIX
SQL Server 2005 source on Windows
OWB Client on windows XP
My problem is: -
I am trying to connect OWB with SQL Server 2005 for which I have to create heterogenous source entry in Oracle home. But AIX box does not have any ODBC drivers installed and hence I can not configure a DSN on the same. Can any one suggest where can I get these drivers and their installation steps.
Thanks in advance!
Arun
Edited by: Uni.... on Jun 2, 2009 10:50 PM

I was not able to find DG4ODBC anywhere.
Somehow I managed to get a copy of Data Drivers from Data Direct and configured ODBC.INI file as below: -
ODBC Data Sources
DB2 Wire Protocol=DataDirect 6.0 DB2 Wire Protocol
Informix Wire Protocol=DataDirect 6.0 Informix Wire Protocol
Oracle Wire Protocol=DataDirect 6.0 Oracle Wire Protocol
Sybase Wire Protocol=DataDirect 6.0 Sybase Wire Protocol
Teradata=DataDirect 6.0 Teradata
SQLServer Wire Protocol=DataDirect 6.0 SQL Server Wire Protocol
MySQL Wire Protocol=DataDirect 6.0 MySQL Wire Protocol
PostgreSQL Wire Protocol=DataDirect 6.0 PostgreSQL Wire Protocol
Greenplum Wire Protocol=DataDirect 6.0 Greenplum Wire Protocol
ODBC
IANAAppCodePage=4
InstallDir=/u01/app/ODBC
Trace=0
TraceFile=odbctrace.out
TraceDll=/u01/app/ODBC/lib/odbctrac.so
AMS
Driver=/u01/app/ODBC/lib/ddmsss24.so
Description=DataDirect 6.0 SQL Server Wire Protocol
Address=10.240.20.154,1433
Database=AMS
My TNSName.Ora file is shown below: -
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/10/db/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
DWHDEV =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = aixdevdb2)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = DWHDEV)
AMS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.240.20.154)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = AMS)
(HS = OK)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
Listener.Ora file is as below: -
# listener.ora Network Configuration File: /u01/app/oracle/product/10/db/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10/db)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = AMS)
(ORACLE_HOME = /u01/app/oracle/product/10/db)
(PROGRAM = hsodbc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = aixdevdb2)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
INITHSODBC file for this source is initAMS.ora is configured as: -
HS_FDS_CONNECT_INFO = AMS
HS_FDS_TRACE_LEVEL = 4
HS_FDS_TRACE_FILE_NAME = /u01/app/ODBC/log.log
HS_DB_NAME = MSSQL
HS_FDS_SHAREABLE_NAME = /u01/app/ODBC/lib/odbc.so
# ODBC specific environment variables
#set ODBCINI= /u01/app/ODBC/odbc.ini
I have tested the DSN created in ODBC.INI file using example appplication that comes by default with datadirect drivers and that is connecting to database and fetching data as per query supplied, but when I am trying to create connecting from OWB to SQL Server it is failing with following error: -
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from OWB_188
Even database link is giving same error message.
I have followed all the steps which are necessary to configure Heterogeneous connectiviyt including restarting listener, but no luck.
Any comments

What is the process for SQL Server 2005 patch update

hi,
i have 2 production SQL Server2005 Database servers in cluster ,
what is the process for applying patches.
Saidireddy

In 2005 you can do it in two ways...
Method 1 :
With SQL Server 2005,
when you start installing cluster service pack (or hotfix), it must be launched on the active node(node
that hosts the instance). When installing the Setup will launch simultaneously "remote silence" on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.
Method 2: First you can install in passive node then you can install in the active node, In this way you can save your down time ( If you start in the active node it will check in the passive, and if its installed already then it skips that
and start applying in the active node ), but most of the DBA's follows only first method because they may not aware of this or just they follows Microsoft common method.
SQL 2008 and Later....
1. Apply the hotfix on pasive node N2
2. Reboot the passive node N2
3. Failover on SQL resource : the passive node become the active node
4. Apply the hotfix on the passive node N1
5. Reboot the passive node N1
Raju Rasagounder Sr MSSQL DBA

Arc is not implemented for SQL Server 2005 physical model

Similar Messages

Maybe you are looking for