I'm currently trying to setup adapter metadata for an SQL adapter in BizTalk through the add generated items (add adapter metadata) wizard but the wizard keeps failing/disappearing.
I can get as far as the Select the type of statement selection.
I choose stored procedure, hit next then the wizard just disappears.
I've checked event viewer but I can't see any related events, I can't see any hidden popups etc. so I'm at a loss.
I am using BizTalk Server 2013 R2 (Standard), with Microsoft SQL 2014 Standard.
I'm using Visual Studio 2013 Update 5 for development with the BizTalk Dev kit.
My dev machine is currently running Windows 10 Pro.
Has anyone seen this before or know how to fix this? I did have a bit of a Google but I couldn't see anything unfortunately.
After much playing around, I finally found the fix.
I'd uninstalled Visual Studio, BizTalk, and anything to do with SQL Server.
Then I'd installed again in the below order:-
Visual Studio 2013
Update 5
Checked for updates
SQL Server 2014
Checked for updates
BizTalk 2013 R2
Checked for updates
That looks to have done it for me.
Related
I have installed SQL Server 2014 and Visual Studio Professional 2015. So, does that mean it already has SSMS pre-installed with it, or it needs to be done separately.
My need is: Report generation using SSMS, from data coming from query behind SQL Server.
So, what needs to be exactly done to configure SSMS into SQL Server with VS 2015.
Upon deep diving even more, got the answer.
Option One: Google for 'SQL Server Data Tools' installer, compatible with your VS. Run the Installer.
Option Two: Open Visual Studio 2015 - Tools > Extension and Updates. Find/Search for 'SQL Server Data Tools' update option. Run it.
I'm still not sure if there comes a complete package of Visual Studio along with Data Tools, but I don't think it does. As we still need to add certain packages into VS Installer as per need.
I am attempting to compare schemas of two databases on the same server.
The two databases are named benchmarkdb and benchmarkdb_dev.
In Visual Studio 2017, I go to Tools > SQL Server > New Schema Compare...
From both drop down menus labeled "Select Source" and "Select Target" (as seen in the picture below), I want to select benchmarkdb as source and bencmarkdb_dev as target.
After clicking to select a source, the "Select Source Schema" pops up, and I clicked the "Select Connection..." button, which brought another popup. The newest popup (the one on the right in the picture below) shows both databases I am trying to compare.
However, after I choose one for either the source or the target, all pop ups close, but nothing populates the "Select Source..." or "Select Target..." drop down menus. In fact, it just goes back to looking like the first picture.
Is there a solution to this so I can compare the schemas between the databases?
Update:
I have tried this on VS 2012, 2015, and 2017. All are facing the same issue. VS software and system software are up to date. Below are some versions of software that I am using, if it is any help.
Windows 7 Enterprise SP1
VS 2012, 2015, and 2017
SQL Server 2014
.NET Framework v4.7.02053
OK, so I managed to fix it.
First off, you need to install SSDT from Microsoft pages. Just google it.
Make sure that you also have it listed in individual components when starting Installer (on Modify). Only SQL Server Database is required (I could choose from Integration Services and 3 more).
Next, you need to "Remove connection from history" in Schema Compare modal for connection selection.
I closed VS at this point, to make sure that the connection is not in history anymore.
Starting VS the next time, you should not have the problematic connection in history.
Recreate the connection (I checked "remember password") and voila. Schema compare works.
Not really sure, but in desperation I also installed "Redgate ReadyRoll Core", "Redgate SQL Prompt Core" and "Redgate SQL Search".
I don't think it matters, but if all else fails...
Edit: This worked on 2 machines and it doesn't seem to be connected to VS version.
I had the same issue, but I don't know if I had the same root cause.
My problems started after changing my database from SQL Server on a Window Server to SQL Server on a Linux Container. The schema compare would appear to accept my selection but the database field would never actually populate and I could not perform a comparison.
There were 2 things I had to do to solve the problem.
Update Visual Studio (using the standard updater within Visual Studio).
Update the SQL Server Development Tools (SSDT) add-on for Visual Studio to a preview version that supports SQL Server on Linux. That download is available here.
After both updates were in place I could select the database and execute Schema Comparisons between my project and SQL Server on Linux exactly as I had been doing for SQL Server on Windows.
If running a local database, check what version of SQL Management studio you are using
I had the same issue running Visual Studio Pro 2017 and SQL management studio v18.6 with SQL Server 2017 installed.
I tried all of the above solutions and no luck
Even going back to Visual Studio 2015 didn't work for me. What did work though was changing back to SQL Management Studio v17.9.1
No issues any more.
I may try to upgrade Visual Studio to 2017 again to see if that works now
We currently work with all versions of SQL Server from 2005 onwards. To save time I try to do everything in a single version of Management Studio. This also helps if running newer client operating systems like Windows 10 which old client tools aren't compatible with.
Specifically when trying to view the graphical SSMS interface for index properties I get the following error if connected to a SQL Server 2005 instance.
In Object Explorer:
Database > Table > Indexes > Right Click > Properties
Full error text:
TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
Cannot read property IsSparse. This property is not available on SQL Server 2005. (Microsoft.SqlServer.Smo)
This also happens in SSMS 2014, but not SSMS 2012.
So my question is; can something be done to work around this issue allowing one version of management studio to be used for all versions of SQL Server from 2005 onwards?
I'm guessing now, but as it works in SSMS 2012 there must be something going on that targets an older version of mscorlib. Maybe because SSMS 2012 uses a VS2010 shell and different .Net framework?
Many thanks in advance for your time.
There is an Active feedback about that on Microsoft Connect here. Someone suggest a workaround to go into Table Design and go to menu "Indexes/Keys...". It works, but some properties are not editable that way, like Included Columns. The other options left are to use SSMS 2005-2012 or use T-SQL script, like Aaron said.
I have a new laptop with Visual Studio 2015 Enterprise and SQL Server 2016 CTP 3.1 installed on it. I want to develop SSIS & SSRS projects using this setup, but I am having a hard time getting the Business Intelligence templates to show up in VS.
I installed the SQL Server Data Tools for Visual Studio 2015 from here:
https://msdn.microsoft.com/en-us/mt186501.aspx
This installation seemed to work, but the BI templates still did not appear in VS.
After this was installed, I started up the SQL 2016 installation again to see if I could add this as a feature in the installation. It was not an option in the Feature Selection area. I tried both the "Perform new installation of SQL" and "Add feature to an existing instance" options during the setup wizard.
What am I missing here? In doing some research, it seems like these BI templates should be available for VS 2015. I would greatly appreciate any suggestions. Thank you!
Go to Tools > Extensions and Updates... Under the Updates tab, you'll find Microsoft SQL Server Data Tools (SSDT) Update.
SSDT is updated separately from SQL Server itself. In the past, SSDT BI was a separate project as well. Integrating both toolsets is a work in progress. The latest SSDT version is the November 2015 preview which supports SSIS, SSAS, SSRS for SQL Server 2016 preview but only SSAS, SSRS for previous versions.
SSDT doesn't actually require SQL Server, only Visual Studio, and will install no matter which version of SQL Server you have installed (if any).
I found the solution in another forum. This issue has to do with using the "preview" version of SQL 2016. Use this link to download the SSDT for this version:
https://msdn.microsoft.com/en-us/mt429383
Hope this helps someone else...
In VS 2015:
Select Tools -> Extensions & Updates
A console opens. On the LHS, you will see 3 tabs - Installed, Online & Updates
Select Updates -> Product Updates -> Choose Microsoft SQL Server Data Tools (SSDT) Update.
I recently installed Visual Studio 2010 and SQL Server 2012 on a Windows Server 2008 R2 machine - (including all updates/Service Packs).
When attempting to work on a SQL Server database from within Visual Studio, VS throws the following error:
This server version is not supported. Only servers up to Microsoft SQL
Server 2008 are supported
I recall getting this same error a while back (on a different computer) when I updated a SQL Server 2008 instance to SQL Server 2008 R2. The fix, back then, was to install (or reinstall) Visual Studio 2010 SP1.
Now that I'm receiving this error again (on a new computer), I thought it reasonable to reinstall VS SP1 just like I did a while back. However, doing so did not fix the problem.
It appears as though Visual Studio may need another update to support SQL Server 2012 instances.
For clarity, here are the steps that I did to produce the error: (using VS 2010sp1 and SQL2012)
Using VS, create a Windows Forms application
Right-click the project and choose, Add > New Item
Select "Service-based Database"
Cancel out of the "Data Source Configuration Wizard"
A Database will appear under your Project in Solution Explorer. Double-click the new database
The Database will be added to Server Explorer's list of Data Connections
In Server Explorer, open the database, right-click the Tables directory, then select "Add New Table"
The error "This server version is not supported...." is thrown
Screenshots for whatever its worth..
My question is, is there a fix for this? If so, what is it?
Maybe get SQL Server Data Tools, which work with SQL Server 2012? I believe there are some good tutorials and other materials in the Developer Training Kit. I don't think there are any tricks yet to make an older version of Visual Studio / Data Dude compatible with SQL Server 2012.
Following MSDN blog link discusses about the issue that you are facing with local SQL Server database instance in Visual Studio 2010.
Using LocalDB in Visual Studio 2010
My problem was that I couldn't get VS2012 to work right with SQL Server 2012. I installed the latter product first, but after installing VS2012 and attempting to open an existing project, my existing data file just would not work. I know the software is supposed to automatically take you through a wizard to update your database in the project, but that didn't happen, and I couldn't find a way to make it happen. I'm on the point now of getting rid of SQL Server 2012 and going back to 2008. I'd rather use the most current releases, but I can't spend any more time on configuration issues.
I tried reinstalling the SSDT as well, but kept getting the same error you mentioned Jed, this seemed to let me get around the error message:
http://forums.asp.net/t/1721552.aspx/1?Working+with+Denali+SQLEXPRESS+in+VS+11+Database+issue
This error could also occur if you use the wrong provider. A recently came across the "This server version is not supported...." error and after changing the provider from sqlClient Data Provider to SQL Server Native Client 11.0 in the connection string for the Data Source configuration the problem was solved.
For me, the error arises whenever I try creating a new database. So after unsuccessfully attempting all methods advised, I bypassed the error by clicking on "Add connection" and putting my server name in the dialog box. After adding the non-existent database name, it notifies that it can't find such database and asks whether to create it. Voila! Database created (even though server version is supposedly unsupported).