Viewing 15 posts - 53,086 through 53,100 (of 59,072 total)
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
Phil,
Nothing attached and no code visible... dunno if that was your intent, or not...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 9:07 am
The only problem I see in such a naming convention is if you have a usefull function, proc, table, or view that is used in one schema that you'd like...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 9:04 am
p.s. IF, by chance, you are using the V&H coordinates (as Telcordia calls them) from the "Donald Projection" that is used so often for calculating distance for telephony, airlines,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 8:54 am
SQRT and SQUARE are standard mathematical functions in pretty much every make and flavor of SQL including SQL Server.
Your values of the coordinates of x1, x2, y1, and y2 can...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2008 at 8:43 am
You might also be able to use something like OPENDATASOURCE...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 10:18 pm
I'm thinking that if inheritance did exist in SQL Server, it would create a "work" table in TempDB, anyway... what's so terrible about using INSERT/EXEC to populate a temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 10:16 pm
I'd start a new thread with a new subject... will probably get more attention that way...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 10:06 pm
Probably easiest to write a pass-through query (maybe to a view) in Excel and print from Excel.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 10:05 pm
Ok, thanks for the feedback... does that mean that you're all set?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 9:58 pm
Assuming that "TimeElapsed" is of the DateTime datatype...
SELECT currDt = GETDATE()-TimeElapsed
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 9:46 pm
3 pages starting at...
http://www.sql-server-helper.com/tips/read-import-excel-file-p01.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 9:37 pm
Viewing 15 posts - 53,086 through 53,100 (of 59,072 total)