Viewing 15 posts - 54,556 through 54,570 (of 59,072 total)
mrpolecat (10/17/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 11:46 pm
Max Yasnytskyy (10/17/2007)
I have found an interesintg function in msdb, seems like it is working much better ...
Ummm... this is an SQL Server 7/2000 forum... wanna tell us how well...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 11:42 pm
Depends... index scans can be worse than a table scan because even after the index scan, it still has to get the data.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 11:22 pm
The EXISTS with the sub-query, probably a correlated one at that, needs to be replaced with a join.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 11:19 pm
So... you've never seen recursive CTE's? You just don't need to use a CLR for such a thing... the tools are in T-SQL... you just need to learn to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 5:07 pm
mdiaz (10/17/2007)
A real quick and easy way to make a split funciton, that returns records as a table.Imagine writing that in TSQL???
Split "functions" are nothing more than RBAR... and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 4:20 pm
Derek Karpinski (10/17/2007)
I'm a DBA and a Developer... Accent on Developer.. 34...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 4:05 pm
Thanks, Noel... that's why I like this place... I learn something new everyday 🙂 I'll check out BOL on that. Thanks again.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 8:46 am
Heh... like I said, Derek... CLR's are for people who don't really know T-SQL... 😉
If you have a GUI involved, that type of formatting should be done in the GUI......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 8:36 am
Sandy (10/16/2007)
I think you both are concentrating multiple table updates
rather than Nested Update Statement,
I clearly mentioned that I have used Nested Update statement
rather than Multiple Table...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 7:45 am
Matjaz Justin (10/17/2007)
create a view and instead of update trigger on that view.lp, Matjaž
Creating the view is fine.... but it won't help you update multiple base tables with a single...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2007 at 7:41 am
This type of formatting should generally be done in a GUI...
However, it can be done in SQL Server... lookup "Cross-Tab Reports" in Books Online for a complete explanation of how...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2007 at 10:52 pm
Grant is correct... you can update only 1 table at a time... you will need two totally separate updates.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2007 at 10:39 pm
Thanks for the feedback, Jay... if you get a chance, let me know what your timings are. Would really appreciate that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2007 at 10:23 pm
Matt Miller (10/16/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2007 at 10:21 pm
Viewing 15 posts - 54,556 through 54,570 (of 59,072 total)