I am relatively new to SQL Server so excuse my ignorance.
I have noticed in many of my SQL Server 2005 instances that the tempdb database is very often reporting the log mode as waiting active_transaction or waiting checkpoint.
Is this of concern, how can I determine the cause of these waits and how can they be reduced or eliminated ?
Hey fellow Swynk'ers,
I have a question for ya’ll. Our company plans on migrating to active directory soon. I would like to use mixed mode for security. My question is, will this work? Can SQL 6.5 pick up on Active directory or is this handled at the OS layer?
Thanks,
Lee E. Smith
On my current contract we have a SQL 2005 box with a user database and the tempdb database in 6.5 compatibility mode. I would like to remove the user database and change the tempdbs compatibility mode. When you try and use EM just about everything fails with errors about collation or syntax. From what I have found it could be related to the tempdb being in 6.5 compatibility mode but either way I would like to remove this old unused DB.
My question is after I remove the user DB and reset the tempdb compatibility mode what will or could break? I haven't been able to find much on what would change or what to look out for after the change is made. Has anyone else done this? If so what issues did you face.
Thanks
Doug
Hi all,
I have a customer with an RS installation in a DMZ, using ADAM for its authentication.
The problem I have is as follows :
When setting up the execution log reporting (supplied as part of the standard install) all information being captured for report execution e.g Which user ran a specific report and when, is coming up with 'UNKNOWN' for the user name.
Does anyone have any idea where to look to fix the recording of user information? I am not sure whether it is a RS or A.D.A.M issue.
Thanks
Clint Pugh
Something strange is happening to our SQL Server DB (2000). Thetempdb transaction log file continues to grow (quite slowly) for noapparent reason. We have it in simple mode, and I have tried a manualcheckpoint command and manual shrink (of the log file only). Thereare no unusual SQL's (large or small) going on. A "heavy hitter" wouldmake it grow fast, not 10 MB every 30 minutes or so. This server hasbeen in production for over a year with no similar issues to this.Anyone encounter a similar situation? This started (as far as we cantell) sometime yesterday. It is growing about 200 MB a day, and is upto 600 MB now, with all but 8 MB "used". For now we added space, butof course that is not a long term solution. The two "data" files(each had a 200 MB initial allocation) have never gone much above 100MB each used (they are each about 100 MB now and have been that wayfor several days, but have shrank and grown). There are about 30small to medium sized "regular" databases on this instance.Any help would be appreciated, especially if there is a way we can fixthis without bouncing the engine (I know, wishful thinking...). The OSis Win 2000, SP3. SQL Server is at 2000, SP 3a.THANKS IN ADVANCE!
View 3 Replies View RelatedHi all,
I m trying to get record from one server to another using Commit and Rollback feature in the Sql Server and getiing error message--
"No transaction is active."
below is my sql block
BEGIN TRAN
BEGIN TRY
INSERT INTO [SERVERNAME1].[DATABASENAME].[dbo].[TABLENAME](PurchaseByUserID,price,purchasedate,affiliateID,LicenseeID,debittype)
SELECT PurchaseByUserID,price,purchasedate,affiliateID,LicenseeID,debittype
FROM [SERVERNAME2].[DATABASENAME].[dbo].[TABLENAME]
WHERE Convert(smalldatetime,purchasedate)>=Convert(smalldatetime,'2/14/2008 00:00:00') and Convert(smalldatetime,purchasedate)<= Convert(smalldatetime,'2/14/2008 23:59:59')
COMMIT TRAN
END TRY
BEGIN CATCH
Rollback TRAN
END CATCH
END
Please replay ASAP.
Posted - 05/03/2008 : 13:37:25
Hi all,
I m trying to get record from one server to another using Commit and Rollback feature in the Sql Server and getiing error message--
"No transaction is active."
below is my sql block
BEGIN TRAN
BEGIN TRY
INSERT INTO [SERVERNAME1].[DATABASENAME].[dbo].[TABLENAME](PurchaseByUserID,price,purchasedate,affiliateID,LicenseeID,debittype)
SELECT PurchaseByUserID,price,purchasedate,affiliateID,LicenseeID,debittype
FROM [SERVERNAME2].[DATABASENAME].[dbo].[TABLENAME]
WHERE Convert(smalldatetime,purchasedate)>=Convert(smalldatetime,'2/14/2008 00:00:00') and Convert(smalldatetime,purchasedate)<= Convert(smalldatetime,'2/14/2008 23:59:59')
COMMIT TRAN
END TRY
BEGIN CATCH
Rollback TRAN
END CATCH
END
Is there a stored proc to tell details of the oldest active transaction ?
View 3 Replies View RelatedI was expecting this to return an active transaction
begin transaction
select * from table1
dbcc opentran
(no COMMIT or ROLLBACK)
Server 1: Win2003, Clustered Environment, SQL 2005sp2
Server 2: Win2003, no cluster, SQL 2000sp3a
Server 3 (aka, client): Win2003, using ODBC (sql native client) to connect to server 1
I'm attempting to run an SQR that connects to server 1, yet updates server 2. Right now, all I'm doing is the statement
delete from <server2>.<database>.dbo.table
and am getting the error (DUL41 is server 2):
SQR 5528) ODBC SQL dbexec: SQLExecute error 7412 in cursor 1:
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider "SQLNCLI" for linked server "DUL41" returned message "No transaction is active.".
(SQR 5528) ODBC SQL dbexec: SQLExecute error 7391 in cursor 1:
[Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "DUL41" was unable to begin a distributed transaction.
If I use query analyzer (or whatever we're calling it now) to connect to server 1 and run the statement, it works fine. But, SQR is connecting via ODBC (that's different) and also is SQR.
I'm also not 100% sure all of the new MSDTC aspects are configured correctly, but I've gone through the settings a few times. Right now, I pretty much have everything set about as open as possible (these are test servers on the same network) and am still getting the error.
Any help, or ideas I could try, would be great. Thanks.
This may be a simple answer, but I was wondering when setting up transactional replication with updatable subscriptions why does this error occur?
Error:
The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "REPLLINK " was unable to begin a distributed transaction.
Changed database context to 'MyDB'.
OLE DB provider "SQLNCLI" for linked server "REPLLINK" returned message "No transaction is active.". (.Net SqlClient Data Provider)
I've looked for MSDTC security documents and checked every box in the security dialog and selected the 'No Authentication Required€™. MSDTC and SQL Agent are running as NETWORKSERVICE user. I also setup permissions on each individual DCOM Objects for SQL Server. And MSDTC service is running. Both Servers are SQL Server 2005 Standard and Windows 2003 R2. The publisher is on the same box as the distributor. No domains or trusts setup on either. This error occurs when changing data on the subscriber.
Thanks,
Patrick
We are having problems around TempDB as follows:
Stored Procedure with complicated Select Into's can block the TempDB's Transaction Log from being dumped (Set to Truncate Log on Checkpoint).
TempDB = 600MB (Disk)
When this happens, most of the developers get blocked until the server is rebooted.
Is there something else I can do besides Trunacte Log on Checkpoint for TempDB? I was under the impression that TempDB should share data and log, but should I have a separate log device for tempdb?
Thanks in advance. we are tired of rebooting the server.
Hello,
I am new to SQL Server 2000 and I have a specific question about the transaction log for tempdb.
Is it true that when a user disconnects from SQL Server, not only are his/her objects in tempdb dropped but
references to those objects in the transaction log are dropped too? On several occassions I rebooted my
machine but I noticed that the same amount of log space in tempdb was still used (according to dbcc
sqlperf (logspace)). Any information would be appreciated.
HelloI have questions about how works transaction log et the databasetempdb in SQL Server and I hop you could help me- Is it possible to reduce the size of the transaction log fil duringan execution ? Indeed, I have a script inserting a very large quantityof data (many Go) and during that process my transaction log file useall the space avaible on my hard drive. Is there any way to solve thatproblem ?- Is it possible to limit the size of the database tempdb ? I have ananother script inserting data using a select joinning 2 tables ofabout 20 Go with group by. If I execute that script sql server seemsto freeze and I must kill the process. What can I do ? Is the onlysolution is that I must make more avaible space on my hard drive ?Thanks in advance for your answers.K.
View 3 Replies View RelatedBesides restarting and expanding, is there a quick way to remedy the error:
"The log file for database 'tempdb' is full. Back up the transactional log for the database to free up some log space."
But, you can't back up a tempdb, so I was wondering if anyone had some thoughts on this.
Thanks
Has anyone ever run across you Tempdb Transaction Log being full and getting an error 9002 severity 17 state 2? One issue is the tempdb was created with all the defaults 1mb in size. As well as my transaction log is now at 4 GIG in size.
View 4 Replies View RelatedWe have a stored procedure that uses temp tables and must gather a lot of data. When we stress test this stored procedure, the tempdb transaction log fills up.
We tried using "Select Into" for our tables. That caused us not to write to the transaction log but it caused problems because it locked up sysobjects.
Is there some other way not to write to the transaction log?
Hi
How to clear the Transaction Log of Tempdb?(Other than Restarting the SQL server)
Thanks in Advance
Regards
Magesh
This question is very basic. When you do a ProcessAdd, is it within a transaciton mode?
I mean, if the ProcessAdd fault and stop when it meets a mistake, the records before the midstake will still be in the cube or not.
Thanks.
SQL2005 SP2+Cum.Patch Rrevision 4 (9.0.3175)
I always get this message, when i want to run a stonger query or a transaction that takes a longer time:
"The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"
I checked the log_reuse_wait_desc column: LOG_BACKUP
I ran tr log backup...nothing...
I tried to set to simple reco mode the db...this helped... temporaly...i got again below message.
( i wouldn't like to set to simple mode the db because the size of db is 160GB now....so i don't want to eun a fullbackup)
TempDB size is 50MB now and it can grow until 7GB.
The trqansaction log size is 14GB and there are 50GB free space, so it can grow.
This symptom occurs since i installed SP2 and the CP Rev.4.0
What is the real problem ?
Can someone please help me with this problem....
I am having problems entering info into my database. I haven't had any problems so far. But all of a sudden when I try to add info to some of my columns I get the error message:
"Transaction cannot start while in firehose mode."
My column type is nvarchar. I thought I might have the length set to low, but I set the length as high as 400 and can't fit the same length of entries as some of my 200 length columns.
And also there are no constraints or foreign key values related to the column. I even created a new column with nvarchar at 400 length just to test it and same error. I'm stumped...
Thank you whomever knows this problem....
-alec
Hello everyone,
In SQL Server Enterprise Messenger I've been getting the following error in a pop up window:
"Transaction Cannot Start in Firehose Mode"
Besides this error that is featured in the Microsoft KB
BUG #: 228790 at
http://support.microsoft.com/default.aspx?scid=kb;en-us;286199
Is there any other reason why someone could open a table (that only has around 200 rows in it) and get this error message upon trying to update a row?
I have a 28Gb temp db transaction log which I want to dump halfway through a process, I have tried;
dump tran tempdb with no_log
which seems to have little effect.
Thanks for your help.
Andy
Hi Guys,
Refering to my previous post I've a package which easily run when transaction mode is Supported but when i put it to Required and All DFs are supported inside the sequence container it won't run.
Well technically it goes and pass step 1, so it goes to green but regardless of what i put in the 2nd DF it won't run. It just hangs in there.
When i check the component service and check DTC, the transaction would be running but never commited.
I have done most of the things about DTC and configuration with the MS articles as this package was failing before but now it just sits at this point.
Any ideas?
Thank you
Gemma
Hi all:
I know i can use the sentence SET IMPLICIT_TRANSACTIONS ON in a Stored Procedure to force SQL Server to set the connection into implicit transaction mode.
Have i a sentence or configuration to force all SQL Server connections to implicit transaction mode?
Thanks in advance.
hi,
we have a SQL Server 2000 database which we set to 'SIMPLE' recovery mode at 6pm (due to nightly large data loads). We revert back to 'FULL' recovery mode at 6am.
My understanding was that in 'SIMPLE' recovery mode, the transaction log would not grow because it would automatically be truncated after a checkpoint. However this is not the case. I thought perhaps it could be due to a long running uncomitted transaction, but when I ran 'dbcc opentran', the oldest running transactions doesn't last for more than a couple minutes. I manually run a 'checkpoint' command as well in the hope of forcing the transaction log truncation. I repeat this a couple of times to no avail. When I run 'dbcc sqlperf(logspace)' , I can still see the transaction log growing.
It is not until I run 'backup log db with truncate_only' that the transaction log gets truncated.
I do not understand, why the transaction log does not get automatically truncated in SIMPLE recovery mode?
Andrew
Is there a formula for calculating how expensive a transaction will be in terms of disk space used before its run. I dont want it accurate to the MB, but rough enough so I can determine how much additional space to assign to a transaction log or SAN volume.
Currently we're reindexing ~25billion rows, nothing too wide, say 12 columns consisting of 1 varchar(50) and the rest ints, bits and money.Roughly speaking if I reindex the clustered index on an int indetity, (with sort_in_tempdb) how would I calculate the the disk space used?
today I've put in production a big database accessed by 200 concurrent users, this database has READ_COMMITTED_SNAPHOT set to ON.I know that RCSI set to ON is very aggressive on tempDB so I'm monitoring it.I've noticed that the Transaction log space usage (%) on TempDB is slowly but ever increasing, I mean in the last 24 hours I've started from a 99% space free, now we are 37% space free...is it normal? TempDB log is 35GB in size.
View 6 Replies View Related
We are currently testing a Replication topology as follows:
SQL Server 2005 Developer as publisher and distributor of a push updatable transaction replication
2 SQL Server 2005 Express clients as subscribers.
The replication is working great. If the connection is lost, the subscribers switch from Immediate to Queued Updating, and seem to shift back to Immediate when they regain the connection.
My question is to determine if there is a way that I can ask SQL Express on the client which mode is it currently running, or ask SQL Express if it has a current live connection to the distributor.
I know that they are usually mutliple ways to accomplish tasks, and I would be open any suggestions, preferrable programming in VB (such as with SMO or RMO) or using stored procedures or functions.
I hope this give some people something to chew on during the weekend and thank you to all that have taking the time to read this.
Hi there - can anyone advise on the following issue. We have recently performed some server side tracing on a particular SQL instance over 24hr period. We are now attempting to load these into a database for analysis. Here lies the problem.
When we are loading the profiler trace files (one at a time) into the database the transaction log is growing at an excessive rate. Even though the database is in SIMPLE mode.
We are loading the traces using the command:
INSERT INTO sqlTableToLoad
SELECT * FROM ::fn_trace_gettable('MytraceFileName', DEFAULT)
Can anyone advise how we could possibly get round this issue as we're running out of space due to the transaction log.
Thanks
I have a table with the following columns employeeSessionID, OpDate, OpHour, sessionStartTime, sessionCloseTime. I need to see how many users remain active per hour. I can calculate how many logged in per hour, but I am stumped on how to count how many are active per hour. I have a single table that stores login data. I have created a query that pulls out the only the data needed from the table into a temp table using this query. Also note it is possible that the sessionCloseTime is null if the device has not been logged out this would need to be counted a active.
TABLE NAME #empSessionLog Contains the time stamp data OpDate, sessionStartTime and sessionCloseTime.
OpDatesessionStartTimesessionCloseTime
2015-01-202015-01-20 14:32:59.1302015-01-20 14:33:14.6299166
2015-01-202015-01-20 06:58:33.7302015-01-20 15:27:16.9133442
2015-01-202015-01-20 09:56:22.8402015-01-20 17:56:29.7555853
2015-01-202015-01-20 05:59:18.6132015-01-20 14:05:19.0426707
[code]....
can see how many sessions logged in per hour with the following statement:
SELECT
opDate,
FORMAT(DATEPART(HOUR, sessionStartTime), '00') AS opHour,
Count(*) AS Total
FROM #empSessionLog
Group BY opDate, FORMAT(DATEPART(HOUR, sessionStartTime), '00')
Order BY opDate, FORMAT(DATEPART(HOUR, sessionStartTime), '00') ASCResults:
opDateopHourTotal
2015-01-20041
[code]....
Where I am stuck is how do I count the sessions that remain active per hour until the session is closed with the sessionCloseTime.
Hi
I am having some teething problems while installing SQL on a 3 node cluster. Within the Cluster configuration I have 3 Cluster Groups with each of them having their associated disk resources. All these disk resources physically exist on a SAN.
The actual cluster is running absolutely fine and I can access all the disks from their respective owner node. The problem only starts when I start installing SQL Server 2005 on this cluster. I specify the Cluster group from the Cluster Group Selection and choose the desired partition and then the error message pops up
"There is not enough diskspace on the destination disk for the current SQL Server data files. To proceed, free up disk space to make room for data files, or install the data files to a different drive"
But the disk I am trying to install it on is 264Gb and none of it is used. I have also tried to change it to a different disk within the same Cluster group but to no avail. I have even tried to install it in a different cluster group all together but I get the same error message.
I have googled around havent found anything so far. The disks have got full permissions for the account I am installing SQL with.
Any help will be much appreciated.
Regards
Adnan
Hi
I am newbie in SQL Clustering. I have set up a Windows Server Cluster with 2 nodes and am having the following problem with Physical Disk resource for cluster groups:
My Default Cluster Group (named Cluster Group) has IP Address, Network Name, Physical Disk and MSDTC resources. In addition to that my Default SQL Server instance resources are also in this group. I had this initial set up for Active/Passive mode.
Now I am trying to set up a SQL Cluster in Active/Active mode. For this I have to install another instance of SQL Server in the existing cluster and make a separate cluster group for its resources. I made a new cluster group (SQL Instance Group) with an IP Address and a Network Name resource for this new instance but I dont have any Physical Disk resource to allocate to it. As such while installing the SQL Server Instance I get stuck when I'm asked to select the quorum disk to be used.
Is it possible to configure two quorum disks, one for each group?
What's the concept of dedicated disks resource for each sql instance in a group? Is this same as the quorum disk? If this is not a shared disk how do I configure a dedicated disk resource for my second cluster group (SQL Instance Group)?
Anyone could please help me out with this?