tag:blogger.com,1999:blog-13265058.post323461121011571142..comments2009-04-21T19:43:43.953+10:00Gary Myershttps://profiles.google.com/116132019768637593422noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13265058.post-66581054328800530842008-03-24T16:39:00.000+11:002008-03-24T16:39:00.000+11:00Hey Gary,<BR/>Nice example of SQL Server troubleshooting for Oracle DBA. Too bad SS is still far behind Oracle on instrumentation front and you have to tweak the code to track it down.<BR/>Cheers,<BR/>AlexAlex Gorbachevhttp://www.blogger.com/profile/03862972144277237798noreply@blogger.comtag:blogger.com,1999:blog-13265058.post-39126345899944218792008-02-14T21:01:00.000+11:002008-02-14T21:01:00.000+11:00Excellent stuff, Gary.<BR/><BR/>Yeah, for some reason inserts on low cardnlty columns are a bit of a disaster in SS2k5. <BR/><BR/>Not sure if they do bitmap indexes instead of btree without telling anyone - a common occurrance in M$-land - or some other weird coding to check values on the duplicate keys. <BR/><BR/>Real weird. <BR/><BR/>There are a few other "gotchas" in that product. I'm finding more and more that good old "rule of thumb" stuff in Oracle also applies to SS2k5. Like drop index-load data-create index. <BR/><BR/>I wish they had an index disable. They probably do, but I never found the dialogue box! :-)<BR/><BR/>Have you tried the maintenance plans in Studio 2k5? That's the bit I'm finding more and more interesting: visual programming at its best. Drag and drop modules, customize their interface, create custom connectors and presto: there's a batch maintenance job.<BR/><BR/>Good stuff.Noonshttp://www.blogger.com/profile/07694829378563989648noreply@blogger.com