WLS -JDBC sql server 2005, if sql server down bringing down entire cluster

Hi ,
From 4 WLS we connect to 4 indivudual SQL Servers 2005 (non clustered) , if one sql server goes down it is bringing down the 4 WLS servers. Tried all the possible parameter tuning in WLS nothing helped.
Is there any solution, if there is one sql server down can we mark the bad sql server down and don't create STUCK threads to all 4 WLS.
Thanks
Manu

Hi Weinstein,
when one sql server went down we saw the SQL server SHUTDOWN in progress. We use the DRIVER weblogic.jdbc.sqlserver.SQLServerDriver. When one server is going down connection pool is keep going to the same server and creating stuck threads.
<Info> <JDBC> <[ACTIVE] ExecuteThread: '150' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1327597605889> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]SHUTDOWN is in progress.
 at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
 at weblogic.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.doConnect(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.connect(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.setupImplConnection(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.open(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseDriver.connect(Unknown Source)
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:320)
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:412)
 at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1717)
 at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1606)
 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1507)
 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
 at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1942)
 at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:40)
 at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2368)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
In .net they have Retry Wait and connection will not go to the failed server until certain time, do we have any parameters like this in weblogic connection pool.
http://support.microsoft.com/kb/169470
1. Q. With ODBC 3.0 Service Pack 1, will the ODBC driver manager try to connect to the database server repeatedly when the server is not available?
A. ODBC 3.0 Service Pack 1 introduced a new API, ODBCSetTryWaitValue, to prevent the ODBC driver manager from connecting to an unavailable server repeatedly. ODBCSetTryWaitValue takes a DWORD parameter and saves the information in the registry at the following location:
HKEY_LOCAL_MACHINE\Software\Odbc\Odbcinst.ini \ODBC Connection Pooling\Retry Wait
Once the diver manager detects a bad database server, it returns an error message and marks the connection with the time. From that point until the RetryWait value expires, the driver manager returns a failure without trying to reconnect to the database server
Thanks for your help.
Thanks
Manu

Similar Messages

How to enable high availability on SQL Server 2005 with Windows Server 2008 Enterprise R2

Dear Folks,
I would like to ask you about this thing. I'm working for IT department for bank in Myanmar. Our bank have up to 96 branches across all of Myanmar including H.O. We are using Microsoft SQL Server 2005 with Windows Server 2008 for our banking
information system. My main problem is having to backup and restore the database backup files every time the servers in branches goes down for whatever reasons. I want to deploy this feature of high availability and failover cluster using Windows Server 2008
and SQL Server 2005. Our branches have 2 Servers. One is for Primary and other is for Backup. What I want to do is that, I want to change Backup Server to Primary Server whenever the Primary Server goes down for whatever reasons. All the working data and databases
from Primary will immediately replicated into Backup Server along with all the IP information of Primary Server. Please give me step by step guide for this process.

Try below
http://blogs.msdn.com/b/cindygross/archive/2009/10/23/checklist-for-installing-sql-server-2005-as-a-clustered-instance.aspx
I will recommend you to upgrade SQL server to newer version for support as well as flexibility.
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

Upgrade from SQL Server 2005 to SQL Server Express 2014 Enterprise

I was just wondering if it is possible to upgrade from SQL Server 2005 to SQL Server Express or will I have to build the environment and then migrate the database?
Thanks for any help

Hi Lance_Romance,
As others’ posts, you don’t have to build new environment and then migrate databases between SQL Server instances, you can use the in-place upgrade strategy to upgrade from SQL Server 2005 to SQL Server 2014 .Please note that SQL Server 2005 SP4 is required
in this case.
Before upgrading , I recommend you to use
upgrade advisor, it can help to analyze your existing SQL Server deployment and inform you of issues that need to be addressed. In addition, please perform a full server backup prior to performing the in-place upgrade, which will be an important way
to revert your SQL Server to its previous state if the upgrade does not go as planned. For more details, please review this blog:
Upgrading to SQL Server 2014: A Dozen Things to Check.
Thanks,
Lydia Zhang

Steps to migrate Project Server 2007 from SQL Server 2005 to SQL Server 2008?

We need to migrate Project server 2007 from SQL Server 2005 to SQL Server 2008.
1. Is it as simple as doing backup and restore of databases and pointing Project Server to the new DB server? Or there are some specific steps that should be followed?
2. Article at
http://technet.microsoft.com/en-us/library/dd207290(office.12).aspx is about moving databases from one DB server to another (same versions). At one place, it mentions to
backup all databases but at another place it mentions that
You should only back up the Draft and Published databases from the source database server.
What should be done when moving from 2005 to 2008?
Regards,
Amit
Gupta

High Level step you can get this form Tech net or MSDN too
Shut down the SharePoint servers (App / Web)
backup all of the SharePoint and Project
Server databases from the SQL 2005 server
copy these over to the new SQL 2008 server and restore all of
the databases with the same names
script out all of the logins used by SharePoint/PS from the SQL 2005 server and create these on the SQL 2008 server
script out the Delete expired sessions SQL job from the SQL 2005 server and create this on the SQL 2008 server - or create them manually on the SQL 2008 server
repoint the SQL server DNS Alias from the SQL 2005 server to the SQL 2008 server, if SharePoint and Project Server was installed using the actual SQL server name and no alias, you can create a DNS alias for the old SQL 2005 server name that points to the SQL
2008 server. This is so that the SharePoint servers can still connect to the same SQL server name
Start up the SharePoint servers
kirtesh

Any problems if run SQL Server 2005 and Essbase Server on 1 machine?

Hi, I would like to know if there's any problems in terms ofperformance when running SQL Server 2005 and Essbase Server on 1machine? Currently, my users are using Excel File (Lock & Send) toupload data to the Essbase Server and it took about 30 mins perexcel file upload. Application Manager is installed on client's andserver PC for adminstration. Now, I need to implement Datawarehouse and wish to installSQL Server 2005 on the current machine my Essbase Server isrunning. I will need to do simple SQL statements on the SQL Server2005 such as Update, Select, Insert etc. When comes to performance issues, will my current Essbase Serverbe affected? What if 2 users are accessing the Essbase Server andSQL Server at the same time? Will any data be lost in the midst ofextracting data? I hope someone can advise. Appreciate that. Thank you.

<blockquote>quote: <hr>Originally posted by: roy_choy Currently, my users are using Excel File (Lock & Send) to upload data to the Essbase Server and it took about 30 mins per excel file upload. I hope someone can advise. Appreciate that. Thank you.<hr></blockquote> My test server is running both Essbase and SQLServer, but I think that you have a bigger problem. If a lock and send is taking 30 minutes, you are using the wrong technology to load Essbase. You should really consider doing the load using a data load rule. If that isn't the problem, it may be that you are having a real performance problem. If you are moving enough data to require a half hour load, it should be probably be loaded from a text file, or even a spreadsheet, using a data load rule. Text file loads are a bit better than excel, especially when there are formatting issues. Lock and sends are fine for changing parameters and doing adjustments, but heavy duty data loads really work a lot better with load rules.

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

Error when upgrading from SQL Server 2005 to SQL Server 2014

Hello everyone,
Could you help me, i have an error when i try to upgrade my SQL Server 2005 Enterprise Edition to SQL Server 2014 Enterprise Edition,
All of prerequisits are available and i dont have a problem,
before the end of migration process, i have this error: The group name could not be found (0x84BB0001)
File log:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Best regards,
Guiga Hafedh

There are more detailed logs for the various components. The one of interesting is the one for the engine or possibly the one for full-text.
These logs are extremely verbose, and the errors are rarely crystal clear, but at least give them a try. If you have problems, find a place to upload them (Dropbox, Skrydrive etc), so that we can look.
The closest at hand is that "group" that cannot be found is an AD group.
Erland Sommarskog, SQL Server MVP, [email protected]

Importing Data from MS Access into SQL Serevr 2005 via Linked Server: User-Dependent failure

I am operating an Express version of SQL Server 2005 on a Windows XP machine.
I have successfully setup a linked server to a remote Access (.mdb) database. With my user account (Windows authentication) I can retrieve and store data without any problem.
I have another user (apparently with same settings as my own account) that is always failing to get the data.
The Error message he gets is:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp" returned message "The Microsoft Jet database engine cannot open the file '\\DSITSO-NT0001\Exchange\Database5.mdb'. It is already opened exclusively by another
user, or you need permission to view its data.".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp".
Here below the code used to set up the linked server (coming from the Code Snippets of SQL Server 2005).
EXEC sp_addlinkedserver
@server = N'TSU_Tmp',
@provider = N'Microsoft.Jet.OLEDB.4.0',
@srvproduct = N'OLE DB Provider for Jet',
@datasrc = N'\\DSITSO-NT0001\Exchange\Database5.mdb'
EXEC sp_addlinkedsrvlogin
@rmtsrvname = N'TSU_Tmp',
@useself = N'TRUE',
@locallogin = NULL,
@rmtuser = N'Admin',
@rmtpassword = NULL
We both run the script, actually is a Stored Procedure, (see code below) on the same XP machine where SQL Server is running.
EXEC('INSERT INTO tblFcst
(StartBUCode, StartBUType, StartBUSeq, StartTrz, StartCty,
EndBUCode, EndBUType, EndBUSeq, EndTrz, EndCty,
FcstCreationPeriod, FcstValidForPeriod, Fcst, FcstExternalReference,
IsProcessed, IsSolved)
SELECT TSU.BUCodeSend, TSU.BUTypeSend, TSU.BuaNoSend, Null AS StartTrz, Null AS StartCty,
TSU.BUCodeRcv, TSU.BUTypeRcv, TSU.BuaNoRcv, Null AS EndTrz, Null AS EndCty,
TSU.[Current week], TSU.[Forecast for week], TSU.[Volume trp m3], TSU.[TSU_ID (Don''t touch me)],
0 AS IsProcessed, 0 AS IsSolved
FROM TSU_Tmp...tbl_TSU_trpm3 AS TSU;')
PS: it is run using an 'EXEC(String)' format as at compile time of Store Procedure the Linked Server is not existing and otherwise compile would fail.
We tried it with different files, in different locations. It always wors for me, never for him...
The files were not used by anyone else. The folder(s) where they were stored are open to "Everyone".
So I concluded it should be something linked to the User... :) But I really do not know what, as said apparently we have exactely the same setup in our Login profiles.
Any idea or suggestion is welcome.
Thanks
Luca

Hi Luca Lentati,
According to your description and T-SQL statement, we need to verify if the download and install the Microsoft.Jet.OleDB.4.0 as a provider.
If the 64bit SQL Server is running on the server, The error, the Microsoft.Jet.OleDB.4.0 is not support, I reommend you download and install the Microsoft.ACE.OLEDB.12.0 as a provider.
The error 7303 message indicates that the linked server does not have correct login mapping. You can execute the sp_helplinkedsrvlogin stored procedure to set the login information correctly. Also, verify that you have specified the correct parameters
for the linked server configuration.
In addition, if the issue still exists, I recommend you copy the access file to local Server, and create linked server between them , check if it can run well. If yes, it means that
the account which SQL server uses to run the service does not have read/write access to that file share.
There is an article about configuring a Linked Microsoft Access Server on SQL 2005 Server , you can review the following article.
http://www.aspfree.com/c/a/Microsoft-Access/Configuring-a-Linked-Microsoft-Access-Server-on-SQL-2005-Server/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Moving from SQL server 2005 to SQL server 2008 ... for a MS/SQL newbie.

Hello,
I am in charge of moving an existing SAP NW BI (SPS20) from a MS SQL Server 2005 database on Windows Server 2003 (x864/64 bit) Platform to a MS SQL Server 2008 database/Windows Server 2008 Platform (x64/64 bit).
The SID of the SAP system will remain the same.
The thing is that I have always worrked so far on Oracle/Unix environements, windows/MSSQL is an entire new world for me,
so I am quite worried.
I have read many sap notes/installation guides/forum posts regarding this operation, I will describe here my understanding
of the techinical operations that I will need to perfrom.
Could you correct me if I am wrong, as well as give me your comments ?
1/ I will need to perform an SQL server database copy within a homogeneous system copy.
2/First ,I'll have to install on the target environnement the SQL server 2008 database. I'll have to install the SQL Server Database Software with SQL4SAP (no need to install the database server software manually, right ?). Afterwards, I'll install on the target environnent, SAP Netweaver 7.0 SR3 with a modified Instalaltion Master DVD.
3/ On the source environement, I'll perfrom a database backup of the SQL Server 2005 system and restore the database on the target environement. since I choose to perfrom a restore of the database , there is no need to follow all the steps described in sap note 151603 :determine the file structure of the source database, create the directory structure for the target database, etc ...
4/ Once the restoration is finished, I use SAPINST and finish the homogeneous copy : >additional sofware->system copy>target system->central system --> Based on AS Abap --central installation
Your comments are welcome.
Thank you for your attention
Best Regards.
Raoul

Hi Raoul,
you also need a modified Kernel DVD for the installation on SQL 2008 (see SAP Note 1152240).
And don't forget to install and patch the Visual Studio c++ Runtime (also described in that note).
I also would recommend to restore the backup and then install SAP NW 7.0 SR3 and use the restored SQL 2008 database.
So the basic steps are:
1. Perform backup and restore to SQL 2008
1.1 Install SQL 2008 with SQL4SAP
1.2 Backup old database
1.3. Restore backup on SQL 2008
2. Install VC runtime on Win 2008
3. Create modified Kernel DVD
4. Create modified Master DVD
5. Perform system copy target installaton with - additional sofware->system copy>target system--->central system --> Based on AS Abap --central installation and use the SQL 2008 database
You could also use SQL Server 2008 R2 which was release last month.
Please also check Note 1476928
Best,
Sebastian Dusch

SQL Server 2005 64BIT Linked Server Cannot fetch a row using a bookmark

We get the following error SOMETIMES when trying to delete a row from an Oracle 10g database table via the SQL 2005 64BIT linked server.
DELETE [edwdev]..SYSTEM.SAIC_ARTIFACT_LOG FROM tblArtifactLog src WHERE src.source_seq_no = SAIC_ARTIFACT_LOG.art_seq_no and src.source_name = 'edwdev' [SQLSTATE 01000] (Message 0) Cannot fetch a row using a bookmark from OLE DB provider "OraOLEDB.Oracle" for linked server "edwdev". [SQLSTATE 42000] (Error 7333). The step failed.
They keyword here is SOMETIMES. The job would fail 100% of the time before applying ODAC 10.2.0.3.0, after the ODAC install the job fails about 40% of the time. We have this setup in a test enviornment and yes there are rows of data in the table everytime the job runs.
As far as the OraOLEDB10.dll install we have a date of 2/20/07 but a version of 10.2.0.2. I am wondering if this shouldn't be a new version.

LearnMoreAgile wrote:
so does that mean no one at oracle can guide me in this issue before i goto microsoft ?How has the Linked Server been created in MSSQL? OraOLEDb.Oracle is the class name for the Oracle OLEDB provider which should appear in your list of OLEDB providers in your favourite windows dev tool or when creating the linked server. If it doesn't appear likely you didn't choose to install it. I don't know if it's a default install with the 64bit client, but the ODAC client contains the .net provider and not the OLEDB provider.
Niall

Upgrade From SQL Server 2005 to SQL Server 2008 or 2012

Hello this is a silly question but I was able to copy our old database to another hard drive and do an ATTACH to sql 2012 and it worked great now am I crazy or is this too good to be true

Hello this is a silly question but I was able to copy our old database to another hard drive and do an ATTACH to sql 2012 and it worked great now am I crazy or is this too good to be true
To be specific to your question.You can very well attach SQL 2005 database to SQL server 2008 and SQL server 2012.But how your application will respond to New database will be difficult to tell.
I strongly recommend you to see below link
Features depricated in SQL server 2012
http://technet.microsoft.com/en-us/library/cc707782.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Replication Configuration issue after migrating from SQL Server 2005 to SQL Server 2008 R2

Hi All,
This weekend we have migrated one of our Core system from SQL Server 2005 SP3 to SQL Server 2008 R2 SP2. Migration went successful. However when we are trying to Configure transaction replication we are getting below Error:
Msg 21854, Level 16, State 1, Procedure sp_MSrepl_addarticle, Line 573
Could not add new article to publication 'abc' because of active schema change activities or a snapshot is being generated.
Background:
Database compability Changed from 90 to 100.
A quick Help would be appreciated.
Best Regards - Viral
Thanks - Viral

Is a snapshot being generated? the message seems to indicate one is.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Problem when connecting sql server 2005 using SQL developer

Hi,
I installed Sql developer and I am trying to connect sql server 2005 using windows authentication. I had previously the SSO folder problem saying the path is missing in java.library.path. I copied the SSO folder into Sqldeveloper directory. I changed the settings under computer management->services and applications->sql server configuration manager->sql server 2005 network configuration ->protocols for sqlexpress->I enabled TCP/IP.
Now I am getting an error saying "Failure-can not open user default database.Login Failed. Login failed for user ...".
I am able to connect thru ODBC driver using windows authentication.
Any help on this is highly appreciated.
Thanks in advance,
Lakshmi

Hi Martin,
Your solution has solved my problem too. Thanks for posting these workaround fixes :-)
However, there seem to be a problem with datetime fields. The query:
select getdate()
returns something like: oracle.datetimestamp.@1aed4
Is there a way to get around with this? Otherwise, using SQL Developer as a client for SQL Server doesn't serve the right purpose when we cannot access simple date fields :-)

DataBase Migration from SQL server 2005 to SQL server 2012

What are the challenges and steps to be taken care for proper migration of the Database.
Applications are using the Visual Studio 2012.
saikalyan

Few things that I can think of -
Verify all logins and users are migrated correctly.
Some of the SQL Server 2005 features/code could be deprecated in SQL Server 2012. Changes could be required before or after migration.
Some of the queries could have different performance (better or worse) on 2012 due to changes in query optimizer.
The applications/SSIS/DTS config files are updated to use the new server/instance name.
DNS alias names from the old servers (if used) are moved to the new server to have minimal impact on connection strings.
Plan for downtime of applications and batch processes.
Notify developers about the migration and the new server name(s)
- Aalam | (Blog)

Upgrade data base from sql server 2005 to sql server2008

Hi guys,
What is the best way for upgrade my SQL Server 2005 data base to SQL 2008?

It depends on how you want migrate, in-place or side-by-side?
In-place: Run a backup of all databases and then install the new SQL Server version
Side-by-side: Install the new SQL Server, backup all database of old SQL Server and restore them on the new one. Then copy all logins from old to new server.
Olaf Helper
[ Blog] [ Xing] [ MVP]

WLS -JDBC sql server 2005, if sql server down bringing down entire cluster

Similar Messages

Maybe you are looking for