SQL SERVER 2005 - part of the tables where migrated

Hello.
I'm trying to convert a SQL SERVER2005 DB to ORACLE 10g.
The sql-developer is converting all the objects from the DB, but builds DDL comands for 43 table insted of 320 tables .
All the tables are on schema dbo.
The user connecting to the sql server 2005 is data base owner (dbo).
After building the repository, on MD_TABLES there are only 43 records.
Any idea where to search the problem?
Thanks
Reuven
Message was edited by: reuven
user533419
Message was edited by: reuven
user533419
Message was edited by: reuven
user533419

Reuven,
We are finalizing our production release and would like to get to the bottom of the problem.
-You can run the workbench/SQLDeveloper so that you can see Java 'Stack traces' from exceptions (errors) in the output:
[from the SQLDeveloper forum under Unable to start sql developer :]
There is another [sqldeveloper.exe] that you should try from the command line:
<sqldevroot>\sqldeveloper\sqldeveloper\bin\sqldeveloper.exe
This will run in debug mode.
If all else fails, try the .bat file in that same folder.
-Are you using a case sensitive database?
-For the pre-production release workbench currently uses SQL Server 2000 views rather than SQL Server 2005 altered to take allowance for the user/schema separation, this may cause unforeseen problems.
-Can you send a test database to us with this problem?
Regards,
Turloch
Oracle Migration Workbench Team

Similar Messages

Copy table from Ms SQL Server 2005 to Oracle with SSIS package

Hi all
I am witting an SSIS package to copy 2 tables from Ms SQL Server 2005 to an Oracle 10g database.
Problem: I can only see the Microsoft OLDB Provider for Oracle and it is too slow. How can I use the Oracle ODBC in aMs SQL Server 2005 or building a .net SSIS package.
thanks

Yes I am able to see the driver on the Data Source (ODBC), I also created a connection to the Oracle database. The problem in Ms SQL Server 2005 is that the ODBC connection I created is not listed. None of the lo local connections are listed, only Microsoft OLEDB connections

I plan to upgrade the SSRS 2005 SP2 enterprise edition in our internal web server to 2005 SP4, the Reporting server database is hosted in another sql server in sql server 2005 SP4. Do I need to do anything on the reporting server database side?

My question is what the steps do I need to take to upgrade SSRS from 2005 SP2 to SP4. The web server that host the SSRS is in 2005 SP2, and the OS is in window 2003.
Our SSRS report server and report server database are in different servers. The SSRS in the web server is in 2005 SP2 enterprise edition, the report server database is in sql server 2005 SP4 enterprise edition.
To upgrade the SSRS in web server from 2005 sp2 to sp4, do I need to backup/restore the encryption key? Nothing will be changed in the report server database. We will still pointing to the same database in the current server, all
I wanted to do is performing a inplace upgrade of SSRS from 2005 SP2 to SP4.
Any response will be greate appreciated. Thank you!
Li-hui Chen

Hi Lihui Chen,
According to your description, you want to install the Services Pack 4 for SQL Server. Right?
In SQL Server, Services Packs are used for fixing issues of current version product. It's not an Upgrade, you don't have to backup/restore your encryption key. You just need to download the Service Pack 4 on:
Microsoft SQL Server 2005 Service Pack 4 RTM . Please make sure you have administrative rights on the computer to install SQL Server 2005 SP4. For more information, see links below:
How to obtain the latest service pack for SQL Server 2005
List of the issues that are fixed in SQL Server 2005 Service Pack 4
SQL Server 2005 SP4, KBA 2463332, Installation Issues
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Sender JDBC support the stored procedure in SQL Server 2005

Dear All,
My question here is , Sender is JDBC adpter support to call the Stored procedure in Microsoft SQL Server 2005?
I followed the below thread before posting this question
Sender JDBC Adapter Supports Stored Procedures????
In the thread Suraj response has mentioned SAP note: 941317, I checked the note, Note says it supported only ORACLE DBMS versions.
Could you please clarify about this to possibility to call the stored procedure in Microsoft SQL server 2005?
Thank you in Advance
Sateesh

Hi Sateesh,
To answer your query, Yes it does. SP call works with SQL Server 2005 as well, the SP call should be "execute SPNAME <paramas>". In the place of update statement put any junk value as mentioned in the earlier comment.
But just one thing to be noted, the select or any other query returning the desired resultset must be the first statement in youre SP returning value to the calling app. Means if there are any update, deletion or intermediate select queries to be used with in your SP, those all should be placed after the Main Select query that returns the desired resultset. Variable declarions and assignments are allowed.
But if the seq of statements in your SP are like:
@var1 Varchar
Update <tablename>....
Select * from <tablename>
Then the output of the SP is :
1 row updated
<the resultset from select>
In such cases, PI can recognise the first value returned only, that is "1 row updated" and hence the returned resultset wouldn't be seen by PI or not be passed to integration engine. Hence the update should come after the main Select.
One more interesting piece of information, even if you copy and paste the entire SP code in place of the query string of Sender JDBC adapter, that too will work with all your variable declarations, multiple queries and updates and everything. Just have to follow the above rule.
Let us know what you find.
Regards,
Suddhasatta

TOPLINK-41 with SQL Server 2005

I have mapped several entities to a SQL Server 2005 database. I am using the Identity column as a sequence generator for the primary key in each table.
This is how I do it:
@Id
@GeneratedValue(strategy=GenerationType.IDENTITY)
@Column(name="server_asset_id", unique=true, nullable=false, precision=18, scale=0)
public Long getServerAssetId() {
return this.serverAssetId;
}However, I am getting the below error:
Exception [TOPLINK-41] (Oracle TopLink Essentials - 2.0.1 (Build b09d-fcs (12/06/2007))): oracle.toplink.essentials.exceptions.DescriptorException
Exception Description: A non-read-only mapping must be defined for the sequence number field.
Descriptor: RelationalDescriptor(jtdi.cm.ejb.bean.entity.ServerAsset --> [DatabaseTable(jtdi_cm_db.dbo.server_asset)])When I go look at the table properties in SQL Server 2005, I see the identity is setup properly.
Am I doing this wrong? Any suggestions would be greatly appreciated. Thank you for taking the time to read my post.
Russ

This error went away once I corrects a target entity declaration.

SQL Server 2005 SP2 install on Vista

Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Professional (Build 6000)
Time            : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine         : USER-PC
Product         : Workstation Components, Books Online and Development Tools
Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time            : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
Lucy

This is the previous errorlog:
2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server      All rights reserved.
2008-04-09 11:47:06.27 Server      Server process ID is 240.
2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server      Registry startup parameters:
2008-04-09 11:47:06.27 Server      -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server      -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server      -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

OraOledb, Linked Servers and SQL Server 2005 issues

Some issues I've come across when using SQL Server 2005 (and SQL Server Express 2005), the OraOLEDB provider (10.2.0.1) and a linked Oracle database (8.1.7.4.0 64-bit)
1) You must set the OraOledb.Oracle\AllowInProcess value to 1 to allow the OraOledb provider to run in SQL Server's process. Without doing this I receive an 'unspecified error' from the OLE DB provider when attempting to run a query
2) When running a ' select * ' query across a linked server using the provider, I receive the following error: Msg 9803, Level 16, State 1, Line 1
Invalid data for type "numeric". I can, however, select all of the columns by name and the query completes (no error). Sometimes the 'select *' query returns a few rows before the error, sometimes it doesn't. The Microsoft Provider for Oracle does not have this problem

Okay... I've got a Win2K3 Std Ed server (x64) running 64-bit SQL Server 2005 Enterprise Edition. I've installed the Oracle 10g 10.2.1 full client and admin tools, added two named services via the NetConfig assistant, and successfully set up (and tested) a connection via the ODBC Administrator to an Oracle database.
Now... when I try to create a new connection manager in SQL Server 2005 Integration Services, the OLEDB provider for Oracle can't be found, and when I try to manually add an underlying OLEDB connection to the database, SQL Server reports:
Test connection failed because of an error in initializing provider. The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.
Does anyone know what I need to do to see my ODBC Server data connections in SQL Server 2005 (64 bit)? I don't have this issue on my 32-bit SQL Server 2005 servers.

JDBC - MS SQL Server 2005 with multible instances

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

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

Howto take SQL Server 2005 Cluster AND Cluster Group Offline

I need to update firmware on the backend storage used by our Active/Passive SQL Server 2005 Cluster. The first step in the process states that all I/O to the disks should be stopped. Per that, I need to take the the SQL Server cluster offline AND the cluster group; however, I then need to use one of the servers that participates in the cluster to perform the upgrade on the storage array. Using the process (which doesn't account for having to use one of clustered servers to perform updates) outlined at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1550288&SiteID=1 as a basis, below is my best guess regarding what I will need to do:
Shutdown:
1. Backup all of your databases prior to the outage and ensure they are in a safe place (NOT on the disk drives in the cluster)
2. Take the SQL Server group OFFLINE. This will cleanly shutdown the SQL Server and it will remain offline when you power the machine back on.
3. Once SQL Server is offline, power off the node which does NOT have the cluster resource currently running on it
4. Save the node which is running the cluster group for last - make a note of this machine as it will be the first one you power back on. MY ADDITION: Before powering it down, set the cluster service to manual so that when you restart the server to perform the storage array maintenance, the cluster will not be running - and likewise not generating I/O against the disk array.
MY ADDITION: 5. Restart the server from step 4. Takes the cluster offline "cleanly" and brings the server back on line so that the storage array maintenance can be performed.
6. Update the firmware on the storage array. After that is complete, set the cluster service back to "Automatic".
Start up:
1. Restart the server. Per the previous steps, the server to be restarted will be the server that last hosted the cluster group and the one used to update the firmware on the storage array.
2. RDP into the node, open cluster administrator, and verify that the cluster came back online successfully and everything looks clean
3. Power on the second node.
4. Failover the cluster group across each node in the cluster and validate that everything looks OK
5. Bring your SQL Server groups back online
6. Validate that everything is operational
Is there a better way to do this or official documentation for the process?
Thanks.

FYI: I did use the process outlined above to briing the cluster offline, perform updates, and bring it back online. It worked as I had hoped. As a test, I had also done the same on a test [non-SQL] cluster prior to making the updates to our SQL cluster. Is it the best way to do it? Who knows. Did it work? Yes.

Replication Error in Goldengate SQL Server 2005 to Oracle.

Dear All
SQL Server 2005 is my source database and oracle is my destination database when i run my param file at source side following error occur.Kindly suggest the solution.
ERROR OGG-00146 VAM function VAMInitialize returned unexpected result:
error 600 - VAM Client Report <MSSqlVam: (1) At least one option of type MANAGESECONDARYTRUNCATIONPOINT
needs to be specified for TRANLOGOPTIONS (DSOPTIONS)>.

The GoldenGate forum is over here:
GoldenGate
(question is somewhat old, but unanswered)
SQL Server setup - you have to choose one of two options for the truncation point and the transaction log:
If the Extract process is running against a SQL Server 2005 source, use the TRANLOGOPTIONS
parameter to control whether Extract or SQL Server maintains the secondary truncation
point. This is a required parameter and must contain one of the following options:
SQL Server replication maintains the truncation point
Use TRANLOGOPTIONS with the NOMANAGESECONDARYTRUNCATIONPOINT option if Extract and
SQL Server 2005 replication or a third-party replication program will be running at the
same time for the same database.
Oracle GoldenGate maintains the truncation point
Use TRANLOGOPTIONS with the MANAGESECONDARYTRUNCATIONPOINT option if Extract and SQL
Server 2005 replication or a third-party replication program will not be running at the
same time for the same database.
See page 29 in the SQL Server setup and installation guide

Migrate a SQL Server 2005 clustered instance

Hi all,
I've a 2 node cluster running Windows Server 2003, on the top of the cluster run two clustered instance of SQL Server 2005 Enterprise. The Windows Server 2003 are physical machine and the shared storage is implemented into a FC SAN.
I want to migrate the 2 clustered instance on a new Windows Server 2008R2 servers that runs on new hardware (so no in-place migration).
Is there a certified path for migration?

Hi,
thank you for the answer, I've just seen that web resource. I'm trying to find something specific for SQL Server, if it exists.
Can you please explain your requirement. Did you read complete article ? As far as i can read you dont want inplace migration in that case get a new windows boxes and configure windows server cluster its fair simple and easy. Do you want document how to configure
windows cluster ?
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Microsoft SQL Server 2005 JDBC Driver

Hi
how can i use Microsoft SQL Server 2005 JDBC Driver to coonect to db???

com.microsoft.jdbc.sqlserver.SQLServerDriver is a SQL Server 2000 class.
Also the port setting in the connection url jdbc:sqlserver://localhost:<port> is not 1433 as in SQL Server 2000.
In the connection URL, <port> is obtained from the SQL Server configuration Manager. When the SQL Server 2005 is restarted the port number changes.
To obtain the <port> in the SQL Server Configuration Manager select the node SQL Server 2005 Network Configuration>Protocols. Right-click on TCP/IP node and select Properties. Select the IP Addresses tab. In IP ALL the TCP Dynamic Ports specifies the <port> value.

Storing the file in to the sql server 2005 table

hi,every body...
in my appliaction i need to store the files.
i have searched the net but only i found as BLOB(Binary L:arge OBject) is the solution,
how to use this blob...technique..
can any one send some sample of code to explain.......
how to insert a file and how to retrive the inserted file from the SQL SERVER 2005...
thanks in advance..

yes, ur rite thse two methods are available..
but i didnt understand that..the method setBinaryStream() accepts 3 parameters
the last parameter which i know that.. size of the file of int type rite?
can u give some more information regarding this..
thanks ..

SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64

I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
ThreadID     Message
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: findDFA_LLR: (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
sqlrule.llr
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: database subsystem only
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: loading libary succeeded
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Init()
(Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
(Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:118): trace message: Setting static property map
(Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: initializing subsystem succeeded
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: done loading subsystem - database subsystem only
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Connect()
(Thu Apr 23 20:57:46 2009)     3024     3028     (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
(Thu Apr 23 20:57:46 2009)     3024     3028     (.SQLServerDatabase.cpp:119): trace message: SQLServer error found: ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
(Thu Apr 23 20:57:46 2009)     3024     3028     (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason: (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
(Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Shutdown()
(Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:182): trace message: Releasing
static property map
How do I get past this?

The workaround was, I installed the SQL Server Client tools and created a System DataSource and then had to create a user DataSource (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and will not allow it.
Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
Thanks.

SQL Server 2005: Multi-part identifier could not be bound

Hello,
I use IBM WebSphere Portal and am desperately trying to move data from the default Cloudspace Database to MS SQL Server 2005, of course following the official guidelines.
What happens is that WebSphere's Configuration Wizard fails because of an error caused by the SQL Script. Trouble is, I can't bring it to work not even in the SQL Server Management Studio.
What follows is the code generated by the script. The error is caused by the last "check"-constraint (colored in red).
CREATE TABLE community.APP_DESC (
OID BINARY(18) NOT NULL,
TYPE INTEGER NOT NULL,
APP_NAME NVARCHAR(255) NOT NULL,
IS_ACTIVE INTEGER NOT NULL,
JSR_VERSION NVARCHAR(255),
GUID NVARCHAR(255),
WEB_MOD_OID BINARY(18),
WEB_MOD_SL BINARY(18),
WSRP_PROD_OID BINARY(18),
WSRP_PROD_SL BINARY(18),
DEFAULT_LOCALE NVARCHAR(64),
CREATED BIGINT NOT NULL,
MODIFIED BIGINT NOT NULL,
WSC_GROUP_ID NVARCHAR(255),
CONSTRAINT PK20 PRIMARY KEY NONCLUSTERED (OID),
CONSTRAINT FK20A FOREIGN KEY (WEB_MOD_OID) REFERENCES community.WEB_MOD (OID) ON DELETE CASCADE,
constraint FK20B FOREIGN KEY (WSRP_PROD_OID) REFERENCES community.WSRP_PROD (OID) ON DELETE CASCADE,
CONSTRAINT CC20A CHECK (((community.APP_DESC.WEB_MOD_OID IS NULL) AND (community.APP_DESC.WEB_MOD_SL IS NOT NULL)) OR ((community.APP_DESC.WEB_MOD_OID IS NOT NULL) AND (community.APP_DESC.WEB_MOD_SL IS NULL)))
And that's what SQL Server 2005 told me:
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_OID" could not be bound.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_SL" could not be bound.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_OID" could not be bound.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_SL" could not be bound.
BTW, as this is a generated script I do not have the possibility to change it. Because it has been released by IBM I am rather convinced that it is correct - therefore I was wondering whether SQL Server 2005 has a known bug that makes it refuse "check"-constraints.
Any hint is very appreciated.
Thanks in advance,
adapter

THe problem is that is was probably not made for SQL Server 2005. It should read:
CONSTRAINT PK20 PRIMARY KEY NONCLUSTERED (OID),
CONSTRAINT FK20A FOREIGN KEY (WEB_MOD_OID) REFERENCES community.WEB_MOD (OID) ON DELETE CASCADE,
constraint FK20B FOREIGN KEY (WSRP_PROD_OID) REFERENCES community.WSRP_PROD (OID) ON DELETE CASCADE,
CONSTRAINT CC20A CHECK (((APP_DESC.WEB_MOD_OID IS NULL) AND (APP_DESC.WEB_MOD_SL IS NOT NULL)) OR ((APP_DESC.WEB_MOD_OID IS NOT NULL) AND (APP_DESC.WEB_MOD_SL IS NULL)))
The meaning of the first identifier changed in SQL Server 2005, as this is now the Schema and not the owner. DO you have a chance of using a SQL Server 2000 computer ? In terms of licences you will have a downgrade licence for the SQL Server, otherwise you should ping the IBM guys to provide a compatible script.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de

SQL SERVER 2005 - part of the tables where migrated

Similar Messages

Maybe you are looking for