Viewing 15 posts - 31,531 through 31,545 (of 59,101 total)
Steve updated the explanation with the lessons learned from this thread for me yesterday.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 4:43 am
No offense taken. The XML method will take pretty much anything that you can throw at it. You just have to remember about entitization of characters. Hmmmm......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 4:37 am
Interesting conclusions. I wonder why it runs just fine on a box with only 500 MB? I'll load it back up tonight after work and take a look...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 4:31 am
Toby Harman (1/2/2012)
Anything which takes that option away from developers is a good thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 10:00 pm
J Livingston SQL (1/2/2012)
I am not surprised that you cannot replicate....I have used quirky update on several db's , all without errors...and the purpose behind this was to build...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 9:44 pm
Gianluca Sartori (1/2/2012)
There's nothing wrong with COALESCE, it's the assignment in the SELECT list that makes the code unreliable.Here's a couple of articles on the subject:
http://www.sqlmag.com/article/tsql3/row-concatenation-solutions-aren-t-all-equal
http://www.simple-talk.com/sql/t-sql-programming/concatenating-row-values-in-transact-sql/
Whup! Be careful there,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 5:37 pm
The article sounded a bit like a rant...
... I only wish I'd thought of it first! 🙂
Well said, Phil.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 3:46 pm
I've not read the whole bill, yet, but my initial impression is that it's not trying to suppress "free speech". My impression is that it's trying to suppress copywrite...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 3:10 pm
rajugnt (1/2/2012)
i need all columns in parent table and primary key as well as a foreign key AND DATATYPE,LENGTN sql 2008
This is report for one...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 2:51 pm
I couldn't get it to fail on two different boxes.
Box 1 is a 9 year old desktop w/single 32 bit CPU, 1GB ram, running 2k5 Dev Edition and Windows XP.
Box...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 1:55 pm
DBA Rafi (1/1/2012)
I am encouraging people here to have a separate team for SQL Server.
Can you please...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2012 at 12:30 pm
Tom Brown (12/31/2011)
Keep 'em coming. I need...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2012 at 7:35 am
manoj0134 (12/30/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2011 at 8:58 am
Michael Valentine Jones (12/30/2011)
Jeff Moden (12/30/2011)
...
And, yeah... there's nothing wrong with having a surrogate key as the PK and a natural key as an AK. 😉
Especially when the value...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2011 at 8:07 am
SQL Kiwi (12/30/2011)
Jeff Moden (12/30/2011)
SQL Kiwi (12/30/2011)
drew.allen (12/30/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2011 at 8:01 am
Viewing 15 posts - 31,531 through 31,545 (of 59,101 total)