I may be misreading this, but it seems to me that if an account has 90 minutes on its SLA, and you calculate the business minutes, you should be able...

If 9-million records is 2 Gig, then 500-million records will be about 120 Gig (plus or minus). So, assuming you're using relatively modern hard drives, storage shouldn't be too...

Did you install SQL Server yourself or did someone else install it?

If you installed it, there was an option for setting up Mixed Mode authentication, which means both Windows security...

Generally speaking, I think the best way to migrate full text indexes is to drop the 2000 ones and rebuild them in 2005 as if they were completely new. ...

If the plan is to switch to SQL/.NET in a few months, starting out with Oracle will simply increase costs without any real benefit.

The best thing to do is evaluate...

Please look at:

http://www.sqlservercentral.com/Forums/Topic457395-338-1.aspx

There are some solutions for this at:

http://www.sqlservercentral.com/Forums/Topic457395-338-1.aspx

Yeah, the CTEs were just a sample. There are a number of ways to accomplish this. The best choice will depend on the rest of the code it's...

Rob Goddard (4/15/2008)

Ouch, although I think that is almost...

You can use multiple CTEs if they are separated with commas. The stuff about Union, et al, is for recursive CTEs or multiple queries in one definition. Slightly...

If you have a numbers table, it's easy enough:

;with Months (Month) as

(select number

from dbo.Numbers

where number between 1 and 12),

Days (Day) as

(select number

from dbo.Numbers

where number between 1 and 31)

select Month,...

Because of the leap year subtraction problem, it won't work if one of the dates is before, and one is after, 29 Feb in a leap year, and the two...

Modified code:

declare @D1 datetime, @D2 datetime

select @d1 = '1/30/2000 11:59:59 pm', @d2 = '1/31/2000 12:00:01 am'

select datepart(year, @d2-@d1)-1900 as years,

datepart(month, @d2-@d1)-1 as months,

datepart(day, @d2-@d1)-1 as days,

datepart(hour, @d2-@d1) as hours,

datepart(minute, @d2-@d1)...

Only month and day need the -1. 0 = midnight, so hours, minutes, seconds, etc., don't need that. Years already has a -1900 (because that's 0 in datetime).

Try...

Yeah. It's not precisely a rounding error. It's a "1 Jan" does not equal 0 error. Needs -1 on the month and day columns because of that.