July 9, 2007 at 12:14 pm
What's the most obscure issue you've seen as a DBA?
July 9, 2007 at 12:32 pm
A bug in ODBC that only affected SQL 6.5 running on a DEC Alpha. Corrupted the data...
July 10, 2007 at 12:31 am
1000+ issues
July 10, 2007 at 3:21 am
A problem with remote transaction between 2000 and 2005 it bugged my head for almost 6 weeks to get a solution. but atlast i got that myself.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 11, 2007 at 4:55 am
It has to be trying to get iFilters for full-text indexing working on an itanium2 server, i spent ages on the phone to MS before getting the right person (John Kane).
It's still not fixed (over a year on), but we do have workarounds in place till people like Adobe get their act together and move into 64-bit computing.
July 11, 2007 at 10:12 pm
Got to be the differences between "contexts" while running on an Windows 2003 x64 64-bit instance of SQL Server 2005. The core database engine is entirely 64-bit but things like ODBC drivers can be running either 32-bit or 64-bit depending on where you're calling them from (e.g. linked server or SSIS) frustrating as heck as figuring out whether you're running 32 or 64 bit can be a matter of trial and error.
Add "buggy" Oracle drivers, that break differently depending on whether it's a 32 or 64 bit driver, to the mix and things can get really interesting.
Joe
July 12, 2007 at 1:09 am
I certainly agree Joe! Our test and dev environments are 32, and production 64... never-ending issues with linked-servers to Oracle crashing our SQL instance. The latest is database mail working on all servers except the 64 bit clustered production box... and all attempt at troubleshooting the standard resolutions don't work.
Todd Carrier
MCITP - Database Administrator (SQL 2008)
MCSE: Data Platform (SQL 2012)
July 12, 2007 at 4:01 pm
Its Microsoft we talking about
There are too many to list.
July 13, 2007 at 12:23 am
Just to add one imp note MS has fixed almost 450+ bugs in SQL 2005 SP1 and almost 300+ in SP2.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 13, 2007 at 4:17 am
Be aware....the original question is not posted honestly. It is posted solely to generate traffic to the mentioned website....and as such is SPAM.
July 13, 2007 at 9:33 am
yeh, but how many of us are willing to go to a Gulf Coast City?
July 13, 2007 at 1:24 pm
Heh, a Gulf Coast City would be a step up for me (West Palm Beach, Florida), not that I really want to move.
Weirdest issues I had stemmed from me letting someone (our in-house IT) tell me it was OK to install SQL 2005 on a machine and then re-name the machine (this gave me headache after weird, mysterious, uninformative-error-message headache for months, regarding everything from the services accounts to replication)
-- http://dbachman.blogspot.com
July 19, 2007 at 1:19 pm
July 20, 2007 at 10:15 am
I'm curious - did you resolve this error by changing the machine's name back, or did you reinstall SS2k5, or ...? How did you fix this problem, and what finally enabled you to identify it?
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply