Viewing 15 posts - 34,681 through 34,695 (of 59,099 total)
Gianluca Sartori (3/10/2011)
I would still wait for Jeff's reply, I might have overlooked something.
You pretty much sussed it, Gianluca. At this point, all I can do is to recommend...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 9:16 pm
Gianluca Sartori (3/10/2011)
Are you sure, Jeff?If I understand it correctly, the sort order should not matter.
No. My bad. I didn't read the requirements correctly. My apologies. :blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 9:03 pm
Patrick Cahill (3/10/2011)
I'll take this one.
I'll be happy to provide a technical review on this one, Patrick. Drop me an email, if you'd like.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 8:49 pm
Allow me to ask a question in return before I respond, please. Why are we playing musical chairs with the requirements? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 8:40 pm
M Joomun (3/10/2011)
I'd like to create an update trigger to detect changes to multiple columns. I can create a trigger to append an entire row of data to an...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 8:04 pm
Heh... everytime I see someone ask "How do I avoid logging", I want to answer "Stay out of the woods." 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:58 pm
sql_2005_fan (3/10/2011)
can we insert the error or error number into the database with an insert statement?
If I understand your question correctly, the answer is "Absolutely". And more.
Lookup Try/Catch in...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:55 pm
Maybe HASHBYTES?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:53 pm
Brilliant! This was the perfect followup to the other editorial you wrote on what acceptable data loss is and the cost of protecting data at different levels. Thanks,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:52 pm
Heh... ya just gotta love XML "Tag bloat". 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:50 pm
Chris Morris-439714 (3/7/2011)
SQLkiwi (3/4/2011)
Exciting day - just had my first Simple Talk article published:http://www.simple-talk.com/sql/learn-sql-server/understanding-and-using-parallelism-in-sql-server/
Good lord Paul, they get better and better. You have an enviable skill, like Jeff M, at...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:46 pm
Steve Jones - SSC Editor (3/9/2011)
jcrawf02 (3/9/2011)
Steve, are you aware that you're sitting on a gold mine? Your barn could power Denver!
Not sure it's a "gold" mine, but I need...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:37 pm
ALZDBA (3/10/2011)
Brandie Tarvin (3/10/2011)
GilaMonster (3/10/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:27 pm
Stefan Krzywicki (3/10/2011)
GSquared (3/10/2011)
Brandie Tarvin (3/10/2011)
Two years ago, we implemented a new process that uses the acronym "RI". I've been working on that process ever...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:22 pm
dba.varun.in (3/10/2011)
I was little bit busy for past few days.I found; u said not to use this query because it will raise issues when data is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2011 at 7:18 pm
Viewing 15 posts - 34,681 through 34,695 (of 59,099 total)