Viewing 15 posts - 1,561 through 1,575 (of 1,583 total)
Can you please suuply the TSQL code you're using?
Ex:
EXECUTE msdb.dbo.sp_send_dbmail @recipients = 'jdoe@gmail.com'
, @subject='Test', @body = 'Test'
Also, you may want to check the settings in >> Management >> Database Mail...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 1, 2011 at 2:56 pm
This could happen for MANY reasons...without knowing your configuration for both SQL and your Server. Considering this occurs at 20-min intervals it sounds like something is scheduled and running....so...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 1, 2011 at 2:47 pm
OMG...talk about an ID10T error...I think maybe I spent too much time looking at it to see the obvious! :s
Thanks for pointing it out 🙂
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
February 24, 2011 at 4:35 pm
I have a function that may help you...of course, you'd have to use dynamic SQL (which has it's own caveats)
It can be used nicely to return a set of values...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
February 24, 2011 at 3:50 pm
Thanks for the reply Craig. This only shows the execution times and steps for everything "after" the build process completes...which runs exceptionally quick (< .5 secs)
It's the actual build...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
February 22, 2011 at 2:02 pm
(from MSDN)
TRY…CATCH constructs will not fire:
1. Warnings or informational messages that have a severity of 10 or lower.
2. Errors that have a severity of 20 or higher that stop the...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 27, 2011 at 9:55 pm
Lynn, sorry I missed that request. The expected result would be an integer value in the prevodometer column for each record in the table.
I don't fully understand why they...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 27, 2011 at 8:58 pm
Sorry! Yes I guess that would help 🙂
CREATE FUNCTION [dbo].[fx_GetLastOdometer]
(@date varchar(40)
,@pan VARCHAR(32)
,@tranid int)
RETURNS int
AS
BEGIN
DECLARE @Odometer int
SET @Odometer = (
SELECT TOP 1 odometer
FROM dbo.[Mileage_Table] WITH(INDEX(idx_TranTime))
WHERE tranid <> @tranid
AND pan=@pan
AND...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 27, 2011 at 10:39 am
Done, thanks for the heads up
http://www.sqlservercentral.com/Forums/Topic1048204-145-1.aspx
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 14, 2011 at 2:12 pm
If I wanted to calculate the average run time for a given SQL Agent job over the past month...knowing that the run_duration column in sysjobshistory is represent as 33848, meaning...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 14, 2011 at 1:59 pm
How would you go about adding actual time fields together?
For instance, you have SQL Agent Job run times as follows:
HH:MM:SS
03:58:19
04:18:42
03:14:09
11:31:10 (which would mean 11 hours, 31 minutes, and...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 14, 2011 at 1:30 pm
Perhaps I am missing something but this stored-procedure only tells you historically the last time a SQL Agent job started and finished, it does not tell you the start time...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 14, 2011 at 12:31 am
Found it!
Turns out that the software install is user specific and must be individually licensed by each user on the server: Simple installing it as an administrator and registering it...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 12, 2011 at 3:59 pm
Again, I can run it from our production box just fine as is (and is SQL 2005), but not from the new box which is SQL 2008.
With the reporting model...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 11, 2011 at 4:26 pm
Here are the results:
(1 row(s) affected)
ID TheOutput
----------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 NULL
(1 row(s) affected)
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 7, 2011 at 11:23 am
Viewing 15 posts - 1,561 through 1,575 (of 1,583 total)