Viewing 15 posts - 31,201 through 31,215 (of 59,101 total)
I think his mindset is just fine, Joe. It is frequently much faster to employ such "Divide'n'Conquer" methods rather than trying to do everything in a single query. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 9:39 pm
Samuel Vella (2/8/2012)
Usually I end up with either CTE's or similar to try and make the SQL more readable.Are there any better work arounds?
Actually, the CTE method you speak of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 9:36 pm
Digs (2/11/2012)
Sir, I am an old fart working on a private project...just needed a little help !Thanks 🙂
Jeez, Digs. The 2nd Cross Tab article that Lutz pointed you to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 9:22 pm
Thanks for the test data setup code. It makes it a whole lot easier and timely for me to help.
Here's your test data and the solution. It returns...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 9:16 pm
Shamelessly borrowing from Mark's good code for test data, we can simplify both the code and the results a bit...
--===== Create the test table/data
DECLARE @t TABLE(PNumber VARCHAR(2),ReasonCode VARCHAR(2))
INSERT INTO...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 5:05 am
Even after passing Gail's "Magic Wand" over this (and you really should read her article if you haven't already), LIKE filters that begin with a wild-card will always be tough...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 4:20 am
First, get 3 envelopes... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 4:06 am
pharmboy4u (2/11/2012)
Hello,Sorry I'm not posting in a table form, I don't create them so I'm not fluent in the lingo and it would take me forever
No it wouldn't. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:57 am
Shark Energy (1/19/2012)
1) DBA Team Leader
2) Software Development Manager WITH DBA responsibility
The...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:53 am
Rob-350472 (2/8/2012)
Blah blah blah <a href=" /xxx/yy/bbb.aspx?ID=111111 "> Entity Name </a>, blah blah blah...
I'm trying to retrieve...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:49 am
kiran.rajenimbalkar (2/8/2012)
I need your help to solve this issue.
I need to tune this my SQL mentioned below,
SELECT ind.ind_cst_key,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:44 am
CELKO (2/8/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:32 am
Rowles (2/9/2012)
Is an inline table-valued function the same as a multi-statement TVF that only had one table-valued SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:22 am
About the only time I've seen this problems is when folks looked at the wrong server. Double check where the linked server is pointing to.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2012 at 3:13 am
Joy Smith San (2/10/2012)
Often times index maintenance is the culprit in this case or some kind of bulk-load process. If there are no scheduled jobs that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2012 at 6:53 pm
Viewing 15 posts - 31,201 through 31,215 (of 59,101 total)