Viewing 15 posts - 44,281 through 44,295 (of 59,097 total)
How very strange... your screen shot of my most is as I saw it when I posted it. It's the new code window with colorized code and the whole...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2009 at 7:10 pm
The purple "windows" that your code is in on this thread is the "old" style and it worked well especially for people to copy from. The new code style...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2009 at 6:31 am
Heh... somebody please tell me how you're managing to use the old code windows... I really don't like the new ones because of the errors they currently have in them....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 11:52 pm
leo4Ever (4/8/2009)
The final datetime value obtained from timestamp being...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 11:45 pm
I believe you've successfully converted the Cross Join to an Inner Join with the criteria so, I think this will do the same thing...
[font="Courier New"]Select t1.UserId, t2.StatusDate LogoutDate, Min(DateDiff(n, t1.StatusDate,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 4:43 pm
Florian Reischl (4/8/2009)
It's another concept than Lowell's but might also help in some cases. Keep in mind, if possible use CONVERT due to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 4:37 pm
Lowell (4/8/2009)
one format, the ISO one, is really handy for me, as I have to do a lot of that conversions;
ISO8601 (XML) ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 4:33 pm
Ells (4/8/2009)
exec sp_spaceused
This then returns
...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 2:53 pm
andrewd.smith (4/8/2009)
Obviously, the actual value of the resulting datetime column is meaningless.
At the risk of rattling the rubble, that statement is 100% spot on. The original developer made a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 2:46 pm
Ummm.... no.... to be as safe as possible with this method, you MUST include a FROM clause in the update and it must use a TabLockX and index hint that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2009 at 10:27 am
Way to go, Roy! I had a similar experience where I'd interviewed person after person after person for a Sr. Developer position. They all had degrees and certs...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2009 at 11:56 pm
Bob Hovious (4/7/2009)
... this is the kind of newbie I like to see...
He is a trophy. Stuff him and mount him on the wall. You could tell from...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2009 at 10:53 pm
AFIFM (4/7/2009)
Is this domain type??
No it is not. One of the legacy applications (A) uses 'Access_Level' as VARCHAR which only uses "1", "2", "3",....."8". The second application (B) uses the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2009 at 10:45 pm
Ok... here we go. I copied your very fine test data code and added the answer to it...
[font="Courier New"]--Post to SQL Server Central
--===== If the test table already exists,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2009 at 9:19 pm
Maxim Picard (3/27/2009)
Cross Tabs and Pivots, Part 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2009 at 8:30 pm
Viewing 15 posts - 44,281 through 44,295 (of 59,097 total)