Viewing 15 posts - 256 through 270 (of 372 total)
This two step process should get what you're looking for. The CPU column is cumulative, so if the job is started using sp_start_job then that should be a pretty...
March 27, 2008 at 3:43 pm
Jpotucek (3/27/2008)
I am using the above code as a second step on my maintenance jobs to so email notifications when the job fails. I can't for the life of...
March 27, 2008 at 11:39 am
Another option is to create a custom perfmon counter; SQL Server, User Settable Object
Then, use that performance counter in an Alert to send the message.
Additionally, if you ever want to...
March 27, 2008 at 4:44 am
homebrew01 (3/26/2008)
Hmmmm.........I only have 1 log.trc file in an unused folder, last modified on 8/2007
Did you query sys.traces? If it's running, the location will be shown there as well.
March 26, 2008 at 12:32 pm
Jeff,
Try changing "DROP" to "DELETE", or set a WHERE clause with EventClass = 47 for Object : Deleted events.
Opening the traces in Profiler will resolve the EventClass to readable names...
March 26, 2008 at 12:22 pm
Todd,
I am not sure how this would work. This function is used to import trace files from SQL profiler. In order for this to work, the OP would...
March 26, 2008 at 11:12 am
Your code seems to work fine by just adding another variable.
DECLARE @newname VARCHAR(50)
DECLARE @DATE AS VARCHAR (8)
SET @DATE = CAST(convert(varchar, getdate(), 112)AS VARCHAR(8))
SET @newname = 'ATT_' + @DATE
EXEC SP_RENAME 'ATT_',...
March 26, 2008 at 9:27 am
I should have qualified the fn_trace_gettable comment. Was the database still attached and you suspect someone used DROP DATABASE? Then the default trace should show that. If the...
March 26, 2008 at 5:31 am
The default trace should show the drop operation, including the hostname and spid where it came from.
For example:
SELECT * FROM ::fn_trace_gettable('C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\log_1.trc',0)
March 26, 2008 at 4:26 am
In the Results tab remove Result Name "1".
"If the result set type is Full result set or XML, you must use 0 as the result set name."
- SQL Server 2005...
March 26, 2008 at 4:10 am
Looks like you have the ResultSet configured to "Full result set"? If so, the Result Name has to be "0", it can't be set to column names.
If you set...
March 25, 2008 at 7:00 am
How are you trying to connect: locally or remotely? In SSMS you would connect using the Database Engine Query, not Database Engine in Object Explorer.
You also might want to...
March 24, 2008 at 6:26 pm
It's logged, but it is logged differently. "ALTER TABLE tablename DROP COLUMN columnname" logs only the removal of rows from some system base tables, which store metadata. It doesn't...
March 24, 2008 at 7:29 am
My recollection is that your step #3 (drop the old column) still has the same problem.
ALTER TABLE ... DROP COLUMN ... is a metadata only operation since it...
March 22, 2008 at 6:43 pm
That explains why it is filling up the log file. If somebody could suggest a solution, I would appreciate it.
You can limit the impact and keep the log file...
March 22, 2008 at 12:18 pm
Viewing 15 posts - 256 through 270 (of 372 total)