Viewing 15 posts - 53,101 through 53,115 (of 59,098 total)
If UDFs can be non-deterministic then the optimiser has to assume that if you wrote a query which implicitly calls a UDF 10,000 times, then you actually want it to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 10:13 pm
Hey Loner... how did your recent interview go?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 8:31 pm
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 8:27 pm
In other words, you can delete the parent records and the child records will automatically be deleted.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 8:22 pm
I guess we also need to know the number of rows in the two tables, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 8:20 pm
Heh... use the GRID mode instead of the TEXT mode...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 5:35 pm
Topher, please post the command you want to execute on all of the databases and what you'd like the output to look like.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 5:26 pm
In SQL Server 2000, there is no "Modified Date" on a stored procedure. So I always drop the procedure and recreate it so the Create Date shows the latest...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 4:49 pm
Heh... C'mon Phil... 😛 this is a 7/2k Forum... there is no VARCHAR(MAX).
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 4:35 pm
Thanks Phil...
Folks, I don't understand why anyone needs VBS for this... why not just do it directly in T-SQL? Heh... everyone gripes about me coming down hard on cursors,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 2:50 pm
I'm thinking this is for an SQL class... with that in mind, now that I've given you the distance function, you must try first... also, see the following... it will...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 1:07 pm
Ananth,
Books Online (comes free with SQL Server) also has a wealth of knowledge on how indexes work and how to build them...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 9:42 am
Heh... ten to one says monthly, weekly, or even daily transaction databases... folks do that a lot especially in the telephone business (Call detail records saved in monthly databases based...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 9:34 am
It would appear from things like "[Expr1002]=Convert([pt3].[STORE_KEY]) " found in the execution plan that 1 or 2 things may really be causing the performance problems...
The first thing is that that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 9:27 am
For the distance formula, please see your other post at the following URL...
http://www.sqlservercentral.com/Forums/Topic439224-338-1.aspx
... that should get you started...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 9:10 am
Viewing 15 posts - 53,101 through 53,115 (of 59,098 total)