.Net compatability with SQL Server 2014 - .net-4.5

I am very new to SQL programming and I wish to work with SQL Server 2014.
Can someone please tell if SQL Server 2014 is compatible with my current configuration:
Visual Studio 2010
.NET 4.5.51209 SP 1
Thanks

It appear to be compatible.Thanks to marc_s for his answer.

Related

SQL Server Integration Services Version

I have a production system which had installed SQL Server 2012, so this system has the Integration Services 11. Then we upgraded the system with SQL Server 2014, so the system had two Integration Services 11 & 12. Then we upgraded to SQL Server 2016, so the system has now three Integration Services 11, 12 & 13.
I done some research on the Internet and i realized that even we upgrade the SQL Server the integration services are installed side-by-side. This is also confirmed from SQL Server Management Console.
When i run DTEXEC on CMD get default version 11, this means that my DTSX packages inside the SSISB Catalog are running using the Integration Services 11 and not the latest one? If this is correct how can i change this to the newest one?
I was recently part of such discussion. It is important to understand SSIS Backward compatibility before.
Also, refer SSIS through its SQL Server Data Tools version, as most commonly people understand it in that way. You can link your thoughts with below mentioned details:
SQL Build# PackageFormatVersion Visual Studio Version(SSDT)
2005 9 2 2005
2008 10 3 2008
2008 R2 10.5 3 2008
2012 11 6 2010 or BI 2012
2014 12 8 2012 CTP2 or 2013
2016 13 8 2015
source: sqlstudies
From this microsoft document you'll understand which SSIS version is compatible with which SQL Server.
Briefly:
Target version of SQL Server Development environment for SSIS packages
2016 SSDT 2015
2014 SSDT 2015 or SSDT-BI 2013
2012 SSDT 2015 or SSDT-BI 2012
In simple words, SSDT 2015 is capable of deployment on any server from 2012 onwards, whereas 2012, 2013 are restrictive.
Beware that, if you open sql server 2012 dtsx in SSDT 2015, then you cannot go back to open it from SSDT-BI 2012.
If this is correct how can i change this to the newest one?
Hence, if you want to upgrade all your packages, open them through SSDT-2015, select deployment version(right click project -> properties -> Target Server Version).
you can read more about these changes here(MSSQLTips)
I think the previous answer provides some very useful information. However, I think I understand the misconception here:
First, there is NO benefit or advantage of "changing this to the newest one". Some people think that SSIS 2016 (11) is better than SSIS 2014 (10) or lower - the fact is that , with SSIS2012 nothing changed except addition of several new features and a new way to deploy items. You will not obtain any speed or performance enhancement. It's just that you get access to a few extra components.
Second, this will never fail because of my answer above. Firstly, SSIS is backward compatible (which is what Microsoft brags about - but honestly, why wouldn't it be?? it's the exact same product sold under different titles, why would it NOT be backward compatible). Secondly, your previous editions of SSIS are there for those like a few features (such as ActiveX) to run in compatibility mode. All in all, I think the question is answered by the fact that SSIS is backward compatible and that NOTHING has changed in the past 3 editions of the product (2012, 2014 and 2016 are nearly identical, and no performance or architectural changes exist between 2008/2008R2 and 2012+)
If you'd like more information, have a look at this link, which starts off by stating:
SQL Server 2014 Integration Services (SSIS) can co-exist side-by-side
with SQL Server 2008 Integration Services and SQL Server 2012
Integration Services.

.Net Framework 1.1 and SQL Server 2014 or 2016

does anyone knows if a .net framework 1.1 application that uses ado.net will still work if I upgrade the SQL Server database from 2008 to 2014 or 2016?

SQL Server 2008 R2 Express: Management Tools Missing from Feature Selection

I am trying to install SQL Server 2008 R2 Express with the SQL Server Management Studio.
However, the Management Tools feature does not seem to be selectable. The screen-shot below shows which Features are available for me to select:
I have made sure that the SQL Server 2008 R2 Management Objects was installed!
I have tried both answered methods at Can't install SQL Server 2008 R2 management tool (complete) and they both do not seem to work for me, I still do not see Management Tools. Upgrading the Edition under the Maintenance section and Uninstalling/Re-installing the SQL Server had no additional effects. The files I am trying to work with to get this to work are:
SQLEXPR_x64_ENU.exe - This is Service Pack 3
SQLManagementStudio_x64_ENU.exe - The file name fooled me, since there is no management studio feature selection!
The question is, why does Microsoft makes it so difficult?
I am using a Windows 7, 64-bit machine. Any help would be greatly appreciated.
You should separately download Microsoft® SQL Server® 2008 Management Studio Express from Microsoft at
http://www.microsoft.com/en-us/download/details.aspx?id=7593
SQLEXPRADV_x64_ENU.exe contains everything and is the best choice for new installs.

Running SQL Server CE 4 Queries with Visual Studio 2012 and SQL Server Management Studio 2012

I have recently upgraded to Visual Studio 2012 and SQL Server Management Studio 2012, however I cannot seem to see how to execute SQL scripts (created by Entity framework) on a SQL Server CE 4.0 database. With VS2010 + SSMS 2008 the Transact-SQL editor would ask for a connection and you could browse to the object, however this option is not available in SSMS 2012.
I have tried to execute the script via the Server Explorer -> New Query window, but I get parse errors. Any clues?
Microsoft got rid of that for SSMS 2012, and suggested to use the integrated tools in WebMatrix instead (from memory, can't find a link for that sorry).
As suggested in that Microsoft Answers post, however, you could use the SQL Server Compact Toolbox, it's pretty effective.
Try using the SQL Server Object Explorer instead of the Server Explorer. That should allow you to do what you wish.

How to migrate TFS 2008 Project Version Control to TFS 2010?

I have Microsoft Team Foundation Server 2008 installed on my company since tree years. I installed TFS 2010 and I want to migrate the version control from 2008 to 2010.
I tried to use Team Foundation Server Integration Tools (March 2011 Release) but I've got an error/conflict when I tried to migrate:
The target server http://tfs2008:8080/
is not a TFS2010 server
I don't know why it says target and not source even I've putted it (tfs 2008) on the left source!!
Can anyone any idea what's going on?
Thank you and Kind Regards.
I was able to migrate from the tfs 2008 server, I ran the TFS integration tool from 2008 and it worked.