Viewing 15 posts - 34,276 through 34,290 (of 59,099 total)
Grreat article, Craig. If people actually study what you wrote, they'll be able to spot and separate the "dream jobs" from the "jobs for Bob" from the "SQL God"...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2011 at 12:18 am
ranjodh_makkar (4/9/2011)
Also about function let me write a quick template to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 10:50 pm
Deeps123 (4/12/2011)
Hi Guys,i got it working..............
Just rank the records. and then use Pivot operator in SQL 2005 to move the column values into single row.
Cheeers...........
... until you have more columns...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 10:21 pm
Kiara (4/13/2011)
CirquedeSQLeil (4/13/2011)
GilaMonster (4/13/2011)
CirquedeSQLeil (4/13/2011)
How many of you would walk out on a job without completing it (as a contractor/consultant) - if you were getting paid?
Never (short of illegal practices...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 10:13 pm
CirquedeSQLeil (4/13/2011)
GilaMonster (4/13/2011)
CirquedeSQLeil (4/13/2011)
Leave the contract early without notice and prior to completing the stated work.What does his contract require? Solo or contracting house?
Solo contract and it required him to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 10:09 pm
Roy Ernest (4/12/2011)
You all are making me looking foolish because I am laughing when going through a SQL Forum. I am getting some strange looks. 😀
BWAA-HAAA!!!! Is THAT really...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 9:55 pm
It looks like the SQLCLRs are getting beat up a bit by straight T-SQL. I believe there may be an optimization on the DISTINCT XML example that we can...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 8:37 am
Ninja's_RGR'us (4/13/2011)
Brandie Tarvin (4/13/2011)
Does the order really matter?
It actually could. If it fails to finish in the allowed time I need to be able to start back where it...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 8:28 am
Ninja's_RGR'us (4/12/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2011 at 8:17 am
Ninja's_RGR'us (4/12/2011)
All I know for sure at this point is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2011 at 1:15 pm
MyDoggieJessie (4/11/2011)
In poorly designed tables that have 400+ columns (but luckily do have a unique guid as a PK), wouldn't it just be easier to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2011 at 12:22 pm
Sorry... I lost track of this one.
Is this still a problem? If so, I've run out of ideas based on the current information provided. I believe we need...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2011 at 12:20 pm
UMG Developer (4/11/2011)
2nd note to self... find the person who made the change without discussing it and invite him/her out for a high velocity pork chop dinner.
I've seen mention of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2011 at 12:16 pm
Nadrek (4/11/2011)
No, I'm not trolling; I'm advertising your article! The full context was:
-- Quirky update!!! BEWARE!!! Do not use this for critical things!
-- BEFORE USING, read http://www.sqlservercentral.com/articles/T-SQL/68467/
"Do not...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2011 at 12:01 pm
I causually looked at your code and it appears to be correct. What is the error that is being thrown?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2011 at 11:50 am
Viewing 15 posts - 34,276 through 34,290 (of 59,099 total)