Is there a risk of corruption in SQL Server 2000 when using SQL Server 2005 Management Studio?

Question

In an interview for the SQL DBA position, I mentioned a while ago that I prefer Studio 2005 Management Studio instead of older versions of Enterprise Manager / Query Analyzer. The database administrator who interviewed me said that in their 2000 databases they did some kind of database corruption when making changes with MS MS 2005, so they always use Enterprise Manager.

It was a little vague, but I got the impression that he was talking about some kind of corruption that occurred when changing the server or database settings, and not just in regular SQL updates or something like that.

Has anyone heard of this? I did not take this position, so I can not follow up on receiving additional information.

Answer 1

Looks like he just used this as an excuse for not having experience with SQL 2005 Management Studio. DBA hate change. lol.

Answer 2

I never came across this, in almost three years of using SQL Management Studio 2005 to manage SQL 2000 databases. There are several tasks that I still return to EntMan, but I never had a database that met even a minimal bit of corruption . (And background: as a consultant, I manage about 45 different databases for both client and internal projects, most of which have been hit hard, and only about a dozen are SQL2005 databases.)