Viewing 15 posts - 26,176 through 26,190 (of 59,102 total)
If you mean how to view the content of what is normally the ".ldf" file, it normally takes some 3rd party software to view the logfile. There are some...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2013 at 11:08 am
Sha_ (8/17/2013)
I need...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 11:24 pm
You would need a trigger and, probably, the ORIGINAL_LOGIN() function to capture the login of the person making the direct changes.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 11:18 pm
I'm thinking that this is way too big a question for a forum.
So far as your point-in-time stuff goes, I believe you're headed in the right direction.
I think your biggest...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 11:10 pm
kapil_kk (8/17/2013)
Previously I used to use PIVOT but after reading Jeff's article I start using CROSS TAbS....
Thanks Jeff for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 10:08 pm
But I don't think this is correct way creating tables and dropping tables and selecting data twice
It's fine the way it is except for the drops at the end. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 7:57 pm
curious_sqldba (8/17/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 7:20 pm
jethrow (8/17/2013)
Another option:
SELECTname, CASEWHEN Mark1>Mark2 AND Mark1>Mark3 THEN 'Mark1'
WHEN Mark2>Mark3 THEN 'Mark2'
ELSE 'Mark3' END
FROMSample;
Welcome aboard!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 7:16 pm
TheSQLGuru (8/17/2013)
jethrow (8/17/2013)
Another option:
SELECTname, CASEWHEN Mark1>Mark2 AND Mark1>Mark3 THEN 'Mark1'
WHEN Mark2>Mark3 THEN 'Mark2'
ELSE 'Mark3' END
FROMSample;
CASE: My favorite 4-letter TSQL word!! 😎
Especially in this "case". 😛
Just so...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 7:15 pm
curious_sqldba (8/16/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 7:09 pm
sgmunson (8/16/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 7:02 pm
p.swathi4 (8/17/2013)
How to find the queries thats causing tempdb fill very often.
It's a fairly large subject so you need to ask your assistant DBA the question. In fact, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 4:38 pm
Please see the following article. Change SUM to MAX if you want to "pivot" character based data.
http://www.sqlservercentral.com/articles/T-SQL/63681/
If you prefer a coded answer to your problem, please see the first...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 4:26 pm
...but it takes participation and rational, reasonable debate, not childish exaggerated complaints and insults. We want to influence and convince, not upset and anger.
I'm thinking that needs to become...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 3:30 pm
You can't just dump any query into @Query for this. The best thing to do would be to capture the data in a table and then query that table.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2013 at 3:15 pm
Viewing 15 posts - 26,176 through 26,190 (of 59,102 total)