Cannot create new database diagram in SQL Server 2008 - visual-studio

I'm using SQL Server Management Studio 2008 and SQL Server 2008.
Currently, I cannot create new database diagram from the SSMS 2008 on an SQL Server 2008 instance.
Has anyone ever experienced this ?
The problem started after I tried to install Visual Studio 11 Beta, and apparently the Beta also installs SQL Server 2012 RC0. Now I have uninstalled the Visual Studio 11 Beta and the SQL Server 2012 that goes along with it.
EDIT :
Error message that shows when I tried to create new database diagrams is : "The specified module could not be found (MS Visual Database Tools)"

I had the same problem but never found an explanation of what was wrong. I ended up uninstalling SQL Server 2012, uninstalling Visual Studio 11 Beta, and then reinstalling the Visual Studio 11 Beta (keeping SQL Server 2008). I can now create DB diagrams from SSMS 2008, but not from within Visual Studio 11 Beta (I don't think Visual Studio 11 Beta supports the feature, at least not for SQL Server 2008).

Related

Visual Studio 2017 Creates SDF

I am using Visual Studio 2017 Community and installed .Net desktop development which has SQL Server Express 2016 LocalDB installed.
I am creating a database through code for a PluralSight project. It creates a SQL Server Compact Edition (.sdf) instead of SQL Server Express (.mdf).
I can't figure out why the Express database is being created. Any ideas? Thanks for your help.

Can we directly migrate SQL Server 2008 to 2014 without changing anything in Visual Studio?

We have Visual Studio 2010 with .Net Framework 4.5
and SQL Server version 2008.
We are in the process of migrating SQL Serer 2008 to 2014.
I want to know the steps to migrate to 2014 and is there any settings or extensions or updates to be done for Visual Studio to make it compatible with SQL Server 2014?
For full support of SQL Server 2014 inside Visual Studio, you need to run at least Visual Studio 2012 and have SSDT installed as outlined here.
However, to connect to SQL Server from your application or from Visual Studio and to do basic operations against the database no update to Visual Studio 2010 is required.

what is the proper install order for visual studio 2012 and SQL Server Management Studio 2012 on win7?

I am preparing to do some web development against a SQL Server 2012 server on a fresh install of win 7 x64 development VM.
What should I install first, visual studio or SSMS?
This is my favorite order:
Windows update before installing anything.
SQL Server 2012
If you have SP1 integrated with you ISO file, skip to step 4.
If you have both SP1 and U5 integrated with your ISO file, skip to step 5
Unselect SQL Server Data Tools during installation (step 8 will install the VS 2012 templates instead of these old 2010 ones)
SQL Server 2012 SP1
SQL Server 2012 SP1 U5
Visual Studio 2012
If you have U3 integrated with you ISO file, skip to step 7.
Unselect SQL Server Data Tools during installation because we'll install the updated bits in step 7
Visual Studio 2012 U3
SQL Server Data Tools - BI (adds BI project templates to Visual Studio 2012)
SQL Server Data Tools (allows you to manage SQL Server 2012 from within visual Studio 2012)
Windows Update
ReSharper
StyleCop
SQL ToolBelt
Neither - you can install them in any order. While you do get the occasional question about it in various different forums, I have done this and never had an issue.
SQL does have a Visual Studio dependency (formerly) called BIDS, but Visual Studio can install over/around this no problem.
Note that this answer is correct when using the initial SQL 2012 release (as that was the latest edition when this question was asked). Subsequent releases may have changed things. I have made this answer CW to encourage others to edit it as necessary to include info about later versions.
I don't know if there is a different way for VMs but on Windows we used to install SQL Server first, as some of the configurations of Visual studio conflict with SQL Server configurations if it was installed before
No direct dependencies found between the two components, installing Visual Studio first then ensure that .NET Framework installed properly is my approach, then installing SQL Server, but in all cases the SQL Server installation installs the following software components - 2008:
NET Framework 3.5
SQL Server Native Client
SQL Server Setup support files
My approach:
Visual Studio 2008.
Visual Studio SP1.
SQL Server 2008.
Run Windows updates.
Useful question here

Where is SQL Server Compact Edition 4?

I have Visual Studio 2010 Prof and sp1 installed. When I go to server to add new connection and create a new DB with SQL Server Compact.
There is no SQL Server Compact 4 option but 3.5?
I tried to run tools for vs2010 and SQL Server Compact which I got a need to install sp1 error which I already heave?
How do I create DB's with compact edition in vs2010?
You need to download the SQL Server Compact Edition v4 from the Microsoft download center and install it.
It's not part of VS 2010 (since it was released after VS 2010)
Update: did you also download and install the Visual Studio 2010 SP1 Tools for SQL Server Compact 4 ?
Update #2: sorry, can't reproduce that issue of yours - after I've downloaded and installed those bits (SQL Server CE 4 runtime + VS 2010 tools), I do get the SQL Server Compact 4.0 in my VS 2010 Server Explorer > Add Connection dialog:

Visual Studio 2008 Reporting Services backward compability issue

I know there is an Issue using SQL Server 2000 Reporting Services and Visual Studio 2005, but does this error still exsist with Visual Studio 2008 and 2010?
If so, is there any work-aground to get this working?
I do know that SSIS 2005 requires VS 2005 and that SSIS 2008 requires VS 2008. So if you have upgraded your SQL Server 2005 client tool installation to 2008, there is no way (AFAIK) to create SSIS 2005 projects.
My guess is that you will see the same issues with SSRS as with SSIS.

Resources