I am having a problem with a SSIS project that downloads data from a MySQL database and insert it in a SQL Server 2014 Database.
So I have two versions of the same project, one for SQL Server 2016 and another one for SQL Server 2014. They have the same scripts and data flows, but for some reason, only the one made for SQL Server 2016 works. The issues resides in the ODBC Driver connector. I can preview data in both project, but for the SQL Server 2014 version, it simply won't load it. So I get 0 rows every time I run it. Sadly, I need the 2014 version for our SQL Server, since when I deploy the project with 2016 as target version, it fails.
This pretty much sum up the whole problem and I have try quite a few things. Including, changing the ODBC connector's version. It all seems it has something to do with Visual Studio, when the target version is change from 2016 to 2014. Still, I can't find a solution to this issue.
I am using a query to source data, but I also tried with the table name, but still didn't work. I am not using any function. I am running directly from Visual Studio in debug mode.
Has anyone gone through the same error? I can't find anything related.
Please, let me know if you need anything else to understand the issue.
Ok I had similar issue but it was in Source query where one of function was not behaving same between 2016 and 2014 version.
When you say 0 rows, does package failed or successful ?
Are you using a query to source data ? If yes, does it have any functions used ?
Are you running from BIDS or SQL Agent ? If Sql Agent, Check if agent job configured to run in same 32bit or 63 bit version ?
Related
Here's my current dilemma: I need to migrate the database, including the data, from SQL server version 13 to version 12. The source is on an Azure box and the destination is on my local box. I can't install SQL server 2016 on my local box; that isn't an option. How do I do this?
I would recommend you to use SQL Database Migration Wizard
Can you try using SqlPackage to Export the Azure database?
I've recently done the opposite of you, exporting SQL Server 2012 databases to Azure SQL V12. I used a combination of SqlPackage and Visual Studio with SQL Server Data Tools.
Basically I made a SQL Project based on the source databases (SQL Server 2012 hosted), set the target platform to Microsoft Azure SQL V12 and fixed any errors and warnings that wasn't supported in Azure SQL V12.
I then did a schema compare between the source database and the SQL Project. With this I generated a script which I ran against a copy of the source database.
Lastly I used SqlPackage to make a .bacpac from the database I ran the script against, which I could then deploy to Azure.
If you do the opposite maybe it'll work. It is important that when working with Azure SQL that you have updated software.
It seems that the answer is in insert scripts, which I didn't realize was a thing. There's good information at How to generate an INSERT script for an existing SQL Server table that includes all stored rows?
Edit: Another answer says NOT to generate INSERT scripts to copy all the data from a DB. I tried it and it seemed to fail because of some truncation in the script itself (it ended up being over 11 GB). A developer I'm working with suggested the bcp utility (documentation at this link), which I have not yet tried.
Is anybody else having an issue when they right click on an SP, and not seeing the option to execute the SP? Only option that I have is to script as execute. I am running SQL Server 2016 express.
Too long for comment!
I suggest that you back up the database now. Full and transaction.
Then check the Compatibility level. Change it back to your previous version of SQL server. Take another back up (to a new file!!).
Now did you upgrade the whole of SQL server or just SSMS? You could just install another earlier version of SSMS and leave the existing server in place and running, test to see if the functionality is all still there with the new (older) SSMS and the old (Ok most recently installed SQL Server).
Microsoft are doing monthly releases of SSMS so it is changing fast - which can mean bugs, but the server should be more stable, so the problem could just be a SSMS issue and your database could be fine.
New patch came out. It works wonderfully now. My issue was resolved. Thanks for the help...
I have created a database in SQL Server 2014 but I don't see it in Visual Studio 2013. I've been trying to figure this out for days to no avail. How can I use the database I created in SSMS in VS 2013? or how can I export it to be used in VS 13?
If I try to open the database from SSMS data folder I get an error. "you don't have permission ..."
But if I copy the .mdf file somewhere else and try to open it I get this error:
db cannot be opened because it is version 782. This server supports version 706 and earlier. a downgrade path is not supported
Any help would really be very much appreciated.
Thanks
Do you have the most recent version of SQL Server Data Tools (https://msdn.microsoft.com/en-us/data/tools.aspx)? I believe it's been updated since initial release to support SQL 2014.
Thank you all. I will leave the db alone where it is. I have SSMS 2014 and vs 2013. I thankfully did the following
" Try changing Tools>Options>Data Connections>Database Tools>Data Connections>SQL Server Instance Name. The default for VS2013 is "(LocalDB)\v11.0". Changing to "(LocalDB)\MSSQLLocalDB", for example, seems to work - no more version 782 error."
As from the above link(answer) posted by user1723033 and VikciaR and all is working for now.
Thanks again for your help.
The background to my problem is based on distributed computing. I want to have a database with some numbers in them and then a number of computers go through each row calculating another number (a little bit of an over simplification).
The problems I'm having are routed in my poor understanding of SQL servers (I think). I've got Microsoft SQL server 2012 (and 2008) installed on this machine and I've somehow managed to make a server for this task but then the problems arise.
I can't add a table to the server (I'm trying to do this in VS2010). When I expand the server and right click on tables and select add new table i get the following error:
"The server version is not supported. Only servers up to Microsoft SQL Server 2008 are supported."
That stops me making a table and from there I can't move on. I've downloaded and installed the VS2010 SP1 (and re-installed it again when it didn't fix the problem) as I found this suggested for similar issues.
Any help on this would be greatly appreciated. I've read around but nothing seems to work, people suggest using "SQL Management Studio" but I don't seem to have this installed!
Also, I haven't gotten to this step yet, but if this gets fixed any advice/links on how to access the database from a different machine (over the same local network) would be greatly appreciated!
Many thanks,
Fraser
R Harvey gave you the pointer to SSMS - that's the ideal tool to use.
As for other computers accessing your local database - the name of your computer (where MSSQL is installed) is the name of the server in your connection string.
My company is planning to migrate it's intranet/internet based ERP to the latest form of MS SQL Database available.
Presently we are using SQL Server 2000 Professional.
And we are planning to shift to SQL Server 2008 Web edition.
Please tell me whether this is the right step and whether it is feasible or not.
Thank you in advance.
"Please tell me whether this is the right step " - that's something you and your company need to decide.
It is feasible, and in the majority of cases straight forward.
Your first step should be to run the Microsoft SQL Server 2008 Upgrade Advisor
Microsoft SQL Server 2008 R2 Feature Pack contains the Microsoft SQL Server 2008 R2 Upgrade Advisor
Formulate and test a rollback plan
Determine your upgrade window and acceptable downtime.
Ensure database consistency: Run DBCC CHECKDB on databases to be upgraded to ensure that they are in a consistent state before performing the upgrade.
Back up all important files: Back up all SQL Server databases from the instance to be upgraded (including master, model and msdb), data and transaction log files, as well as any application files, script files, extract files, etc. so that you can completely restore them in the event of a failure.
It's both feasible and easy. The path from one version of SQL Server to another is usually pretty simple. Do you have any special stored procedures or reports generated in SQL Server that need to be rewritten/re-imported?
As far as right step - the question is, Why? If it's working, do you really need to mess with it?
If it's for intranet (some app for your internal usage) then consider using SQL 2008 Express edition. It's free and you can use it as an instance running along the full 2000 version. That way you will have some extra features from the full version.
But you have to know that applications running on SQL 2000 may not work on 2008 and they are even more probable not to work on 2008 R2.