At my last job, we had a SAN and put the TEMPDB on it. It worked just fine.

Main thing to remember....SQL Server will now have a dependancy on the SAN....

You could try:

(CONVERT(VARCHAR(10),X.CreatedWhen,101) LIKE '2/8/2007'))

if the date is mm/dd/yyyy

or

(CONVERT(VARCHAR(10),X.CreatedWhen,103) LIKE '2/8/2007'))

if the date is dd/mm/yyyy

but personally, I would do:

(CONVERT(VARCHAR(10),X.CreatedWhen,112) LIKE '20070208'))

-SQLBill

To add onto what Lynn said....what date is 2/8/2007? Is it Febuary 8, 2007 or 2 August 2007? How is SQL Server supposed to know?

Either use the yyyymmdd...

I think I would keep the indentity column, create a function that takes the value in the identity column and converts it to what you want, and lastly create a...

And after talking to your boss, the email goes

Boss,

Per our discussion, I am willing to install product X (or whatever was asked). Please keep in mind that, based on...

One BIG problem.

You state: I have an itentity column that I'd like to convert the value to a varchar

This is from the Books OnLine (BOL):

IDENTITY

Indicates that the new column...

Current Role: Permanent Hire SQL Server DBA

Time at Current Job: Less than 1 year (I just moved to Arizona, US and am in a new job).

Aspirations: To win the lottery...

If you go with option #2, keep the following in mind:

1. When you convert CMRGDT to DATETIME it will have the default time of 00:00:00.

SELECT CONVERT(DATETIME, drv.CMRGDT)

FROM (SELECT...

EM,

Don't take too much offense...I was only trying to point out your comment that "SQL 2005 is a great improment over SQL 2005". How can SQL 2005 be better than...

I'm not sure I follow you. There is a set of forums for SQL Server 7 & 2000 and a set of forums for SQL Server 2005. Yes, sometimes...

the first week of 2010 is a two day week (Friday, Jan 1 and saturday, Jan 2). So, yes there are 53 weeks in 2010.

-SQLBill

I think I understand the problem now. You think you are working with DATES and you aren't. Those aren't DATETIME datatypes. You are working with INTEGERS. ...

Why do you expect to get 2 back? If you run just this:

SELECT convert(int, convert(varchar(10), getdate() - 2, 112))

you get: 20070211

and there is only ONE row that is greater than...

I'll back up the rest. You are comparing apples and oranges, as the saying goes. Both are fruits, but they aren't the same thing. Both CMRGDT and...

Don't use COUNT(*). Replace the * with your datetime column. The other thing is, what datatype is CMRGDT? Is is actually datetime?

-SQLBill