Viewing 15 posts - 1,336 through 1,350 (of 1,825 total)
Then a lot more detail will be required to help.
Please post as per the link in my sig
October 20, 2009 at 8:05 am
Scalar udf's yes, inline tables udf are fine....
http://sqlblogcasts.com/blogs/sqlandthelike/archive/2009/10/15/udf-overhead-a-simple-example.aspx
October 20, 2009 at 8:03 am
Sound like an out of data statistics and /or parameter sniffing.
Use update statistics first off.
Then Google for parameter sniffing.
If that doesent sort it , please post as per the links...
October 20, 2009 at 7:26 am
Left join would be better...
SELECT origin_latitude, origin_longitude, COUNT(*) AS Structures
FROM towergrid_reference_natowers
left join towergrid_reference_clli
...
October 20, 2009 at 7:19 am
you need "datepart(dw,"
Check BOL for more details
October 20, 2009 at 7:09 am
A View should be
Create View JobPostingView
as
SELECT Job_Posting.Transaction_Date,
...
October 20, 2009 at 6:01 am
Just on this subject.....
October 20, 2009 at 5:21 am
Im going to duck out of this thread , what you are describing is a set of circumstances that are alien to me.
You may as well want a different value...
October 20, 2009 at 5:02 am
janine.rawnsley (10/20/2009)
I think this is shoddy tbh.. surprised at MS implementing what seems a half-working TRY..CATCH solution.
Personally , i think its pretty shoddy design that you are trying to execute...
October 20, 2009 at 4:01 am
janine.rawnsley (10/20/2009)
The...
October 20, 2009 at 3:42 am
See BOL Here
http://msdn.microsoft.com/en-us/library/ms175976.aspx
The following types of errors are not handled by a CATCH block when they occur at the same level of execution as the TRY…CATCH construct:
...
October 20, 2009 at 3:12 am
You've posted into 'Sql Server 7,2000' forum are you not on a later release ?
In guessing so as you have used row_number().
See this article (and the following discussion for advice...
October 20, 2009 at 1:38 am
matt6749 (10/19/2009)
Wow! I wouldn't have guessed that the formula in the query would be faster!
Much faster..
http://sqlblogcasts.com/blogs/sqlandthelike/archive/2009/10/15/udf-overhead-a-simple-example.aspx
October 20, 2009 at 1:32 am
You still seem to be missing the main performance point , you need to set a limit on the long / lat.
Looking at your query plan in one of...
October 20, 2009 at 1:23 am
matt6749 (10/19/2009)
--> @radius is in miles - I didn't think you could use it with Lat/Longitude calculations??? e.g. ( t1.Latitude between t2.Latitude - @radius and t2.Latitude +...
October 19, 2009 at 10:38 am
Viewing 15 posts - 1,336 through 1,350 (of 1,825 total)