Viewing 15 posts - 28,006 through 28,020 (of 59,101 total)
rmechaber (12/3/2012)
I use this VBS script (it works, please don't tell me that's old school) I wrote to do exactly that.
It IS "old school"... and I love it 'cause I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2012 at 7:50 am
fname lname-1111520 (12/2/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2012 at 6:15 am
kapil_kk (12/3/2012)
Jeff is right...I dont have any knowledge of Tally Table..
Please see the following article. A Tally Table (or Numbers table, as some call it) is a simple table...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2012 at 5:58 am
Jason-299789 (12/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2012 at 5:49 am
You could use either CASE or ISNULL or COALESCE for such a thing. I used ISNULL in the following example. Also, you would do better for yourself if...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2012 at 5:44 am
In SQLServer 2008, there is a DATEPART called ISOWK. I've not used it because I don't work with week numbers but that should fill the bill for you.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2012 at 3:17 pm
Chriz L. (12/1/2012)
The answer is to create relational tables as following, instead of having one...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2012 at 8:40 am
Richard Fryar (12/1/2012)
Or, instead of writing your own backup and maintenance scripts, you could use the ones by Ola Hallengren.Highly recommended.
Do you use it, Richard?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2012 at 8:04 am
SQL Kiwi (12/1/2012)
The set-based iteration (WHILE loop) solution may well be best here, but the following is a recursive CTE solution that appears to work correctly:
All "seeks", too! Nicely...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2012 at 7:23 am
Evil Kraig F (11/28/2012)
--am trying to write a query against a table of invoices, returning all relevant rows for a particular InvoiceId. Heres...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2012 at 7:45 pm
Looking at the data that you've included, Craig, I'm thinking that maybe I didn't have it working at all when it comes to "disconnected" data like you did with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2012 at 1:18 pm
Heh... dammit. I had it working and made a final tweek to the code. Now I have to go back and figure out what the heck I changed....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2012 at 12:57 pm
Post withdrawn. I made a mistake in the code somewhere. I'll post it as a new post if I can figure out what the heck I did wrong...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2012 at 12:27 pm
Alan.B (11/28/2012)
Evil Kraig F (11/28/2012)
This is NOT pretty, but it IS functional.
I am trying to understand why went with a loop vs a set-based approach. I posted a more set...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2012 at 9:43 am
gloing40 (11/30/2012)
The website wholesale for many kinds of fashion shoes, like the nike, jordan, prada, also including the shirts, bags, hat and the decorations.
WE ACCEPT CREDIT CARD /WESTERN...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2012 at 12:01 am
Viewing 15 posts - 28,006 through 28,020 (of 59,101 total)