I have 2 SQL 2005 database servers working together as a mirrored configuration.
Accessing this database I have an Apache Tomcat 5.5 server using SQL JDBC 1.1 driver. When the database is running in a non-failover state everything works fine and my Tomcat application (uPortal) runs as expected. However, when the database is failed over, my Tomcat application hangs indefinitely; even after restarting Tomcat following the failover.
This is how my connection string looks in the server.xml of Tomcat:
Hi.. We have a java application which connect to our MS-SQL DB during midnight using JDBC connector and extract information. But very often ,the java applicatian halted and because of the deadlock as shown below.
Caused by: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Transaction (Process ID 54) was deadlocked o n lock resources with another process and has been chosen as the deadlock victim.
now the java programmer is blaming me that the MS SQL DB is having deadlock and cause their Java application to hang.
Is there any way to clear the deadlock before the the Java applcation run or how to prove the Java application script itself is having problem and causing the deadlock ?
We currently have a system that uses sql server 2005 mirroring. In testing the application, we fail over the database in the middle of a 2.0 .NET web application. The failover partner is specified in the connection string. The next request to the web server results in an error page popping up with the message "A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)" This message only occurs for the first request to the web server, all subsequent requests sucessfully access the new failed over database. Thanks for any suggestions.
1. Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk. 2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode. 3. after fail over done to 2nd secondary node what mode in production(readonly or read write). 4. how to rollback to production primary ,will change data in secondary will get updated in primary.
We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.
However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.
The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.
Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.
The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.
Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.
Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.
We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?
1. In alwaysON fail over cluster, Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.
2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.
3. After fail over done to 2nd secondary node what mode in production(readonly or read write).
4. How to rollback to production primary ,will change data in secondary will get updated in primary.
I have read similar posts to this, but I am still having problems.
I am trying to use connection pooling to connect to a local SQL Server 2005 database. I am running my application using MyEclipse Enterprise Workbench. I have verified that sqljdbc.jar resides in "WebRoot/WEB-INF/lib/"
I've got an import app written in Java. One table I'm importing from contains 22 million records. When I run the app in a 2000 environment, I have my max heap set at 512, and the table gets imported. When I run in a 2005 environment, I have to change the max heap to 1152 or it will error out with a similiar error:
com.microsoft.sqlserver.jdbc.SQLServerException: The system is out of memory. Use server side cursors for large result sets:Java heap space. Result set size:854,269,999. JVM total memory size:1,065,484,288. (<--this is with max heap at 1024)
what is the difference between the 2000 and 2005 JDBC that I have to set max heap in one and not the other?
I am running the following TSQL command and it hangs. These commands are running from SQL 2000 server and it is querying information for SQL20005 database.
Running simple EXEC command work fine but running using Insert hangs.
Hi Everyone, I'm having a bit of a dispute with one of my clients' software developers. This client has a server, installed by us (Windows 2003 Std. SP1/ SQL 2000 SP3a) (Dual Xeon 2.8, 4GB RAM) They are having performance issues with the software developers application, which is based on SQL. I'm having trouble believing the issues are caused by the server, but the software dev's blaming us for the problems.
Yesterday i got a mail from them that a specific SQL query "hangs" upon execution and this is likely caused by a bad install of the server or SQL (yeah right). This query is: select * from table, wich hangs the server upon running. Theyt say a select row(item) from table does work (duh). Now i know a bit of SQL and i'm thinking this select all from that table query locking up the server is most likely caused by a table that has grown so big that it just locks up.
Am i right thinking this has nothing to do with the hardware/software (sbs/sql), but is merely caused by bad programming and/or lack of SQL knowledge at the dev's side? Especially since last year the DB grew to about 40 GB and i had to tell them to think about putting it in simple mode to make it smaller. Something they'd never heared about...
Any ideas would be very welcome. I don't want to go throw mud around with us blaming them and them blaming us and the client being the one with the problems. I just want to make a well thought out statement to the software dev. and then try to find the right solution.
I had 5 servers hang all on the same day, all within about 5 mins of each other scattered across 4 corners of the UK. Our support team tell me that it has something to do with SQL Server, but cannot say what. I can see looking at the error log of one of the servers, that there are about4 entries everyday since startup, and this continues right up until the night before the freeze.
At 22:00 the night before the freeze, a load of entries are written (Iv'e cut down the list to make it easier to read). then at around 4am the servers all froze. Could someone take a sneaky peak at these logs and tell me in your own opinion what caused this to happen.
The first section, is what I believe to be normal
2006-11-28 20:52:53.68 server Copyright (C) 1988-2002 Microsoft Corporation. 2006-11-28 20:52:53.68 server All rights reserved. 2006-11-28 20:52:53.68 server Server Process ID is 952. 2006-11-28 20:52:53.68 server Logging SQL Server messages in file 'D:Program FilesMicrosoft SQL ServerMSSQLlogERRORLOG'. 2006-11-28 20:52:53.73 server SQL Server is starting at priority class 'normal'(1 CPU detected). 2006-11-28 20:52:54.75 server Working Set size set to 409600 kilobytes. 2006-11-28 20:52:54.90 server SQL Server configured for thread mode processing. 2006-11-28 20:52:54.90 server Processor affinity turned ON, processor mask 0x1 2006-11-28 20:52:54.92 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks. 2006-11-28 20:52:55.20 server Attempting to initialize Distributed Transaction Coordinator. 2006-11-28 20:52:57.20 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b 2006-11-28 20:52:57.53 spid3 Starting up database 'master'. 2006-11-28 20:52:59.31 spid3 Server name is 'SN047483'. 2006-11-28 20:52:59.31 server Using 'SSNETLIB.DLL' version '8.0.760'. 2006-11-28 20:52:59.31 spid5 Starting up database 'model'. 2006-11-28 20:52:59.50 spid8 Starting up database 'msdb'. 2006-11-28 20:52:59.50 spid9 Starting up database 'pubs'. 2006-11-28 20:52:59.53 spid10 Starting up database 'udb'. 2006-11-28 20:52:59.64 spid11 Starting up database 'vgold'. 2006-11-28 20:53:00.07 server SQL server listening on 155.202.58.53: 1433. 2006-11-28 20:53:00.07 server SQL server listening on 127.0.0.1: 1433. 2006-11-28 20:53:00.29 spid5 Clearing tempdb database. 2006-11-28 20:53:00.64 server SQL server listening on TCP, Shared Memory, Named Pipes. 2006-11-28 20:53:00.64 server SQL Server is ready for client connections 2006-11-28 20:53:00.71 spid9 Starting up database 'dbs'. 2006-11-28 20:53:01.01 spid8 Recovery is checkpointing database 'msdb' (4) 2006-11-28 20:53:01.50 spid5 Starting up database 'tempdb'. 2006-11-28 20:53:53.78 spid3 Recovery complete. 2006-11-28 20:53:53.78 spid3 SQL global counter collection task is created. 2006-11-28 20:53:54.32 spid59 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'. 2006-11-29 00:00:01.10 spid69 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'xp_instance_regread'. 2006-11-29 02:00:01.54 spid69 Using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure 'xp_cmdshell'. 2006-11-29 02:00:09.31 backup Database backed up: Database: master, creation date(time): 2006/11/28(20:52:57), pages dumped: 1907, first LSN: 159:245:1, last LSN: 159:247:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-29 02:00:11.46 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1667, first LSN: 397:332:1, last LSN: 397:335:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-29 02:01:58.10 backup Database backed up: Database: dbs, creation date(time): 2004/10/05(08:00:04), pages dumped: 94467, first LSN: 114:53199:1, last LSN: 114:53203:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-29 02:01:58.20 backup Database log truncated: Database: dbs. 2006-11-29 10:51:33.43 spid62 Using 'odsole70.dll' version '2000.80.760' to execute extended stored procedure 'sp_OACreate'. 2006-11-30 02:00:04.34 backup Database backed up: Database: master, creation date(time): 2006/11/28(20:52:57), pages dumped: 1907, first LSN: 159:260:1, last LSN: 159:262:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-30 02:00:06.57 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1667, first LSN: 398:26:1, last LSN: 398:29:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-30 02:01:53.84 backup Database backed up: Database: dbs, creation date(time): 2004/10/05(08:00:04), pages dumped: 94467, first LSN: 114:54895:1, last LSN: 114:54899:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-11-30 02:01:53.93 backup Database log truncated: Database: dbs. 2006-11-30 13:10:09.96 spid67 Error: 60002, Severity: 15, State: 1 2006-11-30 13:10:09.96 spid67 PBX login_id 5592 already exists in user id 379. Proc Name: um_user_insert. 2006-12-01 02:00:04.51 backup Database backed up: Database: master, creation date(time): 2006/11/28(20:52:57), pages dumped: 1907, first LSN: 159:275:1, last LSN: 159:277:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-12-01 02:00:06.76 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1667, first LSN: 398:408:1, last LSN: 398:411:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-12-01 02:01:52.31 backup Database backed up: Database: dbs, creation date(time): 2004/10/05(08:00:04), pages dumped: 94515, first LSN: 114:55915:1, last LSN: 114:55923:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'QMBACKDEVICE'}). 2006-12-01 02:01:52.39 backup Database log truncated: Database: dbs.
This second section then has around a good few hundred entries.
2006-12-01 22:00:01.98 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:00:01.98 spid67 Folder 7 is not assigned to user 11 Proc Name: ags_workflow_sess_count. 2006-12-01 22:00:02.04 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:00:02.04 spid67 Folder 7 is not assigned to user 11 Proc Name: ags_workflow_sess_count. 2006-12-01 22:18:02.57 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 22:18:02.57 spid66 Folder 7 is not assigned to user 63 Proc Name: ags_workflow_sess_count. 2006-12-01 22:43:37.42 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:43:37.42 spid67 Folder 7 is not assigned to user 493 Proc Name: ags_workflow_sess_count. 2006-12-01 22:43:37.43 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:43:37.43 spid67 Folder 7 is not assigned to user 493 Proc Name: ags_workflow_sess_count. 2006-12-01 22:44:37.51 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 22:44:37.51 spid58 Folder 7 is not assigned to user 613 Proc Name: ags_workflow_sess_count. 2006-12-01 22:46:07.00 spid67 Error: 60132, Severity: 15, State: 1 2006-12-01 22:46:07.00 spid67 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2006-12-01 23:00:20.65 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:00:20.65 spid58 Folder 7 is not assigned to user 949 Proc Name: ags_workflow_sess_count. 2006-12-01 23:00:20.67 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:00:20.67 spid58 Folder 7 is not assigned to user 973 Proc Name: ags_workflow_sess_count. 2006-12-01 23:02:33.07 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:02:33.07 spid66 Folder 7 is not assigned to user 1010 Proc Name: ags_workflow_sess_count. 2006-12-01 23:04:38.10 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:04:38.10 spid58 Folder 7 is not assigned to user 1247 Proc Name: ags_workflow_sess_count. 2006-12-01 23:04:38.12 spid58 Error: 60132, Severity: 15, State: 1 2006-12-01 23:04:38.12 spid58 Folder 7 is not assigned to user 1266 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.59 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.59 spid66 Folder 7 is not assigned to user 1659 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.59 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.59 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.59 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.59 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.60 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.60 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.60 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.60 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.62 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.62 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.64 spid66 Error: 60132, Severity: 15, State: 1 2006-12-01 23:06:08.64 spid66 Folder 7 is not assigned to user 1812 Proc Name: ags_workflow_sess_count. 2006-12-01 23:06:08.64 spid66 Error: 60132, Severity: 15, State: 1
This section shows from 4am onwards
2007-01-13 04:05:09.87 spid71 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:09.87 spid71 Folder 7 is not assigned to user 613 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:13.40 spid75 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:13.40 spid75 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:16.15 spid77 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:16.15 spid77 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:17.29 spid61 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:17.29 spid61 Folder 7 is not assigned to user 660 Proc Name: ags_workflow_sess_count. 2007-01-13 04:05:18.12 spid69 Error: 60132, Severity: 15, State: 1 2007-01-13 04:05:18.12 spid69 Folder 7 is not assigned to user 63 Proc Name: ags_workflow_sess_count. 2007-01-13 04:10:28.81 spid51 Unable to load OLE/DB initialization service. 2007-01-13 04:58:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 04:58:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 04:59:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 04:59:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:00:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 05:00:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:01:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 05:01:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:02:12.21 server Error: 17883, Severity: 1, State: 0 2007-01-13 05:02:12.21 server The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x250A5C68. 2007-01-13 05:03:12.21 server Error: 17883, Severity: 1, State: 0
Hi Guru,Our HR sql 2000 production server is 800.760 built (SP3a) with 2GB ofRAM and 2 CPU hiper threading. This server is very low activity whereprocessor runs average 1-3 during the day. However, in the last twomonths, I've seen the following message occurred a few times on thisserver.Error: 17883, Severity: 1, State: 0The Scheduler 2 appears to be hung. SPID 0, ECID 0, UMS Context0x0381F660.I did extensive research and read both KB 815056 and 10885 but I couldnot correlate these KBs in to my issue. The reason is, I don't thinkour server is very busy to cause the checkpoint process to be delayed.The database keeps growing only 5-10MB in a week and I allocated thespace during off hour.What is the solution to fix this issue? Will I fix this issue byapplying the hotfix MS03-031?Thanks so much,Silaphet,
hi,everyone!I meet strange thing when I create a maintance job for backup alldatabase.and this backup job just stands "Executing job step '(step 1)'" for averylong time .SQL server startup account is this account for network bakcupafter I issue sp_databases sp, I found my full database size only 1GB,and I found my backupfile is complete.I view event log and Sql server Log and no found error!why do it take so long time, but stands 'executing ' status and neverfinish.help me!best regards!
My SQL CE Replication is hanging during a full CreateDatabase download. My SDF file is around 13 MB loaded onto an SDIO card. I need to be able to blow away the SDF file and fully reload from remote locations.
I get all of the table 'upload' and 'download' async events and it appears to be working but then just hangs until I guess the device runs out of memory. I get several beeps and then the hourglass. After a reboot, the DB file is not usable.
I've been using SQL CE 3.0 for awhile and it has worked ok in the past. I upgraded to SQL CE 3.5 but I see the same behavior.
My replication data consists of about 30K inserts across about 30 tables.
Any ideas on how to debug a problem like this? I'm really stuck with this bug.
I have a job that FTP's a backup file offsite daily. Sometime the job hangs (for undetermined reason). The job never terminates. Is there ar way to force termination of the job after so many minutes? This is a Operating System command job.
I see the parameter "Shutdown Timeout Interval" in SQL Server Agent - currently set to 15 seconds. This apparently is not used or not working, as my job was hung for several days and it was not detected. The job runs daly. Since the prior run was "still running - hung", it didn't start, causing my offsite backups to fail following the job hang.
How can I force termination of a job if it doesn't complete in so many minutes?
Hi, excuse me if this problem has been discussed before!
We handle the addmittance in our university with IIS 4.0 and MS SQL Server 6.5 ... a group of 12 operators keep the server busy entering the information about students... I run backup of the hole database on every 1 hour in order to have a recent copy of the date base in case the disk fail (we had bad luck with a quantum HDD few weeks ago). The problems begun when the data base got to 18 MEGs and at about 32 connections to the SQL server when the dump finish the server goes out...
Anyone heard about this before and how to handle it? Yours truly WarJo
hello: My situation is (1) I upgraded MS SQL 7.0 from original edition to SP 4 (2) DTS packages which download data from an oracle server work fine both on a remote machine and on the Server (3) When these packages are scheduled to run as jobs they do not succeed and do not fail they just keep running e.g for 58 hours over the weekend (4) even if I start the job on the server I still get the same behaviour:
We have initiated reinitialize subscription by which snapshot agent is started and hanged at 26%.We have a publication of 6 articles, transactional replication, using SQL Server 2008R2.
Hi guys, I am having a serious problem on my SQL server. Assuming there's a web server (Cold Fusion in IIS) connects to my SQL server (SQL server 2005 and million records in it which consider quite big for the db size), it works fine and run smoothly during weekday. However, there will be lots of users accessing the db through my web application (located at my web server) until my web application get hang. Not only that, even I want to access my SQL server from my place using management studio also fail.
I try remote desktop into the SQL server, view the 'Task Manager', it shows 1-2% CPU usage that it takes; and i'm able to open the SQL server using management studio. Therefore, I try to restart my web service( IIS ) , and it still unable to open my web application. However, once I restart the SQL service, my web application is available. This issue happens to me every weekend with several times. It's no point for me to restart the SQL service again and again.
1) What's the reason that I need to restart the SQL service then only I can open the web application? Is it the SQL server hang or the connection problem?
2) Is it lots of record in the database causing the server gets hang since lots of user accessing the database? 3) Where can I check out the exactly problem on it ? IIS log or SQL log?
Hope can get any assistance from here and get a solution/suggestion from you guys as soon as possible.
I have a problem with a DTS package to import data from one of our Ingres based Databases.
I've recently moved the DTS package from one server to another and recreated the Ingres ODBC Settings, which are all OK.
When I run the package through EM and the CMD line, it runs OK, but not as a scheduled task.
I've had a look at a KB Article Q318819 and followed the steps about package threads on 3rd party drivers, but this doesent help, nor does making sure DTSRun isnt in the current task list.
I am using Windows 2003 Standard Server (stand alone) and trying to install SQL Server 2000 Enterprise edition. The installation stops whenever I have entered the sa password (the dialog box disappeared and then nothing happed, but the "setupsql" process (something like this) is still there).
The same happened when I install SQL Server 2000 in Windows 2000 Server. For Win2K, I can first install SQL Server 7.0 and then upgrade to 2000 (same SQL Server 2000 installation CD!). However, Windows 2003 doesn't support SQL Server 7.0. So I can't use this method...
lately we are experiencing some very strange behaviour on the part of our SQL-Server.
We are using SQL-Server as a combined Database for one COM+ application and one J2EE-Application. All of this is installed on the same machine (dual-CPU, 2 GB RAM).
This setup has been up and running for almost a year now.
In the last two weeks there have been incidences where the performance of SQL-Server is decreasing steadily until it finally hangs completely (just SQL-Server, not the machine itself).
This happens 2-3 times a week, curiously always between 9 and 10 a.m.!
After stopping and restarting the actual SQL-Server "Service", everything is back to normal (until the next morning or the morning after that).
There are a few automated batches that access the database via the COM+ Server. These run at night and are completed before work begins at ca. 7 a.m.
Profiler-Logs show a few "Escalate Locks", but those alone cannot account for this strange behaviour.
SQL Server 2005 a lot of time hangs. Any advice is highly appreciated! Please have a look at the error log from this link http://download.yousendit.com/B787CBD235FC2417
This morning one of our jobs failed, so I eventually ran the SSIS package manually and found the flow "hanging" at a script task. The fix was to open the script in design mode and hit Save, which I believe compiles the code. Then the package ran as it has normally for several months.
There was a recent Windows update run on this server. I don't know what was updated, as it was the DBA that did that. It seems possible that a .NET framework update would cause this problem, does anyone have any thoughts on this or anything else causing this?
Given the extent of some SSIS environments, and ours is pretty extensive, this could be a real pain to go in and manually recompile each and every script task.
I have an issues that worries me alot. I have SSIS packages scheduled in SQL Agent and they sometime error out or hang in Agent but never when i run them in BI IDE (Visual studio). There are two particular packages that always hang, alway in Agent but when i run them in BI IDE, they run just fine. Im was running them under in Agent under type= Sql server intergration services and also tried running under type = Operating System (CmdExec). Both types have the same problem. The packages hang. The log files dont say much, because the packages hang, no logging is doing so i dont get any infomation to determin what is going on. Can someone please help me ou.
I've been put in charge of a SQL server recently and I'm completely new to maintaining SQL. For some reason several clients when they are doing their database processing I get network_io hangs and everything comes to a halt. I have to go in there and manually kill the SPID and everything continues where it left off.
SQL Setup
Server 2012 R2 SQL 2014 SP1 Dell 850 VM running in Hyper-V 50GB RAM FusionIO Card 10GB Ethernet between clients and server
All workstations are pretty much
Windows 7/8.1 10GB 64+GB of RAM Several CPUs SSD and SATA hard drives
It's very hit or miss when this occurs as well, however, it's always the same NETWORK_IO cause.
I've read on the Internet about how the client keep up with what SQL is sending. Could this be poor programming or do I need to investigate my network setup?
When I try to free previously registered DLL, server is starting to execute query and it takes a number of minutes and nothing happens.
Here is an example:
sp_addextendedproc 'xp_test','test.dll' //works fine
exec master..xp_test '999' //works fine
sp_dropextendedproc 'xp_test' //works fine
dbcc test(free) //do not work
I've tested it on:
SQL MSDE SP3 //i was getting an acces violation first: spid 51 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION at 0x00000000 SQL MSDE SP4 //but on this SP I have the same behaviour as on server 2005 / infinite query execution time SQL Server 2005 standard //infinite query execution time SQL Server 2005 standard with SP2 //infinite query execution time
I can't understand this because this started after chaning my machine.
It worked without any problems on the previous one and I've used this metod very often on the same dll which hasn't changed.
I'm creating my first report. I do "new project" > "report server project". Thereafter I create my shared datasource. Thereafter I try to add a new report. It ask to enter my querry.
I've built up my querry previously with the querry analyser in SSMS, and there it runs quite fast.
But when i copy-paste the querry in the reporting designer, and i choose to preview it, it takes more then 20 minutes.
however, my querry it quite big, but i've written querries ten times larger in my life. (it's about 50lines: 10 querries, union-ed together and in each one i have 4 innerjoins.... all tables are even almost empty, so it's not that indexes are missing or whatever)...
is it known that in the report designer querries are much more slower????
