Shiv (2/21/2008)

---

Ok,

I have given that direction as parameter bcos i want use it like a condition there. That's not problem I can just keep 'queryout' there directly instead of direction...

Matt Miller (2/21/2008)

---

Again - being tentative here. My understanding is that "out" is only to be used when the first argument is a view or table. Anything T-SQL...

Heh... sure you did... you learned that there's more than one way and that one of the ways will be easy. 😀

I understand... if "every code change can be acceptable", then consider implementing that which is found at the following URL:

http://sqlserver2000.databases.aspfaq.com/why-should-i-consider-using-an-auxiliary-calendar-table.html

What is the exact wording of the error?

Yeah... it's a simple "Name/Value" table that can easily resolved using various high performance methods (none of which require a CLR) including simple cross-tabs. What kind of an error...

Simong,

Here's a simple "splitter" to normalize the CSV entries you have so you do a join instead of a "LIKE"...

--===== Create a table to hold user ids and a word...

Good thoughts, Terry......

Either way, looks like a correlated sub-query is going to be involved which is why Matt suspects the performance is going to suck a bit...

Here's another way (output could be...

Ya gotta make one...

--===== Create and populate the Tally table on the fly

SELECT TOP 11000 --equates to more than 30 years of dates

...

Nicely done, Lynn!

Man, I can't wait to get off this cold medication... I totally missed that...

Dang... I was loading up the double-barreled pork-chop sling-shot. 😉

I'm with Michaeal... I'm not sure anyone would have entries for, say, 1754, or even 1901 and certainly not for the year 2100 or 2200. What I'm trying to...

No... if you don't specify the database or the server, it assumes the "default" database for the user (which has been nicely overcome by the 3 part naming convention) and...