Viewing 15 posts - 52,066 through 52,080 (of 59,091 total)
Oooohhh... I just ran into that paging problem... really bad case of parameter sniffing and the traditional methods don't fix it... only full blown dynamic SQL fixes it... lemm see...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 1:38 pm
p.s. You friend DOES know what Books Online is, doesn't (s)he??? I figure if you have to ask questions on this forum for him/her, they just might not...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 1:03 pm
A week of preparation on this is not enough... but I'd say your best bet is to curl up with Books Online for the next week...
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e9099cce-7f81-4808-8523-587bbcdc1720.htm
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/c2eb5f77-2dc1-49b4-bd19-2cdac4c6cae1.htm
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/31529dfe-68e7-49f7-b3c2-39fcecf33a95.htm
... an exam-cram of this...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 1:00 pm
Just another test... please ignore.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 11:00 am
Just a test... please ignore...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 9:12 am
Perhaps a permissions change on SQL Server or someone removed a "share" from the target drive... or, maybe the file isn't there anymore... or the machine the file is on...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 8:01 am
Shiva,
Try the Microsoft website... I'm sure they have oodles of SSIS propaganda there...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:58 am
Ok... was just making sure. You should have no problems with the temp tables.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:54 am
No... you don't need anything that complicated. Looky here...
[font="Courier New"]SELECT CAST('Jan 2008' AS DATETIME)
------------------------------------------------------
2008-01-01 00:00:00.000[/font]
So, the only thing you need to do is change the backslash to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:52 am
GilaMonster (3/6/2008)
The index with ProductID first produces an index scan because ProductID is not in the where clause.
Ummmm..... heh... What's that highlighted in red????
SELECT
ph.ProductId
,ph.CLientID
, ph.PolicyType
FROM
PolicyHeaders ph
INNER JOIN Products pr
ON...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:40 am
Ken... the OP actually wants to know what the algorithym is for the CheckSum function.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:35 am
Jacob Luebbers (3/6/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:34 am
Nisha, 2000 rows is nothing. Use Select/Into. Look at my previous post with the test code. Select/Into will load 2000 rows in less than 15 milliseconds. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:26 am
Why would you want to create, compile, register, and attach a CLR to do the same thing that was just done in T-SQL?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:18 am
I agree.... the Dynamic SQL will frequently perform better because it snuffs any chance of parameter sniffing and forces a recompile so you're always using a good execution plan... For...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2008 at 7:09 am
Viewing 15 posts - 52,066 through 52,080 (of 59,091 total)