You're 100% correct.

I actually thought that was what I said.

You get all the functionality I've talked about without any of the server components. The server adds in all the Team activities like Work Items, Team builds, shared documents, etc.....

Now we're both learning. I never noticed that before either.

Thank you.

Yeah, I've noticed the same thing. When a line of code extends past the edge of the screen it shoots ALL the text out there too. It does make things...

I agree. Best measure is either to use the STATISTICS TIME or Profiler.

Interesting point, don't use both because you'll get confused. We found that there are small differences between the...

What you usually see in the STATISTICS is the time on the server. It doesn't include time to move the data to your machine or time to display the graphics....

2005 uses SMO.

Several people have commented that they use NOLOCk or setting the isolation level because they're in a read only environment. Have any of them considered setting their database to read...

Just an idea. Buy vs. Build always has trade-offs in either direction.

There are other text indexing products out there. Shop around.

Is there an INNER JOIN involved to arrive at the data being selected. Join criteria is evaluated prior to the WHERE clause and you can sometimes move things from the...

If you're going for cheap, then you just need to set up full text indexing that comes with SQL Server 2005. Otherwise, I found this information on the Google site:

Are you kidding? Set logic is bloody difficult. I have a hard time wrapping my brain around it almost daily. I just know that I have to take the approach...

Just to start with, no:

SELECT * FROM ... LIKE 'Asp.net%'

will only find data that is starts with Asp.net. If you want to search in the middle of a string you...

It's not so much the database that's set oriented, although that's a big part of the issue. It's that TSQL is set oriented. Especially 2005 with common table expressions &...

I agree with Ms. Shaw. Who wouldn't. You may also want to consider using a unique constraint:

ALTER TABLE [x]

ADD CONSTRAINT [y]

UNIQUE NONCLUSTERED ([emailaddress],[password]) ON [PRIMARY]

Then you get the index suggested...