Viewing 15 posts - 1,126 through 1,140 (of 1,583 total)
Unfortunately no, I've read this great article in the past and while it's great for tuning, it doesn't discuss the difference between reads found in profiler with the reads returned...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 16, 2012 at 12:13 pm
There is a DBScript utility (not sure if it's 100% compatible with SQL versions beyond 2005) but if you run it from a server with SQL 2005 installed on it...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 16, 2012 at 10:59 am
This script returns nothing...which I would have expected to have had "some" rows in it...
SELECT
err.[description],
fail.*
FROM [msdb].[dbo].[sysmail_event_log] err
inner join [msdb].[dbo].[sysmail_faileditems] fail
...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 2:17 pm
Yes. i did finally find an error mesage:
Date3/15/2012 3:10:52 PM
LogSQL Server Agent (Current - 3/15/2012 3:05:00 PM)
Message
[264] An attempt was made to send an email when no email session...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 2:12 pm
Righto....busted again not reading things carefully enough :ermm:
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 11:50 am
Careful with using tinyint here in this case...it doesn't go up to 3000! ::-D
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 11:39 am
Yes of course, legitimate failure...ghost box :w00t:
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 11:07 am
As you can see from the image attachment, this was done initially (again I set db mail and the jobs up the same way on all my servers (+20)). ...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 11:00 am
I did not create a specific alert (as I don't believe it is needed to trigger the email for a job failure). I have not done this on any...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 10:48 am
The safest way to resize tempdb is to schedule a maintenance window, restart the mssql service, resize (increase) the tempdb files to a reasonable size (adjusting the auto growth settings...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 15, 2012 at 8:00 am
Taken from a post by Lowell not to long ago...http://www.sqlservercentral.com/Forums/Topic1265103-391-1.aspx
tempdb is recreated every time the server is stopped and started.
the only way to reclaim the space (as far as i...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 14, 2012 at 9:52 am
Not unless there's something else broken (replication, mirroring, open transactions, etc). They should reach a steady size (or be set to a steady size) and stay there.
Check other maintenance jobs...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 14, 2012 at 9:46 am
Wow that's a large update! Off hand I see an index scan in your execution plan that may save a little time if you modified your existing index to...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 13, 2012 at 1:31 pm
Yes, be very careful...using a parameter for something like this can leave you wide open for malicious attack. Search this site for SQL Injection (or google it)
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 12, 2012 at 7:59 am
Let me get this straight, you're passing in the entire SELECT statement as a parameter?
If that's the case, check the length for your datatype on the parameter for the SQL...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 12, 2012 at 7:44 am
Viewing 15 posts - 1,126 through 1,140 (of 1,583 total)