Heh... Nope! Doesn't make a bit of sense... all the rows you posted are identical and there is no question column.

Please see the link in my signature before you...

rbarryyoung (7/9/2008)

---

You gotta love English. I almost started to reply with "But you didn't include the States' Capitals." Then I realized that you didn't mean the capital capitals...

You might want to double check... CROSS APPLY is a fancy name for "Correlated Subquery" and can have all the same problems with performance.

I believe you're thinking of blocking.... deadlocks do not resolve themselves in a nice manner... there is always a "victim" that get's rolled back... always.

Heh... if more than one user has to use it even just once, it's not "one time"... 😀

ggraber (7/9/2008)

---

Try this:

DECLARE @Table TABLE

( BatchID INT

,TransactionID INT

)

INSERT INTO @Table

SELECT 101, 1

UNION ALL...

No problem and thanks for the feedback, Phil... I've made similar mistakes... just wanted to be sure...:)

That would be a problem... only way I can see to do it...

I'm with Gail... but a bit more stringent on the subject. If you have any deadlocks, something is wrong in the code somewhere and you need to fix it....

There are three reasons I can see for it... and I use neither because of what Grant said... would probably be a bad design...

Someone already said to build "user defined...

Ummm... the best thing to do would be to create a stored proc and send the users instructions on how to run it with the correct parameters.

Nah... not a problem Kent... I just had more coffee than you 😛

It's just a way of showing that it actually works... the temporary table is just for demonstration purposes....

While COLLATE will take care of case sensitivity and the like, trailing white space is a huge PITA... I think anyone that depends on trailing white space is asking for...

You should still take the time to read the article about Tally tables whose link I posted, but here's the solution to the problem you posted. Also, take a...