Viewing 15 posts - 38,656 through 38,670 (of 59,072 total)
ravikanth232 (4/30/2010)
Thanq...that helped me...procedure is working not.
You're welcome. I'm assuming that you really meant "procedure is working now".
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 11:17 pm
Heh... you also need speed to insert and doing it the way I suggested will help both speed to read and speed to insert.
PK's are only clustered by default. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 11:14 pm
Have the best of both worlds... from Books Online...
In SQL Server 2005, sp_updatestats updates only those statistics that require updating based on the rowmodctr information in the sys.sysindexes compatibility view;...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 11:06 pm
yogesh_pandey (4/30/2010)
Got it working thank you.
Two way steet here... please post your solution. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 10:53 pm
Using the great start that Paul provided, the following will also drop the decimal point if a whole number is realized...
USE tempdb;
GO
-- *Inline* table-Itemd function
-- Deterministic, system verified, not precise
GO
CREATE...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 10:05 pm
ColdCoffee (4/29/2010)
There is absolutely no information about the emp...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 9:26 pm
Homework, Test, or Interview?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 9:24 pm
Paul,
Try this...
-- Test with table
DECLARE @data
TABLE (
value DOUBLE PRECISION NULL
);
...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 8:53 pm
irobertson (4/30/2010)
Ha really? Lol, that won't work then will it? Complex function it is then.
Do you know what the maximum number of decimal places will ever be for this data?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 8:30 pm
The two articles that Lutz points out above will show you how to do the "multi-pivot" you seek... and all the reasons not to use it as well as an...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 8:01 pm
Change this...
Declare @SqlStr varchar(max);
... to this...
Declare @SqlStr Nvarchar(max);
... and try again.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 7:53 pm
Credits to Navy beans says there's probably a DISTINCT in the offending query and that, behind the scenes, SQL Server is having to make a whole lot more rows due...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 7:46 pm
csillag.yitzik (4/29/2010)
When I get...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 7:36 pm
p.s. Nice post, Digs. It's always great to see the table and some data.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 7:05 pm
I'd recommend NOT using a clustered index that has Symbol,Date as the columns and in that order... there will be a pot wad of page splits.
Make Symbol,Date a NON clustered...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2010 at 7:04 pm
Viewing 15 posts - 38,656 through 38,670 (of 59,072 total)