Your join is multiplying the number of rows in the target table.

Try this:

CREATE TABLE #T1 (

ID INT IDENTITY PRIMARY KEY,

Col1 CHAR(1));

CREATE TABLE #T2 (

ID INT IDENTITY PRIMARY KEY,

T1ID INT,

ColA CHAR(1));

INSERT...

Yes, it's slower. That's because of the extra checks for word-breaks on variable delimiters.

If that's Excel, which is what it looks like, Offset isn't something that translates directly to T-SQL.

I "Report"ed it as plagiarism, so it's no surprise...

That would work. Do it in a temp table instead of the real table, and query the temp table. That way, you don't mess up the database.

Take a look at "SUM" in Books Online (or on MSDN). T-SQL can aggregate data with functions like Sum, Max, Min, Avg, and so on.

It looks to me like you have what you need in order to write a query. What's your question?

First you need to identify the prior n rows for each set (dog, cat, etc.) for each entry. That can be done by using row_number and partitioning by the...

Here's a Title Case script I set up that avoids UDF overhead. It assumes you have a Numbers table. You can use the CTE from Jeff's script if...

I still think the most important resolution one can make is to enjoy the new year more than the last.

Then work out ways to do so. You can always...

Event notification works. I use a server-side trace for login events to get the same sort of data, mainly just because I've been doing that for eons at this...

Not really. I'd pretty much just be poking around and talking to my network people at this point.

I generally have login triggers use a sysadmin account. If you don't, and the trigger ends up blocking you from logging in, it's gets really messy really fast.

Do you know what parameters are?

Do you know what a...

It depends.

Do you want any parameters? Perhaps something for the Where clause. That would be pretty normal for a stored procedure.