Viewing 15 posts - 43,771 through 43,785 (of 59,101 total)
Praveen,
What version of SQL Server are you using? 2k, 2k5, 2k8?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2009 at 4:50 pm
Robert (5/15/2009)
If you have an "order...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2009 at 8:17 am
Attila (5/15/2009)
Paralelly start a script which runs in every minutes, and writs out the inputbuffer of each spid>49, plus the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2009 at 8:14 am
alex (5/15/2009)
What do you gain by handling the looping yourself rather than just using a...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2009 at 8:12 am
I found the code I used to gen a Tally table on the fly using what Oracle calls "Subquery Refactoring" which is a fancy name for "CTE". Add a...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 9:44 pm
Haven't need to try it. I'm pretty fortunate in that most of the data providers I "meat" up with respond pretty well at the mere threat of a malstrome...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 8:23 pm
Barkingdog (5/9/2009)
Per the Extimated Execution Plan, TableA (with 60 millon rows) uses about 56% of the query for a table scan! (I will investigate the "predicate" shown in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 8:05 pm
Got it and mostly agree especially since CHECKSUM is not a guarantee that something has changed or not.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 7:58 pm
Bruce W Cassidy (5/14/2009)
Jeff Moden (5/14/2009)
The performance on a persisted calculated column is "sucky"?
[font="Verdana"]Yup. You persist it by creating an index over it, right? So when you do...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 7:43 pm
christophe.mulotti (5/14/2009)
SELECT DISTINCT Cast(Cast(Col1 as nVarchar(2))+Cast(col2 as nVarchar(3))) as nvarchar(5)) as invalidValue
FROM Table1
WHERE Cast(Cast(Col1 as nVarchar(2))+Cast(col2 as nVarchar(3))) as nvarchar(5))...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 7:28 pm
Bruce W Cassidy (5/14/2009)
[font="Verdana"]A persisted value can help. However, from experience... don't bother -- the performance is too sucky.
The performance on a persisted calculated column is "sucky"?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 7:14 pm
Is it homework, a test, of a job interview? ALL of that information is in Books Online. I recommend you spend a bit of time there. Hope...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 11:29 am
usman.tanveer (5/14/2009)
Christopher Stobbs (5/14/2009)
DECLARE @MyTable TABLE
(Id INT,
Team CHAR(1))
INSERT INTO @MyTable
SELECT 1, 'A' UNION ALL
SELECT 2, 'A' UNION ALL
SELECT 3, 'A' UNION ALL
SELECT 3, 'B'
SELECT
Id,MAX(Team)
FROM @MyTable
GROUP BY Id
Thanks for...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 11:19 am
Shawn Therrien (5/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 11:12 am
Steve Jones - Editor (5/13/2009)
Ahhh, Klingons asking questions. About databases? Could be interesting....
Heh... still not as bad as some of the questions folks ask on the forums. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2009 at 10:49 am
Viewing 15 posts - 43,771 through 43,785 (of 59,101 total)