Viewing 15 posts - 40,891 through 40,905 (of 59,069 total)
ezlikesundaymorning-573799 (11/24/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 11:15 am
Interesting and thoughtful editorial you wrote there, Mr. McGehee. I'd like to add a 3rd category instead of just the Giver or Taker catgories... Receiver. It seems like...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:34 am
I have to admit that when I read the following, I thought that Seth had simply lost his mind...
My quick resolution in this situation is to:
1. Remove the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2009 at 5:41 pm
To produce a random order. It's an old trick.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2009 at 10:43 am
Mitesh Oswal (11/29/2009)
Hi what abt this ?
--===== Create and populate a test table
IF OBJECT_ID('TempDB..#TestTable','U') IS NOT NULL ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2009 at 5:23 am
Thanks for the update and the code to create the data... now all we need to do is come up with an answer for this. Good problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 11:10 pm
I believe I'd contact the people who made the DB based software and get them to fix the problem. You could actually be voiding a warranty if you try...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 9:43 pm
It sounds to me like you've gone through an upgrade process and TempDB now has a different collation that the database you're working with. It's a real PITA to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 9:33 pm
Thanks for the feedback, Shilpa.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 9:21 pm
Heh... wilst I was pondering the situation, I see Bru snuck one in on me. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 9:18 pm
Also, I see you're brand new here. Take a look at the first link in my signature below. It helps you and us, a lot.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 9:17 pm
Can the following happen? If so, what do you actually want displayed?
id | record_id| date_changed | old_state | new_state |
1 | 1 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 9:16 pm
This should get you started...
WITH
cteRandomlyNumber AS
(
SELECT PersonID,
CoID,
RowNum = ROW_NUMBER() OVER (PARTITION BY...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 8:49 pm
Ummmm.... I haven't used them in SQL Server but wouldn't synonymns do the trick here?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 8:36 pm
If you forget to put gas in the boat, "RBAR" (Row-By-Agonizing-Row) may actually mean something.... heh... Oar Not... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 8:34 pm
Viewing 15 posts - 40,891 through 40,905 (of 59,069 total)