I have a program that we distribute to our customer base that uses a SQL Server CE 3.5 database. We recently upgraded our VS from 2010 to 2012. Now I need to modify the database slightly. I understand that VS2012 no longer supports SQL Server CE 3.5, however to upgrade to 4.0 will take me a large chunk of time.
Is there any way to add fields to my EDMX manually? I am able to alter my database with a script but I would like my EDMX to match so I don't have to make more calls to my database.
I have tried adding the field manually, however when I make a call to that table I get an invalid column error. I had already added the field to the database file as well.
Open the project with the edmx in VS2010, replace it with a new one based on the updated database structure, open the project in VS 2012
Related
Visual Studio 2019
Excel 365 64-bit
Excel file has a single worksheet named raw_products
I added a Data Flow Task to my Control Flow
Added Excel Source to the Data Flow
Opened the Excel Source and clicked "New" to create a new connection manager.
Selected my Excel file (Noted that the Excel version changed from 97-2003 to 2007-2010 after I selected the file).
I selected Table or View for Data Access Mode and was greeted with the error:
No Tables or Views could be loaded
Could not retrieve the table information for the connection manager 'Excel Connection Manager'.
Failed to connect to the source using the connection manager 'Excel Connection Manager'
I went through and tried every version available and none would connect.
A quick search on SO shows that the fixes are anywhere from reverting to Windows 98 or reinstalling VS to installing 32bit or 64bit Access Database drivers.
The purpose of this task is to import the Excel file into my SQL database. If I use the SQL Import Wizard it works perfectly, and I actually saved it as a SSIS package and imported it into the package I'm working on now.
I've tried all the versions available in the connection manager, and I installed the 64bit Access Database Engine drivers (it won't allow me to install the 32bit since I have 64bit office installed). I tried changing the Run64BitRuntime option in the project properties.
I don't want to reinstall VS2019, it took me 4 hours to get it and the Integration Services installed!
EDIT: Against my better judgement I removed VS2019 and Integration Services. It took me almost 8hrs to get them reinstalled and for everything to work again since MS Visual Studio Tools were not removed or registered correctly.
I have reinstalled everything, rebooted at least a dozen times, and I am still having the same issue where it will not show anything. VERY frustrating since this is the most important part of the SSIS package.
You need to Connection manager:
One for the source (Excel) that you already added
One for the target/destination (SQL)
Do you have the second one with SQL? Can you test it if it is successful?
Once it is successful you will have list of tables and you can choose your target table from the list if it exists.
I have multiple Azure SQL databases. One database holds all the staging table and the other database holds all the fact/dim tables. Now in my development environment I have stored procedure which reads data from staging tables (from staging database) and loads the data into its respective fact/dim tables (in a different database).
The above scenario is all working fine. I have multiple SQL projects for each database.
Now how do I deploy the elastic database queries while deploying the dacpac?
Below is the error when I add the elastic queries as a part of my post deployment scripts in Visual studio and try to build it.
PS: The SQL project properties is set to target the V12 version of the Azure SQL Database
Which version of the SQL Server Data Tools (SSDT) are you using? If you are not using the latest (14.0.60413.0), give it a try to upgrade SSDT: https://msdn.microsoft.com/en-US/mt429383. With that version, I am now successfully able to compile and publish database projects and dacpacs.
To successfully build, you will need to install the latest SSDT Preview which includes support for these objects from here. Support for the latest Azure SQL DB and SQL Server 2016 features is only available in the Preview for VS2013 at present, whereas for VS2015 the support was shipped in VS2015 Update 2. Once SQL Server 2016 goes GA (June 1, 2016) an RTM update will be pushed through the Visual Studio 2013 Extensions and Updates channel containing this support. That will ensure you get monthly updates with the latest changes again.
Note that even with the latest bits, if you open the file itself you'll get an issue with the Intellisense parser. Building the project will work fine but on opening a document you will see the errors appear for that specific document. Note that the same issue occurs in SSMS when coding this into a query window. This is because the Intellisense parser is separate from the core build system. The fix for this is in progress and will land in a post-SQL Server 2016 update (likely late June - July timeframe).
Disclosure: I work on the SQL Server tools team.
Why is SQL Server Compact not available from within a Web API project when right-clicking the project's "App_Date" folder and selecting Add -> New Item... -> Visual C#" -> "Data?
According to this tutorial on adding a database to an ASP.NET Web API project, there should be, not only these options there:
SQL Server Database
XML File
XML Schema
...but also "SQL Server Compact 4.0 Local Database"
Yet I only have those first three available. Why?
The tutorial linked to above was written on on May 30, 2013, and it specifies Visual Studio 2012 whereas I'm using Visual Studio 2013. Did "SQL Server Compact 4.0 Local Database" get dropped in VS 2013?
If not, how can I restore SQL Server Compact to the selection of available options?
Yes, SQL Compact Local Database was removed in VS 2013, but you can use the Sql Ce Toolbox to manage your database, and manually include a SQL Ce file in your web app.
I'm developing a Windows CE Mobile Application and using SQL Server Compact Edition as database server. However, I cannot drag and drop database tables from Server Explorer to a form's design view. It simply doesn't respond the drop. What could I be missing? I reinstalled and repaired everything. One note that I was able to do this operation a while ago. I also tried creating another database file and dropping tables of the famous Northwind.sdf.
Another thing is: I cannot generate a new data source within my project. When I try that the following error appears:
An error occurred while creating the new data source:
An error occured while generating the data source.
The problem couldn't be solved any of the suggested operations, but the following one.
Start the Visual Studio from the command line:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe /resetskippkgs
And everything works just fine.
Problem
I can't figure out how to ignore users in my vs 11 beta sql server db project when publishing.
Why is this a problem
This is a problem because I want to keep the setting where I want to drop objects that are not in my project but are in the db being published to. If I delete a sproc in my project I'd like to drop the sproc in my db.
Any ideas? I've looked at all of the publish settings and just can't seem to figure it out....
Encountered this as well, since it persists in Visual Studio 2012 RTM / SP1 with SSDT (SQL Server Data Tools). I reached out to Barclay Hill at Microsoft who works on the product, who confirmed that this is currently not possible:
It is frequently asked for i.e drop everything, but users, permissions
and roles. We have it on our backlog, but have not been able to get
to it yet.