There is no need for dynamic SQL.

Insert the values in @IDList into a table, and then just do this:

SELECT * FROM TW_Transaction WHERE pkTransactionID IN (select ID from #temp)

You can...

I don’t think a permanent lockout is practical when it comes to SQL Server service accounts. It would be dirt simple for someone to do a denial of service...

It depends on what you really mean by Julian date. There are a couple of common meanings that have nothing to do with each other (refer to link below).

More...

What I don’t understand is how you would make any change, since you can’t change the schema or application?

SQL Server locks are not meant to be used as application row...

You will have to use dynamic SQL.

You could use backup and restore.

PFlorenzano-641896 (11/4/2010)

---

Thanks guys.

Yes the tud.value column is a varchar column, but further down in the query within the WHERE clause, the tud.userdatacode = 'PRX IVPB EndDTM' criteria is...

You must also still have the database compatibility level set to 2005, because this line of code would give an error in 2008:

FROM CV3Order o (nolock)

The correct syntax in 2008...

You could store the Dividend and Divisor as individual columns. Probably be a bit painful to work with.

Example:

Update MyTable

set

Dividend = 1,

Divisor = 3

where

<condition>

I don't understand why you want to store this information is a table, since the length of time changes from one day to the next and the data will be...

You need to give a better definition of your rules for calculating "years".

Do you really mean number of full years based on hire or rehire date? If that is...

I was going to suggest this solution:

Select

*

from

table_with_one_billion_rows

cross join

table_with_one_billion_rows

It’s interesting that you brought up transaction isolation level.

There is a nasty gotcha to watch out for if your application is doing connection pooling: The transaction isolation level does not...

Jeff Moden (11/3/2010)

---

I believe everyone is missing the requirements a bit on this one. The op wants to know how many months are in each year of a...

What you are missing is the following from SQL Server Books Online under the SET DATEFIRST topic:

ValueFirst day of the week is

1Monday

2Tuesday

3Wednesday

4Thursday

5Friday

6Saturday

7Sunday

When you have @@DATEFIRST = 1, the...