June 10, 2009 at 3:49 pm
We recently had a workstation crash and are in the process of rebuilding a workstation that supports Visual Studio Team Suite with "data dude". Our db uses partitioning, and VSTS seems to think it needs Enterprise Edition for its local validation database. Of course, I tried the Developer version since it supports all SQL Server functionality, but it still offers the smae error messages ...wanting Enterprise Edition.
So I tried to install Enterprise edition....but Enterprise wont install on XP.
Any ideas? We had this working once....but lost that system.
June 10, 2009 at 5:05 pm
If you are in VS2005 Team Suites you need the Database Pro edition addon before you can develop database solutions, because the Database Pro edition uses the developer edition without issues. You know that if you are in VS2008 you need SP1 and GDR download.
Kind regards,
Gift Peddie
June 10, 2009 at 5:18 pm
Thank you for assisting! My Help/About shows:
Microsoft Visual Studio 2005 Version 8.0.50727.762 (SP.050727-7600)
Microsoft .NET Framework Version 2.0.50727 SP1
Installed Edition: Professional
Microsoft Visual Basic 2005 90613-246-0000016-41234
Microsoft Visual C# 2005 90613-246-0000016-41234
Microsoft Visual C++ 2005 90613-246-0000016-41234
Microsoft Visual J# 2005 90613-246-0000016-41234
Microsoft Visual Web Developer 2005 90613-246-0000016-41234
Microsoft Web Application Projects 2005 90613-246-0000016-41234
Visual Studio 2005 Team Edition for DB Professionals 90613-246-0000016-41234
Microsoft Visual Studio Team Edition for Database Professionals Version 2.0.50727.354Visual Studio 2005 Team Explorer 90613-246-0000016-41234
Crystal Reports for Visual Studio 2005
Microsoft Visual Studio 2005 Team Explorer - ENU Service Pack 1 (KB926601)
SQL Server Analysis Services
SQL Server Integration Services
SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Update for Microsoft Visual Studio 2005 Team Edition for Database Professionals - ENU (KB936612)
June 10, 2009 at 5:36 pm
You can use the developer edition if you make it SP2 or SP3 and make sure VS2005 is at least Sp1 or Sp2, the reason I used it at a previous employer and the base install require SQL Server the developer edition to be Sp2.
Kind regards,
Gift Peddie
June 11, 2009 at 8:42 am
Yeah, I'd make sure you've got the SP for VS installed, but also, I'd strongly recommend getting the GDR version, which I think also has a service pack. It eliminates a lot of bugs and increases performance as well as adding new functionality.
You may have an incorrect saetting in the Data Connections property under Database Tools in the Options window. Check that prior to opening any data dude projects.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 11, 2009 at 9:02 am
Is there a GDR for 2005? I thought that was just a 2008 issue.
June 11, 2009 at 9:04 am
The GDR is for 2008, but it changes the tool pretty radically in terms of deployment. It works great with 2005. I'd go for it if I were you.
I just checked, GDR R2 is out. Which means even fewer bugs than before.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 11, 2009 at 9:08 am
Thanks for that suggestion, but Im not in a position to force the client to upgrade from 2005 to 2008....there are a lot of folks that dont just hand over $ to M$...just becasue time passes.
June 11, 2009 at 9:15 am
No, I'm sorry. I didn't mean upgrade to SQL Server 2008. I meant upgrade to the GDR. I don't think there's any cost associated there. The functionality improvements in the GDR over the older release, again, especially around deployments, are not to be missed.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 11, 2009 at 9:19 am
Thanx !! I never can get a grip on the whole licensing model of m$, but I believe if we were already licensed for vs2008 we could move the GDR for 2008; however since we are only licensed for vs 2005, we are not entitled to move to move to VS208 GDR. If im wrong (common), please set me straight.
June 11, 2009 at 9:20 am
I think GDR is for VS2008 but the user is running VS2005 so the person cannot use GDR.
Kind regards,
Gift Peddie
June 11, 2009 at 9:32 am
vaxn8r (6/11/2009)
Thanx !! I never can get a grip on the whole licensing model of m$, but I believe if we were already licensed for vs2008 we could move the GDR for 2008; however since we are only licensed for vs 2005, we are not entitled to move to move to VS208 GDR. If im wrong (common), please set me straight.
Nope. I think I'm wrong on this one. You said 2008, I read SQL SErver 2008, but you meant Visual Studio 2008.
You're right. There is a cost there. Sorry for the bad information.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 11, 2009 at 11:50 am
For all that read and offerred assistance....and for those that just read....and for those that might read in the future...
My problem is (mostly) resolved. I changed NOTHING with my VS or SQL, but I did remove a database reference (via a dbmeta) and all is now peachy.
I can only say,,,,,,WTF? Why did a reference cause 600 other errors/issues for objects that had NOTHING to do with the reference???
Regardless, thanx to those the offerred assistance.
Viewing 13 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply