I am trying to export an SSIS project from the Integration Services Catalog and am getting an error:
The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Windows Authentication. (Microsoft SQL Server, Error: 27123)
I am connected to SQL Server using SQL Authentication and the sys admin account. I don't have a login with which to use Windows Authentication. How can I export the project and packages to my local drive?
Right Way
You can use DTUtil Utility to perform these operation.
You can found helpful information at the following Links:
Script To Export All DTS Packages ON IS To File System
http://www.bimonkey.com/2010/01/ssis-command-line-utilities-part-1-dtutil/
Workaround
I know this is not the right way, this is a workaround:
Open a new Integration services project in visual studio
On the solution explorer tab add an existing package from sql server using your sql authentication
Related
I am attempting to deploy an SSIS package on a remote SQL Server by following the following tutorial. My issue is that the Integration Services Catalogs folder is empty and when I try to create a catalogue, I get the following error:
The path to the catalog backup file could not be determined.
Integration Services might not be installed on this server, or the user may not have the appropriate access permissions
Is it even possible to achieve my goal on a remote server or do I absolutely need access to the machine on which it is running on?
Once SSIS is installed on the server, you can create the SSIS catalog and deploy SSIS projects to the catalog remotely.
I've deployed an SSIS project using the "SA" account to my SQL Server. When I run a package from the SQL Server I am getting the error saying I need to use Integrated Authentication. I corrected the problem in Visual Studio (I changed it to use Windows Authentication) and the packages work fine there. When I redeploy them to my SQL Server, the authentication method didn't change. It won't even let me delete the packages or the project on SQL Server giving me the message that I can't delete using SQL Server authentication. How am I supposed to update the authentication method?
I am finding SSIS so problematic that I'm considering just replacing my data transfer packages with a C# program.
I had to shut down SQL Server Management Studio and then open it using Windows Authentication instead of SQL Authentication. All works now.
I have one database in azure and accessing in my SQL Server Management studio and try to export the database but gives me the errors.
Here are the steps I have done:
1) Export data-tier Application
2) No of errors I got
3) Got this error in all the processes:
I am using SSMS (2014 and 2016)
Try downloading the latest version of SQL Server Management Studio in order to have the best user experience with Azure SQL Database. Please download it from here
That dss schema means you were using SQL Data Sync. You may need to use the deprovision utility to clean that remnants left by SQL data Sync.
Alternatively you can use SQLpackage, PowerShell or Azure Portal to do the same task. You can learn more about it here.
SqlPackage.exe /a:Export /tf:testExport.bacpac /scs:"Data Source=apptestserver.database.windows.net;Initial Catalog=MyDB;" /ua:True /tid:"apptest.onmicrosoft.com"
I'm trying to move my databases to a newer Azure subscription. I used to simply click "Deploy to Azure" on a local database from SSMS and have it deployed to a specified Azure server. Importing/Exporting a BACPAC file also works. However, I can't seem to do any of this on the new server. I keep getting the error:
"The service objective 'Web' specified is invalid."
Googling around, I found this thread explaining the need to update the CREATE DATABASE template to accommodate Azure Databases (Azure upgrade, I'm guessing). However, the hotfix provided is specifically for SQL Server 2014 and I'm using SQL Server 2012. I checked other cumulative updates for 2012 here but found no fix for the issue.
Is there any other way I can fix this without having to upgrade to 2014?
Just to summarize my software versions:
SQL Server 2012
SQL Management Studio 11.0.2100.60
Local database: SQL Server 10.50.16000
Old Azure server: SQL Server 11.0.9230
New Azure server: SQL Server 13.0.15
You are getting this error because the latest V12 servers are not supporting the Web and Business Editions anymore. If you don't want to upgrade to SSMS 2014, you can create a V11 server and import your DB on this server. However this is only a temporary solution as Web and Business edition databases will be retired in September. At this point you will have to work with the latest tools to avoid this problem.
There is a Hotfix for it you can download and install on your machine. Please navigate to:
https://support.microsoft.com/en-gb/kb/2936603
You need to enter your email then download link will be sent to your email address. Then install it on your machine and you can see the following options:
Install the database as a Data Project into Visual Studio,
Set the target framework in the properties window to SQL Azure,
Build the project and resolve any unsupported issues.
Publish to your azure site.
I have tried the above and did not work for me - this solution worked!
I've created my first database based desktop app in .NET and not able to understand how can I deploy the database with the application installer, so that the database, application and the SQL Server is installed in one go.
If I only deploy the native client for SQL Server and the database with the installer, will it work?
The application uses the database very frequently.
You need to install the SQL Express engine if you want to use it. Deploying only the client connectivity will give you exactly what the 'client connectivity' name implies: you'll be able to connect to a SQL Server. But only a running SQL Server instance will be able to read/write your application database.
The SQL Express install MSI is actually very customizable and allows for a lot of scenarios, including unattended setup and remote deployment. For the most basic options, see Configuring SQL Express During Installation. Your application installer will have to invoke the Express installer passing in the desired parameters.
Using click once you can make sql server express a dependency of the main project and it would be deployed with the instalation data and installed, if it is not instaled yet, when you first install your app.
You can do it in the project properties, in Visual Studio.