Gaetan

I downloaded the RTM bits of "VS 2005 Team Edition for DB Professionals" on a VS 2005 SP1 system running on Windows 2003 Server SP2 and performed this:

- Took my DB offline
- Copied the MDF and LDF file to another folder
- Brough back the DB online
- Attached the copy of the DB and used a different name as the DB name
- Added a few columns and constraints to the original DB
- Started a "Schema Compare" and compared the 2 databases
- After a minimal amount of processing, Visual Studio 2005 crashed. Repeated attempts produced the same result.

I was expecting something else from that add-on. Does it work Are there any special configuration steps I need to perform

Here is the Help - About info of my VS2005 environment:

Microsoft Visual Studio 2005
Version 8.0.50727.762 (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Enterprise

Microsoft Visual Basic 2005 90613-246-0000016-41289
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 90613-246-0000016-41289
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 90613-246-0000016-41289
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 90613-246-0000016-41289
Microsoft Visual J# 2005

Microsoft Visual Studio Tools for Office 90613-246-0000016-41289
Microsoft Visual Studio Tools for the Microsoft Office System

Microsoft Visual Web Developer 2005 90613-246-0000016-41289
Microsoft Visual Web Developer 2005

Microsoft Web Application Projects 2005 90613-246-0000016-41289
Microsoft Web Application Projects 2005
Version 8.0.50727.762

Microsoft Web Deployment Projects 2005 90613-246-0000016-41289
Microsoft Web Deployment Projects 2005

Visual Studio 2005 Team Edition for Architects 90613-246-0000016-41289
Microsoft Visual Studio 2005 Team Edition for Software Architects

Visual Studio 2005 Team Edition for DB Professionals 90613-246-0000016-41289
Microsoft Visual Studio Team Edition for Database Professionals Version 2.0.50727.251

Visual Studio 2005 Team Edition for Developers 90613-246-0000016-41289
Microsoft Visual Studio 2005 Team Edition for Software Developers

Visual Studio 2005 Team Edition for Testers 90613-246-0000016-41289
Microsoft Visual Studio 2005 Team Edition for Software Testers

Microsoft Visual Studio 2005 Team Suite - ENU Service Pack 1 (KB926601)
This service pack is for Microsoft Visual Studio 2005 Team Suite - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/926601

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.3042.00

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.3042.00

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.3042.00




Re: Visual Studio Team System - Database Professionals VS 2005 Crash on Schema Compare

Gert Drapers - MSFT

Without more information I am not able to help you, if you can provide me with a concrete repro of the steps, not just the configuration, or you would have to contact product support services so they can help you.

A crash is never by design, but I need more concrete info to look at, if you have a stack dump or crash dump from Watson that should also help.

-GertD





Re: Visual Studio Team System - Database Professionals VS 2005 Crash on Schema Compare

StevenPo - MSFT

Gaetan -

Are you still blocked by this issue If so, please provide the additional repro steps that Gert requested and we will see if we can get you unblocked.

thanks,






Re: Visual Studio Team System - Database Professionals VS 2005 Crash on Schema Compare

Gaetan

Sorry about the delay ... I was away. As stated in the OP, I took a copy of the DB files and added them to SQL as a different DB name then performed changes to the original DB before doing a schema compare. The compare failed to complete because VS2005 crashed. Many reports were sent to Microsoft using the dialog at the crash time.

This morning I took a different approach to perform a schema compare. I restored from Visual Source Safe an earlier build of the SQL files used to create my DB. I edited the files to create a different DB name and excluded the lsingle CLR based stored procedure. I then performed a new schema compare and this time it worked.

I will try once more the DB copy as stated in the OP to see if that approach is the culprit of the compare failure leading to the VS 2005 crash.





Re: Visual Studio Team System - Database Professionals VS 2005 Crash on Schema Compare

StevenPo - MSFT

Gaetan -

Thanks for the follow-up (I realize that most customers' top priority is getting their project to work, not spending time chatting with us here in the forums Smile. If you do see the crash again, let us know and we can have our test folks see if they can reproduce that scenario in-house.

thanks,