I inherited a project that was being built in VS 2019. After I finished building it and asked the requestor for clarification on how to handle a few scenarios I get a warning that the license for VS 2019 is about to expire. Turns out the project was running on the 30 trial license. The server is on a network that is isolated in such a way I can't use an MSDN account to sign in. We were able to get VS 2017 Standalone shell installed with data tools using the off line method. Now the problem is I have a 2019 project and dts package with 2017 tools. Is there a way to downgrade the project to 2017?

I am using Visual Studio 2017 (SSDT). I have several packages (about 50) I need to migrate to use the project deployment model (instead of package deployment). I created a new Project and added my first SSIS package. I converted the existing database connection manager to Project connection and everything worked fine. I then added my next package to the project. I can see 2 connection managers in the package. 1 being the existing Package connection and the other being the Project connection manager I just created. Since both connection managers point to the same database, is there a way I can just swap the existing package connection manager with my new Project connection manager so that I won't have to go into all the different tasks in the SSIS package and update them to use the Project Connection manager as this would be very time consuming and prone to error? I did some research and the best I could find was an article on updating the SSIS packages in a text editor by doing a find and replace. I'm hoping there is an easier more automated way of making the change within Visual Studio? Anyone have any suggestions? In case it helps anyone: Here's an article I found describing how to get around the issue by editing the SSIS XML I would have thought this could be done natively within VS without having to edit the package XML.

I am able to run an SSIS package from my machine without issue in Visual Studio 2017, but I am unable to run the same SSIS package on the same machine in Visual Studio 2022. I am running Windows 10 Enterprise 64 bit. The error message when trying to run the SSIS package in VS 2022 is: > Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine. The part of the SSIS package that fails is in a C# Script Task that is trying to open a connection to an excel file using the following code: string ConnectionString; ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + Dts.Variables["User::ExlFQFileName"].Value.ToString() + ";Extended Properties=\"Excel 12.0;HDR=No;IMEX=1\";"; var conn = new OleDbConnection(ConnectionString); I am not sure why the same SSIS package being run on the same local machine works when run in VS 2017 but not when run in VS 2022. I've tried installing the "*missing*" provider even though VS 2017 is apparently able see it and use it, but VS 2022 thinks it's missing (or can't see it?). I believe we have Office (Microsoft) 365 installed on our machines. My excel version is: Microsoft® Excel® for Microsoft 365 MSO (Version 2209 Build 16.0.15629.20256) 64-bit How can I resolve the error in VS 2022? Update: Using the link provided by billinkc in the comments, I was able to determine that VS 2022 is running the Script Task in 64 bit mode (where it doesn't work) and VS 2017 is running the Script Task in 32 bit mode (where it works fine). https://billfellows.blogspot.com/2015/02/is-my-ssis-package-running-in-32-or-64.html I've tried setting VS 2022 Run64BitRunTime to False but it still runs the script task in 64 bit mode. How can I force VS 2022 to run the script task in 32 bit mode like it does in VS 2017? Or should I try to update the script task to use: Microsoft.ACE.OLEDB.16.0 instead of Microsoft.ACE.OLEDB.12.0? Ultimately, I am just looking to get the package to run in VS 2022 like it does in VS 2017 regardless of the bit version it uses.

When working with SQL files in a VB.Net project, how can the connection parameters be saved for easier development? There are SQL files in the project, to hold queries for use in the app. When one of the files is opened for editing & testing, the credentials & properties must be entered again - every time! See screenshot below. Anything in the Connect and Advanced Properties windows is lost each time the file is closed. The credentials are very long, so they must be copied & pasted, and some connection properties need to be set. To redo these every time is annoying & inconvenient. How can the credentials & properties be saved in the project? (if possible) Sidenote: I do understand credentials should not be hard-coded into the project, so that need not be discussed. This is just for development, and eventually I will harden it up so the credentials will not be in the project.

This takes up [SSIS package with status running is not running - Stack Overflow](https://stackoverflow.com/questions/33889507/ssis-package-with-status-running-is-not-running) . SSIS project window turns white right at the beginning of debugging, status "Running": Right click closing cannot be done: And if I hover over the task bar icon, wait for the preview to pop up, and right click on the X of the crashed window, I can see the project again in the old window so that I can close the other window since I do not need it anymore: And you can see that the debugging has run through, everything green: And the whole run took just 3 seconds even though I waited minutes for the white window to go away: And the run is flawless, no warnings or errors in the Progress / Execution Results. This happens at every debugging. How can I get rid of this whitened project window of Visual Studio right at the beginning of running a container? PS: This is most likely not linked since I run into this too often, but who knows: at the same time, I also cannot change the size of any boxes in the Control Flow or Data Flow. The mouse cursor sometimes stays a double arrow after having tried resizing something, and even though it is a strange double arrow, I can double click into the boxes or click to rename things.

I have visual studio 2017. I have a script transform that I can run locally just fine, however when I deploy to the Integration Services Catalog on the dev server and run it, it fails with the following error: > 'package name':Error: Failed to compiled scripts contained in the > package. Open the package in the SSIS Designer and resolve the > following compilation errors. So, when I remote into the dev and rebuild the package, it will work fine on the next execution. I thought this might be a reference issue but after reinstalling Visual studio 2017 and SSDT the references are an exact match on both machines. What could be the issue for this?

I have an issue with an SSIS package, that when deployed via VS2017 to the integration services catalog is not actually being deployed. This is an individual package deployment, and not a project deployment. There are no error messages, and the deployment appears to go through fine. Checking the initial packages and projects tables indicates that although the deployment has happened (project timestamp gets updated), the latest version of the package code has not really been deployed as the version number on the packages table does not match the latest version from within Visual Studio. In fact, the issue is exactly as described in this previous post by another member, only there was no update on the resolution on that post. I'm hoping that someone else may have come across this situation. https://dba.stackexchange.com/questions/254079/why-is-my-ssis-package-not-getting-updated Some additional information that may assist: Right click, Project deployment - this works (we've tried this with another project, although for the project we're really interested in we cannot do that as not all the packages are ready for deployment at a project level). Right click, Package deployment - this doesn't work (deployment is reported as a success, but evidently the package has not been deployed). Calling the ISDeploymentWizard from the command line for the package in question doesn't work either. Again, no errors reported, but nothing deployed. When using the wizard via Visual Studio, the XML you can save post-deployment reports 'success' at all stages. Thank you.

my connection string: SqlConnection con = new SqlConnection("Data Source=ANUPAM-DESKTOP\ANUPAM;Integrated Security=True;Connect Timeout=30;Encrypt=False;TrustServerCertificate=True;ApplicationIntent=ReadWrite;MultiSubnetFailover=False"); But it is showing this error: What can I do now?

I'm attempting to install SQL Server Data Tools, but the installation is hanging. It had an error the first attempt; and I've restarted the machine (as that seems to help in those scenarios). Now it just sits there on the tools for Visual Studio not installing (I've left it running over night). Any suggestions on what to do here?

I have found out that there is a difference error (Remaining Qty (Purchase - Sales)) in one of the items in my database. There are more than 5000 items and more than 100,000 transactions has happened up to now. Same procedure runs every time for this calculation. But only a single item has an error and it has happened only one time. It does not seem to be happening from the application side since it has run for more than 100,000 times. The database server is not physically protected and does not connect to the Internet. Only I can log in to the server. No exceptions has happened in the procedure since I log the errors. I do not understand how the above error happened. I have seen that it's possible to open unencrypted SQL Server backup files using Notepad and read its data. Is the following scenario possible or not? 1. Boot the server using a live CD and copy the database .mdf file 2. Edit and change the data of it (Example: some numeric values) 3. Replace the original .mdf file on the server with a hacked database If the above scenario is not possible, is there a chance this has happened due to an error from the SQL Server side or through communication error (not from the application code side).

I'm looking for a way to move all our SQL Server databases (on one server) into source control. I tried creating a solution, and then adding VS database projects to the solution that correspond to the SQL Server databases. As I was creating the projects (via importing existing databases) I chose to import security objects. These security objects are users that need to reference logins of some kind. i.e. in a database project I have a folder Security with the SQL script: CREATE USER xxx. The VS debugger underlines this in red and warns me: > SQL71501: User: xxx has an unresolved reference to Login xxx. To fix this I tried creating a new project called SERVER, in which I would include server-related SQL files. - How do I reference this new project from the other database project?

I'm trying to (learn) publish a SQLCLR function using Visual Studio 2017. (It's a simple function that sends an email.) As a reference I used this articles on CodeProject and MSSQLTips : Create, Run, Debug and Deploy SQL CLR Function with Visual Studio 2013 Database Project Send Email from SQL Server Express Using a CLR Stored Procedure On project properties->SQLCLR I've set: Permission level : UNSAFE And according to the article I've updated target databases: sp_configure 'clr enabled', 1; GO RECONFIGURE; GO And after I've got the error I've followed this advice on MSSQLTips article: >If you get error messages when trying to compile the code you may need to alter the database using the following command and then try again to create the assembly and the stored procedure. ALTER DATABASE msdb SET trustworthy ON I've tried using two different target databases: - SQL-Server 2017 LocalDB - SQL-Server 2017 Express I can build the project without errors, but when I publish the project I receive one error when it executes the next command: CREATE ASSEMBLY [dbSysmac] AUTHORIZATION [dbo] FROM 0x5F8A900003000000... WITH PERMISSION_SET = UNSAFE; >(47,1): SQL72014: .Net SqlClient Data Provider: Msg 10327, Level 14, State 1, Line 1 CREATE ASSEMBLY for assembly 'dbSysmac' failed because assembly 'dbSysmac' is not trusted. The assembly is trusted when either of the following is true: the assembly is signed with a certificate or an asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission, or the assembly is trusted using sp_add_trusted_assembly. What I'm doing wrong?

I have downloaded and installed SSDT from Microsoft docs . The install was successful and I now have SSDT for VS 2017 installed - version 15.8.9 (as per screenshot) However, I cannot create an SSIS project. There is no option in SSDT to do so. When I try to open an old version of an SSIS package I get the below 'Unsupported'... What else am I missing?

I have a Visual Studio database project with several stored procedures. I deleted one of them and then published the project. But the SP was still present on the published database and I had to delete manually. I would want the VS project to be the point of truth for the database. But at the same time, I'm publishing to a production database that has data. Is there a way to delete files in a VS database project so that those changes reflect on the published database?

I am trying to connect to a SQL Server 2017 via Visual Studio 2017.What should I be entering in the User name and Password fields?

I connected R with SQL Server (in Visual Studio 2017) the connection succeeded this is Setting.R settings <- as.environment(list()) dbConnection1 <- 'Driver={SQL Server};Server= (local);Database=SaVeITDB;Trusted_Connection=yes' this is SqlQuery.sql also executing the below query succeeded -- Place SQL query retrieving data for the R stored procedure here select AOIName from AreaOFInterest a, ProjectsAOI p where p.AOIId = a.AOIId; and this is Script.R when I executing it throw this function in df file source("Settings.R") library(RODBC) conn <- odbcDriverConnect(connection = dbConnection) df <- sqlQuery(conn, iconv(paste(readLines('c:/users/comnet/source/repos/rproject3/rproject3/sqlquery.sql', encoding = 'UTF-8', warn = FALSE), collapse = '\n'), from = 'UTF-8', to = 'ASCII', sub = '')) View(df) this df file (appears with lock icon) function(x, df1, df2, ncp, log = FALSE) { if (missing(ncp)) .Call(C_df, x, df1, df2, log) else .Call(C_dnf, x, df1, df2, ncp, log)} **Edit** It's executing correctly without any error after run Visual studio as admin

It's possible to connect SQL server file (mdf) with R tool in visual studio 2017? I tried that many times but the connection failed. From visual studio2017, I want to connect R with Sql server database. I created R project then from R (tools--> Data --> Add database connection --> Attach database file) but connection failed.

I have installed VS 2017. After that I have installed SQL Server 2014. Whenever I create a DB using SSMS and attempt to create a table it returns the following error: > This backend version is not supported to design database diagrams or > tables. (MS Visual Database Tools). When creating the database using SSMS the compatibility level has no value to select from. Version of the SQL Server is 2017 and version of SSMS is 2014. How do I resolve this? As there any way to use SQL Server 2017 with SSMS 2014?

For the life of me, I cannot get the MySQL for Visual Force connector to work in VS. I just want to be able to add a MySQL database as a database connection in VS so I can build an integration. I have the community version of VS 2017. I have [followed the instructions listed on the MySQL website](https://dev.mysql.com/doc/visual-studio/en/visual-studio-preface.html) - I have tried the MySQL Installer as well as the standalone download. My first problems began because the MySQL installer would not recognize the installation of Visual Studio (even though I ALSO have 2013 installed!). So I uninstalled Visual Studio, the MySQL ODBC and .NET connectors, and I tried reinstalling them over and over again. Each time I would attempt to install the MySQL for Visual Studio connector, the installer would say that Visual Studio was not installed on my computer. So then I installed the connector by itself, BEFORE installing the ODBC or NET connectors and I got it to install. I still could not get the MySQL connector to appear when I tried to connect a new database to VS, though. Frustrated, I decided to create a User DSN (as opposed to a System DSN) and connect that way. It seemed to work, and I was able to see the connector in VS. However, now when I try to connect, I get "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". I [looked up the error](https://stackoverflow.com/questions/21395492/error-im014-microsoftodbc-driver-manager-the-specified-dsn-contains-an-arc) , and it appears that there is a mismatch between the x86 and x64 drivers. The problem is that I cannot find a x64 driver for MySQL for VS. I'm at the end of my rope. I just want to build out a package that will allow me to pull data from the MySQL and push to a SQL server. Is there a better way to do all of this, or am I on the right track? I would appreciate any assistance.

I want to move a .sln file to a directory above where it is currently located (because right now it's in a project directory, which isn't semantically correct). The project is called 'pName', and within the project there is a file pName.sqlproj.user. When i move the .sln file to the parent directory that same .user file is created. Why? is it due to which project is set as a startup?