Viewing 15 posts - 196 through 210 (of 219 total)
If you don’t get much info with DBCC INPUTBUFFER, find out the SPID as mworku suggested. And launch the trace flag with SPID or userid criteria. And check your t-sql...
June 6, 2003 at 8:55 am
Try launching the trace flag 3111 and see. Even though MS KB says it will happen only if the transaction log back size more than 4GB, I’ve seen this on...
June 5, 2003 at 2:56 pm
What exactly the error message says? What is the severity it shows?
June 5, 2003 at 2:40 pm
You can get the Error message from master.dbo.sysmessages. You need to capture the Error code with help @@Error and use the following one
Select substring(Description, 1,150) form master.dbo.sysmessages where Error =...
June 5, 2003 at 10:31 am
If you don't care about the log file, you may want to schedule a job every often to truncate the log
use <Database_Name>
go
dbcc shrinkfile (Log_Filename, 300)
go
backup log Database_Name with no_log
go
June 5, 2003 at 10:05 am
You can never block sa access, change the sa password and remove the Built-In Admin Acct. By doing so you can block the rest of the users. Also make sure...
June 5, 2003 at 9:59 am
If the log file still grows after the Truncate log on check point ON, you might want to schedule a hourly job with the following commands
use <Database_Name>
go
dbcc shrinkfile (Log_Filename, 300)
go
backup...
June 5, 2003 at 8:21 am
I guess you need to Rebuild the master database and re-attach all the user databases.
June 4, 2003 at 11:25 am
You mean the Transaction log? Or the transaction log Backup file? If you are referring to the T-Log
You can use
DBCC LOG (DBID/DBNAME, Type = 1/2/3/4)
This gives you only...
June 4, 2003 at 10:41 am
With simple recovery you can recover to the point of the last backup. You cannot restore the database to the point in time. Since most of your database set to...
June 4, 2003 at 10:10 am
If there is so many things to consider, just change the pwd of the login. It is always easy to manage to run all your jobs or any thing with...
June 4, 2003 at 9:11 am
How you are connecting to the server? Terminal server? Remote Desktop? Is the tools installed on the server? Also if yes try changing the protocol
June 3, 2003 at 2:35 pm
If you are using sa account make sure your server security is configured to allow both sql and windows accts. Also try change the utility to Named Pipes
June 3, 2003 at 10:55 am
Try this
Create table users
( Userid int,
Pwd VARBINARY(32) )
INSERT INTO users VALUES (3,CONVERT(VARBINARY(32),PWDENCRYPT('TTT')))
Select * from users
Declare @Valid int
SELECT @Valid = PWDCOMPARE('TTT', Pwd) FROM users where Userid = 3
Select @Valid...
June 2, 2003 at 2:29 pm
Viewing 15 posts - 196 through 210 (of 219 total)