Viewing 15 posts - 136 through 150 (of 388 total)
j-1064772 (2/29/2016)
rstone (2/29/2016)
February 29, 2016 at 12:29 pm
kenambrose (2/29/2016)
In fact, I always (always) create a unique constraint on the natural key and a surrogate key (bigint)
If all SQL devs knew this, the world would be a...
February 29, 2016 at 12:00 pm
If we make sure that input data is uniquely identifiable on each table, i.e. non identity as that is generated after the input data, then we will be forced to...
February 29, 2016 at 10:18 am
Optimise your indexing. Tlog is used to rebuild unused indexes as well so get rid of the dead weight. Also I set threshols higher and run online daily so that...
February 23, 2016 at 2:00 am
Would you mind posting the TVF definition?
I just want to be sure that it is not a multistatement TVF.
Is it defined as
CREATE FUNCTION DBO.iTVF (@Var INT)
RETURNS TABLE
AS
RETURN
SELECT blaadieblah
FROM...
February 11, 2016 at 4:41 am
type Cntrl+t in results pane.
select '8'+char(13)+char(10)+'9'+char(13)+char(10)+'6'+char(13)+char(10)
+'4'+char(13)+char(10)+'3'+char(13)+char(10)+'2'+char(13)+char(10)+'1'
February 9, 2016 at 8:18 am
Apparently there is a compatibility matrix which lets the engine know if the cast preserves the order of the data between the 2 data types.
So Cast ( intcol as small...
February 9, 2016 at 5:22 am
Instance level doesnt matter.
Each index should be hand crafted, i.e. each index should be <create index blah blah with(fillfactor = X)>
Indexes on identites, which increase monotocically, should be around 100.
Indexes...
February 9, 2016 at 5:10 am
Hugo Kornelis (2/5/2016)
Instant file initialization applies to data files only; log files always have to be zeroed.
+1
February 5, 2016 at 9:28 am
rcerney 63319 (2/1/2016)
February 2, 2016 at 3:04 am
Thanks Gail.
I have been using your article as a way to optimise a catch all proc without DSQL cos the devs are, let's say, averse to DSQL.
On re-reading, I do...
January 25, 2016 at 8:57 am
Hugo Kornelis (1/22/2016)
MadAdmin (1/22/2016)
Instead of the non sargable
WHERE LEFT(TRANSDATE,6) = @CutOffDate
use the sargable
SELECT SUM(QUANTITY) AS TotalQty, @CutOffDate
FROM ICIVAL
WHERE TRANSDATE like @CutOffDate+'%'...
January 22, 2016 at 6:17 am
Just throwing in my 2 pence
Instead of the non sargable
WHERE LEFT(TRANSDATE,6) = @CutOffDate
use the sargable
SELECT SUM(QUANTITY) AS TotalQty, @CutOffDate
FROM ICIVAL
WHERE TRANSDATE like @CutOffDate+'%'
January 22, 2016 at 4:14 am
You can only get 99.99% improvement if the original query was doing scans. Seems like yours was not so 15% ontop of an already fast proc is very good.
Would you...
January 13, 2016 at 8:03 am
Viewing 15 posts - 136 through 150 (of 388 total)