Viewing 15 posts - 52,456 through 52,470 (of 59,072 total)
The fact that the UDF is taking longer than the embedded code is normal... there's a bit of an overhead associated with running UDF's in many cases especially when the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:51 pm
Cross post...
http://www.sqlservercentral.com/Forums/Topic457027-8-1.aspx?Update=1
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:49 pm
Why? That's as bad a double post. You're just gonna make people mad...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:48 pm
Good list, like everyone else said. Just no hair in the list...
I'd first ask them if they've actually tested their code on a 64 bit machine. I'd want...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:45 pm
How many times have you run the test? First section of the test caches the data for the second one. Try reversing the two tests and see what...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:38 pm
Good stuff, Phil... we had some critical stuff we needed to do as a batch job and, for sure, it required "SA" privs and xp_cmdShell...
I love my DBA... she...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:02 pm
Ken Gaul (2/18/2008)
Still can't see why anyone would...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 11:46 am
Although using FSO through sp_OA is a wonderful idea... it still requires "SA" privs. Not complaining or arguing... just reminding 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 11:34 am
Schnurdle (2/18/2008)
I always create the temp table first, then INSERT into it to avoid such issues.
e.g.
--Create...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 11:13 am
Sure thing, CA... thanks for asking...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
... and thanks for the kudo on formatting. I do it mostly so I can read it 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 10:49 am
What are you using to measure the times with? Typically, I'll use SET STATISTICS TIME ON... the CPU time is the actual time it took sans any display. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 10:11 am
Heh... if you don't care so much about a trigger providing a friendly error, you can always just have the table lock itself up when you create it...
CREATE TABLE YourTable...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 10:06 am
Thanks for the feedback, Julie... hmm... maybe I should publish it here, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 9:14 am
What an awesome article... I've seen quite a few on the same topic, but this one "nutshells" the whole 9 yards very nicely. It's definitely a keeper.
Thanks for...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 8:59 am
Actually, the help system in SQL Server is pretty good. Comes free with SQL Server. It's called "Books Online".
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2008 at 12:23 am
Viewing 15 posts - 52,456 through 52,470 (of 59,072 total)