I would be looking at using a storage array for that size. However Before I could comment on architecture I would need to know what sort of data it...

sp_spaceused. Shows you how much space is taken up by your indexes.

Tara, Just because there is an index on a column does not mean it will be used. It depends upon the query plan and the selectivity of the index...

Sounds like the query timeout value should be increased. What other activity is going on on the server during the time the SP is executed by the application? Queries that...

you are correct, fat finger error on my part. I meant to type:

declare @myDate datetime

select into holds locks on various systems tables until the query completes. If the query is a long drawn out one it could result in other processes timing out like...

it can be used pretty much directly if the like is of the form "column like 'begins with%'"

if its like this: "column like '%something%'" then it can't be...

that would be equivalent to '7/9/1998'. It looks okay to me, perhaps a localization setting. I give up, except perhaps try this:

declare @myDate

set @myDate = '7/9/1998 12:00:00 AM'

select @myDate

tell...

do you have any schedule tasks running, perhaps something using select into?

are you backing up the transaction log? If not, set the recovery mode to simple. If it is just in your QA environment you may not need to be...

hopefully #STARTDATE# contains a valid character representation of a date and/or time. IIRC Access requires the date to be bracketed by '#', SQL Server does not.

64 bit versions of Windows OS can handle 32GB

In the vast majority of cases properly normalized database will always perform better than un-normalized database. Yes, it is true that in special circumstances a certain amount of de-normalization *can*...

use a global temp table (insert into ##temp .. )

Put those audit columns in a separate table. Each row would have a date_time, a userID and a type (create, updated etc.) and a column (ID probably) to link back...