Viewing 15 posts - 2,341 through 2,355 (of 5,504 total)
If you always need to search by Symbol and Date, change the PRIMARY KEY to [Date] ASC, [Symbol] ASC. I'd even recommend to makes this the clustered index (assuming you...
December 23, 2010 at 1:06 pm
As an alternative you could use the CrossTab syntax as described in the related article in my signature.
If you'd need to add some flexibility, use DynamicCrossTab (a related article is...
December 23, 2010 at 12:51 pm
Ok, so at least you have a budgetary number to compete against... 😉
Get a quote from your vendor how much it would cost to replace the "heaviest" c.u.r.s.o.r.s.
Once that's done,...
December 23, 2010 at 12:33 pm
Something like this?
DECLARE @tbl TABLE
(
DATE DATETIME, OrderNmbr INT, Transtype VARCHAR(10), Amount INT, InvoiceinPer CHAR(1)
)
--/*
INSERT INTO @tbl
SELECT '12/1/2010', 12345 ,'Inv', 1000 ,'N' UNION ALL
SELECT '12/3/2010', 12345 ,'Credit', -1000 ,'N' UNION...
December 23, 2010 at 10:25 am
Wouldn't it be more efficient to have one table ANTI_RES with a column AB_CODE, a column for the sensitivity result and one for the sample?
With such a structure you wouldn't...
December 23, 2010 at 9:44 am
skcadavre (12/23/2010)
To add to this, I had a similar issue not too long ago which was solved on this forum.
Hmmmm... your last statement in the link...
December 23, 2010 at 9:35 am
If you're referring to the "Call in the Experts" editorial: sure I did and it demonstrated how much more efficient an organization can be if people know what they don't...
December 23, 2010 at 9:27 am
rmechaber (12/23/2010)
...it honestly sounds like you'd likely get more performance bang for your buck by doing that than you will by virtualizing. ...
Just to make sure there is no misinterpretation:...
December 23, 2010 at 9:24 am
I think the table design needs to be re-evaluated...
Basically there are products, sections and status history per product and section. There might be section groups as well (at least what...
December 23, 2010 at 7:57 am
I was reading a white paper yesterday on virtualizing SQL Server and there was something about "physical I/O path".
Care to share the link? Others might benefit from it.
December 23, 2010 at 4:35 am
I'd go with the XML approach but shred it into relational data behind the scenes (noone needs to know 😉 ).
December 23, 2010 at 4:30 am
If I understand correctly, you have two questions:
a) how to load the file into SQL Server and
b) how to shred the data into tables
a) load the (unshredded) file (using a...
December 23, 2010 at 4:18 am
rootfixxxer (12/23/2010)
No one... 🙁
One reason for not getting an answer yet might be a missing table structure (reduced to the relevant columns) with some sample data so we can visualize...
December 23, 2010 at 3:56 am
Hi Wayne,
the reason for the additional empload tag is the "ROOT('empload')" code snippet.
The ROOT element basically is the "wrapper" around the xml code since a wellfomrmed xml needs a covering...
December 23, 2010 at 2:50 am
Here's one version to define the order:
ORDER BY CASE WHEN cast('19000101' + ' ' +StartTime as datetime) >'19000101 11:30:00:00' THEN 0 ELSE 1 END, StartTime
But I strongly recommend to...
December 22, 2010 at 4:56 pm
Viewing 15 posts - 2,341 through 2,355 (of 5,504 total)