Not sure what to do about that one. I haven't had an installation go bad on me in that way.

Tom Garth (5/9/2008)

---

GSquared (5/9/2008)

---

I would consider a question about the Resource database valid in an interview (or QotD). In the interview environment, if asked "What are the system databases...

I can't see a boycott being effective in this regard.

Insofar as upgrading to SQL 2008 goes, I see a bunch of features in Enterprise that would be very, very useful...

I write because I like to communicate in all its myriad forms. (I talk too much, write too much, heck, since I spent a summer with some Italians, I...

You just failed your own proof of observation of language. 🙂

Thus, per your own argument, you need to stop stop using case sensitivity. 🙂

troyehall (5/10/2008)

---

Phil Factor,

Being able to easily spot the difference between getElementById() from getElementByID() while skimming through code is not a matter of being clever. In fact, I expressly stated that...

Actually, in the right (wrong) circumstances, Cross Apply can be worse than a regular correlated sub-query. It depends on...

Are you literally running exactly the same script in each database? They all have the same tables and columns to clean up, etc?

If so, then you could turn it...

Vijaya Krishna (2/24/2008)

---

Hi,

if you are very sure about the values that you can have for that columns is less than 3 then you can go ahead with bit data type....

Regardless of cause, that's the error you get for deadlocks.

Is there any reason that this has to be done in SQL? Most of the time, pivoting data works better in various front-end applications. Reporting Services, Excel, Access,...

The only way to do exactly what you're asking is dynamic SQL. That opens up all kinds of serious security and other issues. Might want to reconsider the...

Another way to join the tables together to get this is:

select *

from WData

inner join tempProjtable

on WData.proj_ID like tempprojtable.proj_id + '%'

where tempprojtable.proj_start_dt is not null

and tempprojtable.proj_end_dt is not null

Then you just...

The only way I can think of to do this more efficiently would be to select the max(sd.DateID) for each dt.DateID in one query, then join that to the sparse...

Is there a particular proc that's causing the problem? Or a couple of specific ones?