SSIS with SQL 2014

I have recently installed SQL2014 and currently have 2 issues which may be BIDS 2012 or SQL2014 related.
1. If I deploy a package to MSDB, then try to re download and open the package in BIDS it complains that it cannot open a version 8 package in Version 6 studio. How do I overcome this?
TITLE: Microsoft Visual Studio
Error at Extract_NHP []: The version number in the package is not valid. The version number cannot be greater than current version number.
Error at Extract_NHP []: Package migration from version 8 to version 6 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.".
Error at Extract_NHP []: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">8</DTS:Property>" from node "DTS:Property".
ADDITIONAL INFORMATION:
One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.
One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.
BUTTONS:
OK
2. I have a flat file source on a SQL2008 R2 database that reads in and successfully processes a csv file which has double quotes as text qualifiers. If I run the same package in BIDS2012/SQL2014 it fails due to not being able to read the file. Now I know
the row below has some qualifiers in it but 2008R2 seems to load it and not fall over and puts '\"Spelga Lodge\" 3 High Street' into the second column of the table. Why does
BIDS2012/SQL2014 not cope with it?
Error: 0xC0202055 at Data Flow Task, Flat File Source [17]: The column delimiter for column "street_name" was not found.
"id","street_name","post_town_name","county_area_name","outcode","incode","type","type2","status","price","item1","item2","item3","item4","property_number"
"515370","\"Spelga Lodge\" 3 High Street","York","","","","ABCD","","Y","1234567","0","4","0","0",""
Regards
David

Hi David,
As discussed above, a SSIS 2012 package format package will be upgraded to SSIS 2014 package format once we deploy it to a SSIS 2014 environment (MSDB or SSISDB catalog). Once the package is upgraded, it cannot be downgraded. Besides, a package
created in a higher version of SSIS cannot be opened in the BIDS/SSDT shipped with a lower version of SQL Server.
So, to edit the SSIS 2014 packages, you need to install the
SQL Server 2014 SSDT-BI for Visual Studio 2013 which is the native SQL Server Data Tools for SQL Server 2014. However, the SSDT is temporarily offline because of some compatibility issues. Temporarily, you can install and use the SQL
Server 2014 CTP2 SSDT-BI for Visual Studio 2012. Both of the two SSDT are for SQL Server 2014 BI development.
Regards,
Mike Yin
TechNet Community Support

Similar Messages

Backup Sharepoint 2013 SP1 Farm with SQL 2014 RTM "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 SP1 Farm with SQL 2014 RTM "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find information anywhere.
Regards,
Igor

This is a DPM supportability issue, I believe. Last I heard, no it was not supported. SharePoint 2013 does not support SQL 2014 until the April 2014 CU. The CU should be out soon, although it appears to have been delayed (usually comes out on Patch Tuesday,
which was this past Tuesday).
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SCOM database compatibility with SQL 2014

Hello Experts,
We are finally upgrading from SCOM 2007 R2 to SCOM 2012 R2. Currently we have our DB's on SQL 2008 R2. I would like to know if the SCOM DB is compatibility with SQL 2014.
Thanks in Advance.
Regards,
Prajul Nambiar

Hi,
With UR5 SQL2014 is now supported
Support for SQL Server 2014 with System Center 2012 R2 Update Rollup 5
http://blogs.technet.com/b/systemcenter/archive/2015/02/23/support-for-sql-server-2014-with-system-center-2012-r2-update-rollup-5.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SSIS Development SQL 2014

I've searched and read that SQL Data Tools is gone in SQL 2014. It seems as though it's been replaced, and is currently pulled, by a plugin for VS2013.
My question is this; is SQL Server 2014 not a complete product any longer? I don't have VS 2013, so what am I supposed to do? I need to develop/modify my SSIS packages and we're about to migrate to SQL 2014. I can't believe all the tools
I need no longer come with the install of SQL 2014 - this is extremely disappointing.
Thanks in advance
André

Hi Andremg,
To do SQL Server Business Intelligence development, you don’t need to install Visual Studio. The specif version of BIDS/SSDT just uses specific Visual Studio shell, and can be integrated into the corresponding Visual Studio. The BIDS/SSDT is a different
product and works independent of Visual Studio.
Since the relase of SQL Server 2014, the SQL Server Data Tools used for Business Intelligence development is not shipped with SQL Server installation. To get the SSDT-BI Tools, we need to download it from the Micrsoft Download Center manually.
Currently, there are two versions of SSDT-BI Tools avaiable for SQL Server 2014 BI development:
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013
Microsoft SQL Server 2014 CTP2 Data Tools - Business Intelligence for Microsoft Visual Studio 2012
Actually, the SQL Server Data Tools - Business Intelligence (SSDT-BI) for Visual Studio 2013 is the native SSDT for SQL Server 2014 RTM. However, it is not available in the Download Center due to some compatiblity issues currently. So, we can temporarily
use the SQL Server 2014 CTP2 Data Tools - Business Intelligence for Microsoft Visual Studio 2012 for SQL Server 2014 BI development. Once the SSDT-BI for Visual Studio 2013 is back, we can install it and use it instead.
Besides, please understand that BI projects created in SQL Server 2014 CTP2 SSDT-BI for Visual Studio 2012 can be opened and eidted in SSDT-BI for Visual Studio 2013 without any problems. So, we don't need to worry about the continuity of the BI development.
In addition, as Kieran said, SSDT-BI Tools is a client tool and seldom installed on a production server.
Regards,
Mike Yin
TechNet Community Support

Sharepoint Foundation 2010 compatibility with SQL Server 2014

Due to a requirement to use Sharepoint without Active Directory access. I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014. I have seen that Sharepoint Server 2010 and 2013 are compatible
with SQL Server 2014 as of CU 1 (released in April). But there is no mention of Sharepoint Foundation.
This chart is great except it doesn't mention whether the Foundation versions are supported.
http://msdn.microsoft.com/en-us/library/gg492257.aspx
Thanks.

Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
supported at all with SQL 2014 as a Database Engine.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Best practice configuration for SQL 2014 to achieve HA when hosted on Hyper-V 2012R2 cluster

Hi,
I've had a hunt around but so far I've not found a conclusive answer to my question. I am currently moving from a SQL 2008R2 (physical tin) failover cluster to a virtual environment build on Hyper-V 2012R2. I am building everything with SQL 2014
SP1.
I want to achieve the same level of high availability that I currently have and at the same time make sure that I can replicate (DR) data offsite (Azure) in the future. I have two options with SQL which are clustered instance (basically the same as
I have now) or AlwaysOn Availability Groups for database level HA.
I am unsure which is the best method to use when the SQL nodes are highly available guests on Hyper-V, trying to imagine how the guests will all move around in the case of a host server failure is a bit mind boggling to say the least.
I am leaning towards a instance failover but I would appreciate any input/advice etc.
Thanks
Rob

Hi Rob,
To start with I will not be installing SQL Server 2014 with SP1, as SP1 has bugs and Microsoft has disabled its download. See reference: http://www.eweek.com/database/microsoft-halts-sql-server-2014-sp1-downloads.html
With regards, I would go for AlwaysOn Availability Groups configuration, because it has several benefits:
You will get same amount of high availability you normally get with native cluster configuration, if you use AlwaysOn configuration. However, AlwaysOn configuration provides more granular high availability, and fail-over are invisible to the application,
if you using Availability Group listener to connect to server.
You can offload read-only workloads to secondary replica.
You can perform transaction log backups on secondary replica.
Reduce production downtime during patching or other planned work on the server.
So in short, you should use AlwaysOn configuration.
Regards,
Basit A. Farooq (MSC Computing, MCITP SQL Server 2005 & 2008, MCDBA SQL Server 2000)
http://basitaalishan.com
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Can't update SQL 2014 DB during web publish from Visual Studio 2013

According to Visual Studio 2013 I have "SQL Server Data Tool 12.0.40706.0" installed, which should allow me to update a SQL 2014 database but when I try to publish my web application I get the error: "Web deployment task failed. (Could not
generatedeployment script. Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database
platform service. Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service isloaded, or you must provide the full type name of a valid database platform
service. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.)" I can update the database fine if I go into the package managment console and run -UPDATE-DATABASE but I don't want to have to go into myweb.config, update it to point to the production
database, run the update command, and then change my web.config back everytime I try to update my database. What do I have to do to getthis working? I had no problems when I was on an Azure DB.

Actually problem seems to be related when web publish to remote server. I tried local web publish to sql2014 db and it works.
For remote server web publish works to sql 2012 express db but when try with sql 2014 express db on same server get bellow error.
Error message "The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider
is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service."
Any ideea what may be causing it? I have installed the sql server 2014 express with advanced services x86, exact same version as on my local machine, and also restarted server after install. Need install/configure anything else on server like SSDT 2014 to
make this work?
Cheers!

SQL 2014 RTM and Sql 2008r2 standard side by side installation ..

We are planning on reconfiguring our database server and then installing SQL 2008 R2 Standard edition in a side by side installation with SQL 2014 RTM. I have researched a little, and have not seen any major issues when planning this type of configuration.
Are there any issues that may occur with this?
2008 R2 will be in the default instance, and 2014 will be using a named instance. We do foresee uninstalling 2008 R2 after a period of time, and moving all of our databases to 2014 after testing has been performed. Once we uninstall 2008 R2, will we be able
to install a default instance of 2014? Are there any special steps that need to be taken to do that?

Hello,
If possible install the SQL Server 2008 R2 instance first, then install SQL Server 2014. Through the years, the formula
of installing the older versions of SQL Server first has proved to be a winner for me.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2014 Cluster to Cluster protection

Hi,
I got 2 physical servers in Cluster with SQL 2014 on source site and same environment of two physical servers on target site. I want target cluster to protect target source. The site are remote from each other. How can I do replication and FO & FB? Can
always on protect source cluster to target cluster? can it monitor and do FO to remote cluster. Both cluster on the same domain.
Thanks
Erez

Please check Symantec Backup Exec 2014 it works with CSV.
remove the CSV from the failover cluster manager and then try to point the tool and see if it is able to see the volumes without CSV.
http://www.symantec.com/business/support/index?page=content&id=TECH205833
Hope this helps.
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

SQL 2014 Issues

I have setup SQL 2014 for my DB server, however the pre-requisite check is failing. When I checked the compatibility on TECHNET, 2014 is listed as supported for SCCM 2012 R2. Can someone let me know if there is a patch that's needed.
Thanks in advance

ConfigMgr 2012 R2 are supported with SQL 2014.
Just use the 3020755 hotfix.
More info:
https://stevethompsonmvp.wordpress.com/2015/02/11/configmgr-2012-r2-support-for-sql-server-2014/
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Moving SCCM 2012 R2 SQL 2014 Database to New Server

Greetings,
I have a SCCM 2012 R2 server with SQL 2014 installed which has been upgraded from SQL 2008 R2. My goal is to separate the SCCM and SQL servers. I am aware that SCCM only supports SQL 2014 if it has been upgraded on new installs, but after installing
SQL 2014 on a new server and importing the database I get an error from the Configuration Manager Setup stating that I must upgrade the SQL server before I can modify the SQL Server configuration.
Does this mean I need to install SQL 2008 or 2012 on the new DB server and from there upgrade to SQL 2014?

Thank you for your reply. We have been having several issues with our current server, and have had performance issues with SQL and SCCM installed on the same server mainly during OSD deployments to several machines at the same time. These servers
wouldn't necessarily need to be separated since we can allocate more resources, but the overall goal is to move our primary site server to a new server running Server 2012 R2 (current server is 2008 R2).
I have tried the site recovery option in the installer where you run the SCCM backup and restore maintenance task and I have renamed the new server to the name of the old server. If I understand correctly, this is the correct method of switching out
a site server machine? I experience the same error as my original post when trying this, but I will try the hotfix Torsten provided as this seems to be the issue I'm having.
Thank you.

Upgrade DTSX packages from VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014

Hello everyone,
I’m very new to SSIS world. I’ve been assigned a task to upgrade the existing packages running in VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014. And then submit the migration report to my client.
On very quick search at Google, I've found the following link. It seems like I just need to open the existing SSIS project in VS 2013 and follow the wizard.
https://msdn.microsoft.com/en-us/library/cc280547.aspx
Can anybody please advise, are there any other things need to be taken care while doing this up gradation process?
Please share your experience.
Any help would be much appreciated.
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Hello Arthur,
Thank you for the response.
I just got an access of the packages. They are of VS 2008 and not 2010.
Do you know how to upgrade VS 2008 packaged to VS 2013?
When I tried to open the solution file in VS 2013, it says "incompatible".
Any help would be much appreciated.
Thanks,
Ankit
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
Lpd

OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd

DB-Library BCP issue with SQL Server 2014

Hello,
My application uses DB-Library (ntwdblib.dll) to communicate with SQL Server 2014. We are having issues calling bcp related functions like bcp_init which always returns FAIL status. Our application was working fine with SQL Server 2012 and all other previous
SQL releases. But we are getting below error in SQL 2014,
msg 4801, state 1, severity 16 : Insert bulk is not supported over this access protocol.
Can anyone please help ?
Thanks,
Himanshu

Hi Himanshu_kus,
Is this still an issue, or can we close the thread?
[Personal Site] [Blog] [Facebook]

SSIS error authenticating proxy with SQL Agent

Hello,
I'm a BI Analyst (not DBA) and I've asked our IT department for access to SSIS and SQL Server Agent to deploy packages to import data from Oracle nightly and transform it into a dataset in SQL Server 2012 using SSIS.
I've written several packages, deployed these to a SQL Server. These run fine when ran locally through Object Explorer > Integration Services Catalog > SSIDB by right clicking/execute.
However our DBA has set up an SSIS Proxy that I can use in conjunction with SQL Server Agent to run these packages. However, when I try to use this proxy I get the error message:
'Unable to start execution of step 1 (reason: error authoenticating proxy ad\[name removed], system error. The username or password is incorrect. The step failed.'
I've tried packages with security for 'dontsavesensitive' and 'encryptsensitivewithuserkey' but neither work. I'd like to rule anything out that I'm not doing, however I think it is a permissions issue (happy to be proven wrong though).
Can anyone offer suggestions for next steps please?
Thanks,
ZP

Hi V,
Thanks again.
I went to the general tab and it is all greyed out and the credentials box is empty - though I can click on the button with three dots on. However, it just takes me to a credentials form but doesn't give me any options to select from. The box for SSIS is
ticked though.
It is all greyed out - I presumed this is because I haven't got permissions to set what the proxy can do?
I tried select * from sys.credentials - didn't return any information (zero rows).
I'm (mostly!) convinced the packages are fine - I've created several simple packages to demonstrate the same thing to our DBA and these simple packages all run fine when executed directly through SSMS but never work through SQL Agent with SSIS Proxy. His
thinking is that its because I need to run them with security as 'dontsavesensitive' but these dont work either.
Do you know if I should be asking for a specific permission/credential?
Thanks!

SSIS with SQL 2014

Similar Messages

Maybe you are looking for