Viewing 15 posts - 31 through 45 (of 363 total)
Yes, in my exper. also... you need to...
select * from dbo.MyFn('value1', NULL) --- at the very least ![]()
Oh well, SQL's 1st time with UDFs,...
Once you understand the BITs, all the pieces come together ![]()
March 8, 2004 at 11:21 am
Off the top, I think both SPs and UDF can have default values, but UDFs require at least a NULL in each params.
Once you understand the BITs, all the pieces come together ![]()
March 8, 2004 at 10:47 am
You can always insert into a #Temp table using either OpenQuery or Server.DB.dbo.sp_Execute ...,
then JOIN the #Temp table. This may be better for the optimizer to deal with anyway.
Once you understand the BITs, all the pieces come together ![]()
March 8, 2004 at 10:34 am
Seems 4 part UDF naming conventions are NOT supported in SQL2K.
see http://support.microsoft.com/default.aspx?scid=kb;en-us;Q319138
Once you understand the BITs, all the pieces come together ![]()
March 8, 2004 at 9:27 am
Interesting...
It doesn't work with a param unless you use dynamic SQL, but here's something to start with...
select * from openquery(Server, 'Select * From db.dbo.fnMyFunctionName()' ) T1
Once you understand the BITs, all the pieces come together ![]()
March 8, 2004 at 8:56 am
Thanks Mith
I'm kind of interested in actual timed results with a number of records that would realy make a difference... maybe 500K rows down to a couple or few.
And... what...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 4:46 pm
SQL Server "Profiler" is the generic answer to your generic question. I'd much rather see you target very specific areas of performance concerns... particular query, particular procedure, application connection time, application...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 4:03 pm
I understand ![]()
I know you can "edit" your post. Noel, can you try to "delete" 2 of the 3 posts? or maybe at least...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:50 pm
Sagar, check out some of the "script" resources on this site at http://www.sqlservercentral.com/scripts/categories.asp?groupname=SQL%20Server%207.0/2000&groupid=1 either Misc. or TSQL aids, search for "pivot" etc.
Please post back to this thread if (or not)...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:47 pm
Ok Noel, we get the point... what happened a "triple-click" ? ![]()
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:42 pm
Hitek, a few questions...
1. Make sure I understand...
1, 40, 'M', 'Bob', 'Mr', ''
1, 40, 'M', 'John', 'Mr', ''
1, 40, 'F', 'Betty', 'Mrs', ''
1, 40, 'F', 'Jane', 'Mrs', ''
Becomes
1, 40, 'M',...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:39 pm
Interesting point Mith...
Can you post what the estimated execution plan shows when using Jack's syntax? Does it show anything? because OPENQUERY just shows "Remote Scan" which is useless to...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:21 pm
I think what srankin is saying, is that if you have a SELECT that JOINS and aggregates your data, and then you create a VIEW based on that SELECT (less the WHERE clause...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:12 pm
I just like posting into threads with Frank
.
I did not mean Rob specifically either, at least Rob posted that "a solution...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 3:00 pm
Also...
Do NOT use this in a loop or Scalar UDF. This method adds overhead, and should be used as a "last resort". Do not use this method just for...
Once you understand the BITs, all the pieces come together ![]()
March 3, 2004 at 2:51 pm
Viewing 15 posts - 31 through 45 (of 363 total)