Viewing 15 posts - 51,736 through 51,750 (of 59,091 total)
peer_mohamed2k (3/14/2008)
I have 1,65,00,000 rows [16 million rows] in one table. I am using this table for SQL reports. When I use this table joining with some other tables, my...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:46 pm
The short answer is NO and sys.tables won't tell you a thing about this.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:41 pm
Heh... all good methods but they left a really good one out... it's really old fashioned but it works really well... look at the drive... if the little red light...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:40 pm
Yep... also try sp_helpdb. Not as robust but will tell you the overall size. And thanks for posting even though you found your own answer.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:37 pm
DECLARE @EndTime DATETIME
DECLARE @StartTime DATETIME
SET @StartTime = GETDATE()
--... code here to be measured for duration
SET @EndTime = GETDATE()
PRINT...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:35 pm
Dunno if it's any of these... see attached... might be DBCC Buffer or DBCC ProcBuf.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:16 pm
I found it... it's an article on this forum by a good fellow by the name of David Poole... I had it in my "favorites"...
http://www.sqlservercentral.com/articles/Administering/utilityprocedures/2272/
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:10 pm
kumar99ms (3/16/2008)
could plz tel me is there another way to find out dead lock
How can i rectify this deadlock
Which situvastion it will occure
Blocking and dead lock which...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 9:05 pm
The fastest method is neither... the fastest method is BULK INSERT. I don't use SSIS or DTS, but rumor has it that SSIS has a "BULK INSERT" object that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:59 pm
Absolutely... I have the steps to do it somewhere but it's been a 1000 years since I've done it... let me look for it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:54 pm
I agree with Sergiy... and, if you use SELECT INTO, you will have about 58 minutes left to ensure the FK's have been correctly instantiated and to do some regression...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:46 pm
Lisa Slater Nicholls (3/16/2008)
Before you use any of those that have a self join or correlated subquery that use the ">=" or "<=" or any other inequality method to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:43 pm
Ok, folks... I was operating on some old experiences with correlated sub-queries... Hugo and Barry's posts made me look deeper and, after studying the actual execution plans in both SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:36 pm
Hugo Kornelis (3/16/2008)
]
Heh... How often I've been bit by the infamous timeout on this forum... I too have learned to at least do a {CTRL-A}{CTRL-C} before I hit PREVIEW or...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:26 pm
anvi (3/16/2008)
This is a top class article: clear, deep and useful.
Thanks for the feedback, Anvi. What's even better than my humble article is what folks have to say in...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2008 at 8:15 pm
Viewing 15 posts - 51,736 through 51,750 (of 59,091 total)