Viewing 15 posts - 36,451 through 36,465 (of 59,067 total)
Dave Ballantyne (10/4/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 7:57 am
Grant Fritchey (10/4/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 7:54 am
Dave Ballantyne (10/4/2010)
Started off , other than pre-amble, with a run through of my "Fifo"...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 7:45 am
LutzM (10/4/2010)
Your latest version include results for 2010-02-27 to 2010-03-05. But those are out of the date range to be queried.
I guess Digs need to decide where to place the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 7:24 am
Dave Ballantyne (10/3/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 6:20 am
With the understanding that you'll eventually verify what I asked, the following code does the trick. I went for logical understanding and ease of maintenance rather than code brevity....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 6:01 am
Digs (10/3/2010)
The daily data can be nasty.
For example I can get data for a week like these three cases:
1) Tue,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2010 at 4:40 am
Heh... P.S.... don't worry about the correlated subqueries. The only time such a thing will become a problem is when an aggregated inequality is involved which will make for...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 8:42 pm
Digs (10/3/2010)
HI Jeff,Max records : 40000
Average : 6000
Cool... This should do nicely with the indexes you currently have then because they're going to cause table scans the way they...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 8:40 pm
Hey Digs,
What's the max number of data rows you expect to handle at one time?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 7:21 pm
Digs (10/3/2010)
CREATE TABLE [dbo].[DIM_Data_OHLC](
[RecID] [int] IDENTITY(1,1) NOT NULL,
[Date] [datetime] NOT NULL,
[Open] [float] NULL,
[High] [float] NULL,
[Low] [float] NULL,
[Close] [float] NULL,
[Volume]...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 7:06 pm
CirquedeSQLeil (10/2/2010)
Brandie Tarvin (10/2/2010)
CirquedeSQLeil (10/2/2010)
Grant Fritchey (10/2/2010)
Hey guys, thanks for dumping a load of... something into my in box. What the heck were you guys smoking in here last night?
No...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 12:40 pm
@Pavel,
What is the default collation on your machine, please? And thanks ahead of time for helping me figure this out.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 12:32 pm
Pavel Pawlowski (10/2/2010)
Maybe I'm doing somethig wrong or forget something, but I'm not...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 12:27 pm
steve-893342 (10/2/2010)
Aha the 1,333 test:-) Curiously enough I had already carried out the analysis according to your CsvTest but on 10,000 Row X 1,333 Element table. Results available on request
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2010 at 12:22 pm
Viewing 15 posts - 36,451 through 36,465 (of 59,067 total)