Viewing 15 posts - 30,061 through 30,075 (of 59,101 total)
Now that you've been shown the principle of how it works, how about showing us your try?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2012 at 9:13 am
best_yunus (5/12/2012)
Can we do point in time recovery in Bulk loged recovery model?If yes then how?
Yes but only if there were no minimally logged transactions in the final log file...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2012 at 12:15 am
Perhaps a bit of a join tutorial is in order.
http://www.w3schools.com/sql/sql_join.asp
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2012 at 12:12 am
Ummmm.... if the first character is always a backslash (and I think it will be), you could really shorten up the code by starting the charindex search at character #2....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 11:50 pm
MaverickMan (4/30/2012)
Performance is not the need for our problem so it will work with any of the solutions presented above.
BWAAA-HAAAA!!!! So! Did you pick the slowest solution? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 11:42 pm
selvakumar.sms (5/12/2012)
please explain me where to use right outer join and left outer join.
i referred many articles but i couldn't get clear...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 11:02 pm
Good article, Steve. I believe that you've hit the nail on the head. So many managers think that Hours worked = Hours wisely spent = Good lines of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 10:55 pm
To the best of my knowledge, no such tool exists. Certainly, not an accurate one. Even the actual execution plan is frequently wrong when comparing things such as...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 10:43 pm
nitin_456 (5/12/2012)
Thanks for the reply !!But there can be thousand of Comid , is there any other way to to do this...
Understood on there being thousands of Comids...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 10:21 pm
Heh... I took too long and CC beat me.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 10:09 pm
Ya just gotta love non-ansi joins for correlation. 😉
SELECT tyn.IdNum,ca1.Pnum,ca1.YN,ca2.Value
FROM #TempYesNo tyn
INNER JOIN #TempValue tv
ON tyn.IdNum = tv.IdNum
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 10:07 pm
erics44 (5/12/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 9:52 pm
Lynn Pettis (5/12/2012)
Jeff Moden (5/12/2012)
Elliott Whitlow (5/12/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 9:41 pm
I've not checked it for performance but it does avoid a full cross join and it does work.
WITH
cteUnPivot AS
(
SELECT ex.[Drawn Date], ca.Number
FROM dbo.Example ex
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 9:14 pm
Elliott Whitlow (5/12/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2012 at 2:05 pm
Viewing 15 posts - 30,061 through 30,075 (of 59,101 total)