Visual Studio 2013 SQL Query and View Designer Not Appearing

Visual Studio 2013 SQL Query and View Designer not appearing

I have been having the same problem and think I have found the solution.

When you are adding the connection to the Database, in the Add Connection Dialog.
Click 'Change...' next to the Data source

Dialog opens showing 'Change Data Source'

You probable have selected 'Microsoft SQL Server' and then below that there is a drop down where you can select:

.NET Framework Data Provider for OLE DB

.NET Framework Data Provider for SQL Server (This is probably selected by default)

try changing to the OLE DB connection.

Click OK, and then complete the rest of the connection on the 'Add Connection' dialog.
I have then found that using the database works as it did in VS2012 and as you are describing above.

Visual Studio 2013 designer not generating code for Telerik controls

After contacting Telerik support they determined that the issue was with Team Foundation Server and the Visual Studio option to "Get everything when a solution or project is opened". Disabling that appears to solve the issue.

Visual Query Designer not accessible in when connecting to SQL Server 2012 in Visual Studio 2012

Microsoft moved some of the Data tools into SQL Server Data Tools (SSDT). That is a separate install, and it comes with a Visual Studio Extension.

Here's a link to another thread on Stack Overflow.

Visual Studio 2012 Database Designer - Has the functionality changed?

Unable to display SQL Azure table definition in Visual Studio 2013

I found this on a Microsoft forum after struggling for hours. It still takes an age to load, but with the preview SSDT tools, I did get a visual editor for the first time.

Posted by Microsoft on 1/7/2015 at 1:59 PM:

This bug has been fixed in the Preview release to support Azure SQL Database Update V12

See http://blogs.msdn.com/b/ssdt/archive/2014/12/18/sql-server-database-tooling-preview-release-for-the-latest-azure-sql-database-update-v12-preview.aspx for details of this.

The fix will also be included in our next full (non-Preview) release.

Thanks,
Kevin Cunnane,
SQL Server database tooling team

---

Related Topics