Viewing 15 posts - 841 through 855 (of 3,011 total)
Please do not cross post:
http://www.sqlservercentral.com/Forums/Topic1112853-1550-1.aspx
May 21, 2011 at 1:18 am
Please do not cross post:
http://www.sqlservercentral.com/Forums/Topic1112853-1550-1.aspx
May 21, 2011 at 1:18 am
Why do you have such a high number of backup job failures?
We backup at least 20 times that number of databases every day with far fewer backup job failures.
May 21, 2011 at 1:16 am
Most systems I have worked do not use ordinal date; I personally don't see much value in it.
However, I have worked on applications that used the ordinal date (Julian date)...
May 20, 2011 at 3:53 pm
Welsh Corgi (5/20/2011)
Michael Valentine Jones (5/20/2011)
Welsh Corgi (5/20/2011)
May 20, 2011 at 1:34 pm
Welsh Corgi (5/20/2011)
I'm sure that the USNO has it's reasons but the US Military Finance and Accounting, etc advances the Julian Date at midnight as opposed to noon.
That is something...
May 20, 2011 at 12:23 pm
sqlfriends (5/20/2011)
1. For both sql 2005, or/and sql 2008, does it still...
May 20, 2011 at 10:23 am
Ian Scarlett (5/20/2011)
Michael Valentine Jones (5/19/2011)
May 20, 2011 at 10:15 am
This will convert a datetime value to the ordinal date (what you calling Julian date).
select
OrdinalDate =
(1000*datepart(year,a.[DATE]))+
datediff(dd,dateadd(yy,datediff(yy,0,a.[DATE]),0),a.[DATE])+1 ,
a.*
from
( -- Test Data
select [DATE] = getdate()union all
select [DATE] = getdate()+37
) a
order by
a.[DATE]
Results:
OrdinalDate DATE
-----------...
May 19, 2011 at 10:24 pm
Lee Crain (5/19/2011)
I am missing something.Are my "SET" statements not assignments?
DECLARE @test_dt DATETIME
SET@test_dt = DATEDIFF(D, 0, GETDATE());
SELECT@test_dt
DECLARE @x DATETIME
SET@x = @test_dt
SELECT@x
Both "SELECT" statements produce the same "timeless" timestamp.
LC
The...
May 19, 2011 at 12:24 pm
PLE is also a function of the queries that the server runs. It you have a lot of queries that force scans of large tables, then it will remain...
May 19, 2011 at 12:13 pm
I have a database with about 95 GB of data that produces compressed transaction log backups totaling about 37 GB in a span of about 40 minutes when the weekly...
May 19, 2011 at 10:10 am
As I said before, I would increase the transaction log frequency to every 15 minutes, 24x7. That will help control transaction log file growth and help you identify exactly...
May 19, 2011 at 9:49 am
jpSQLDude (5/19/2011)
Ninja's_RGR'us (5/19/2011)
May 19, 2011 at 9:38 am
One of the reasons to run transaction log backups more often is to control the size of the transaction log files. As was said in another post, it will...
May 19, 2011 at 9:28 am
Viewing 15 posts - 841 through 855 (of 3,011 total)