Viewing 15 posts - 931 through 945 (of 2,171 total)
See
http://www.sqlservercentral.com/articles/Advanced+Querying/howmanymoremondaysuntiliretire/2475/%5B/url%5D
N 56°04'39.16"
E 12°55'05.25"
May 14, 2008 at 12:36 am
This would be a starter
http://technet.microsoft.com/en-us/library/bb630290(SQL.100).aspx
Interbase can give you some clues
http://www.ibprovider.com/eng/documentation/odbc_escape_sequences_eng.html
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 11:41 pm
No. FN makes your connection resort to ODBC level calls and use the WEEK function and calculate the week value for created column.
It will be faster to use DATEPART(WEEK, Created)...
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 1:50 pm
The "blog topic" text is a link to the actual blog topic entry.
With Peso 1 it takes about 458,426 milliseconds for all 1,000 ProcessCell set to same value
Give or take...
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 8:45 am
Michael Meierruth (5/13/2008)
Thus how long does you query take on your test data of 1000 rows with all ProcessCell values set to 'A'?
With Peso 3 it takes about 76 milliseconds.
With...
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 8:20 am
Turned out to be easier than I thought.
The "collapsed" date ranges are already sequenced 🙂
-- Get the collapsed date ranges
SELECTProcessCell,
MIN(DateFrom) AS DateFrom,
MAX(DateTo) AS DateTo
FROM#ProcessCellAllocation
GROUP BYProcessCell,
Seq
ORDER BYSeq
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 7:53 am
Thanks Jeff.
It sure is an interesting problem!
I tested with 100,000 date pairs and Peso 3 run in 900 ms. With 1,000,000 date pairs Peso 3 run in 2.2 seconds.
I will...
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 7:51 am
For 10,000 date pairs, I couldn't run Peso 1 and Michael in a timely fashion.
Here are however the results for Peso 2 and Peso 3
** Peso 2
Table 'Worktable'. Scan...
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 7:19 am
Here is a script for testing, Jeff.
Results for the three previous methods and a new method is included below
Peso 1 - Traditional t-sqlSQL Profiler - Rowcount 949, reads 43,512, CPU...
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 6:47 am
Or you can connect with a stream file object.
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 4:18 am
Also asked and answered here
http://www.sqlservercentral.com/Forums/Topic492872-8-5.aspx#bm498859
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 4:17 am
Also asked here http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=102718
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 4:15 am
7 times faster?
Not that bad for a LIKE '%' + Col1 + '%' query.
N 56°04'39.16"
E 12°55'05.25"
May 13, 2008 at 3:40 am
You are referring to this topic?
http://www.sqlservercentral.com/Forums/Topic317259-9-1.aspx
Yes, I wrote that just for testing output from yours faster functions, which initially had some flaws.
I am happy we worked them out and now...
N 56°04'39.16"
E 12°55'05.25"
May 12, 2008 at 11:59 am
Viewing 15 posts - 931 through 945 (of 2,171 total)