I want to deploy mdf file with version 904 (sqllocaldb2019) on processor x86 but I cant find sqllocaldb 2019 foe x86, what should I do
SQL Server LocalDB is only available in x64 edition.
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.
Unable to start MongoDB 3.0.9,3.1.9,3.2.0,3.2.1 after installation on Windows 2012 R2 after installation. Continually receive APPCRASH errors. MSVCR120.dll c000001d.
Builds 2.7.9 and 3.0.0 do not experience the same issue.
You can resolve the issue by installing the 64 bit (or 32 bit) version of the Visual C++ Redistributable Packages for Visual Studio 2013. It can be downloaded from Microsoft:
https://www.microsoft.com/en-us/download/details.aspx?id=40784
I am upgrading SQL Server from 2008 R2 Standard Edition Service Pack 1 to 2008 R2 Enterprise Edition as per the instructions at Upgrade to a Different Edition of SQL Server 2008 R2.
In the past whenever I have upgraded software in such a manner, I had to re-apply the service pack.
Does a SQL edition upgrade require a service pack re-install ? The MS documentation doesn't talk about it.
select ##version
after the upgrade gives me
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011
00:54:03 Copyright (c) Microsoft Corporation Enterprise Edition
(64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
I don't believe the service pack needs to be re-applied - if you run the service pack setup it shouldn't identify this instance as a valid target since the ##VERSION is already at the SP level.
That said, why not just apply Service Pack 2 and Service Pack 2 Cumulative Update #1?
I want to design a report with new SSRS feature called tablix, but it seems I've previous version of SSRS installed because instead of tablices there are matrices, tables and lists.
Where can I get a newer version of SSRS? (I've already googled all over the web but have found nothing)
Installed prerequisites:
Microsoft SQL Server 2008 (SP1) -
10.0.2531.0 (Intel X86) Mar 29 2009 10:27:29 Copyright (c) 1988-2008
Microsoft Corporation Enterprise
Edition on Windows NT 5.1
(Build 2600: Service Pack 3).
Microsoft Visual Studio 2008 Version
9.0.30729.1 SP Microsoft .NET Framework Version 3.5 SP1
SQL Server Reporting Services
Microsoft SQL Server Reporting
Services Designers Version
10.0.2531.0
The answer was quite simple: I needed to install new version of ReportViewer.dll. After that everything worked perfectly.