Trying to import data into a new database with SQL Server Management Studio's Import and Export Wizard.Shows an error below:
Warning 0x80049304:Data Flow Task 1: Warrning: Could not open global
flow performance counters are not available.To resolve, run this
package as an administrator, or on the wywtem's console
Please tell me what should I do? Thanks
(SQL Server 2012 64 bit, Windows 7)
To resolve, run this
package as an administrator
, or on the wywtem's console
personally I think you should try this first. Then if that fails - tell us what it says.
Related
I am trying to import a DB in the Azure Portal. The original DB I exported from was on a different server, but is setup identically to where I am trying to import. I am importing by going to the target server and clicking the import button. I then choose the storage account, container, and bacpac file I would like to import. I check that the database size and type are the same for the import as the bacpac file. I also double check that the collation is the same on the import as it is in the bacpac. I then confirm. It attempts to do the import for about 20 minutes before giving the error message below. I can see the DB is created when I go to the sql server and click the sql databases blade, but the tables inside the DB are empty.
Could not import package.
Warning SQL72012: The object [data_0] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.
Warning SQL72012: The object [log] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.
Error SQL72014: .Net SqlClie
I have seen some responses in regards to similar issues, but they all seem to be using SSMS. Does anyone have any ideas on how to fix this issue inside the Azure Portal? Also, does anyone know what check box they are talking about? there is no checkbox when I am doing the import setup.
The warnings you are getting are a bit of a red herring. The issue is with the error you are getting. The line you posted only shows a generic error which should be followed by the actual error after. Try going to the actual database server and check import\export history.
try also importing using powershell which may give you some more details on the error you are getting:
$importStatus = Get-AzSqlDatabaseImportExportStatus -OperationStatusLink $importRequest.OperationStatusLink
[Console]::Write("Importing")
while ($importStatus.Status -eq "InProgress") {
$importStatus = Get-AzSqlDatabaseImportExportStatus -OperationStatusLink $importRequest.OperationStatusLink
[Console]::Write(".")
Start-Sleep -s 10
}
[Console]::WriteLine("")
$importStatus
Without knowing what the error you are getting it's a bit of a stab in the dark trying to guess what the issue is. Giving the version of SQL you are exporting from I can guess this is an on prem database server.
One of the common reasons dacpac files tend to fail when importing is your source database server isn't configured to allow contained databases
If that's the case, you need to go to your source database server (where you are exporting from) and enable that option:
sp_configure 'contained database authentication', 1;
GO
RECONFIGURE;
GO
Once this is run, recreate your dacpac file and try to import that.
As I mentioned, this is a complete stab in the dark as you haven't provided the error you are actually getting
I am trying to make SQL Server 2014 my data persistence provider as per the instructions provided at http://support.ptc.com/cs/help/thingworx_hc/thingworx_6.5_hc/index.jspx?id=ConfiguringaPersistenceProviderEntity&action=…
but unfortunately, I am not able to do so. I get an error message (please see attached screenshot). How can I solve this error?
Also when the instructions say import the PersistenceProvider package what exactly the instructions mean by that?
Error screenshot
No need to add an extra Persistence Provider, since the installation package already made MSSQL as the default persistence provider while installation.
I'm using the GA Analytics data source for Data Tools 2012. I'm able to log-in and use the component within an SSIS package, debug and run the package, fetch and load data (to OLE DB target). No problems!
But when I try to deploy the package to SSIS Catalog on local or remote servers, the package throws the following validation error: "Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData100'. This operation failed because the QueryInterface call to the COM component for the interface with IID '{887BD061-82D4-4F06-A222-33D4E7F896}' failed due to the following error: No such interface supported"...
I've made sure to isolate the problem down to it's core. I've created a package with only the GA data source on it, and ran into the same issue. I have no problem deploying or executing any other ssis packages / components.
Aside from deploying the SSIS Package to the SQL Server SSIS Catalog, I've also tried to run the Execute Package Utility 2014 to run the package. I run into the same validation / execution error as listed above.
The only way I can run this package now is to run it in debug mode through VS / DT 2012 - Manually!
Also, I feel like maybe the components OAuth session is being lost upon deployment.. and if it isn't.. I don't know how I would otherwise reset an OAuth connection for GA data source on a remote server (without having a VS/DT installed)..
Can anyone please help shed light on this issue?
What is the proper deployment strategy for packages containing the GA SSIS DataSource?
What would be an alternative and effective way to schedule such a package on a production server?
Is there a known fix for this issue?
I had the same issue. As it turned out I was using VS2012. The GA loader on VS2012 is compatible with MSSQL2012. To use the loader on MSSQL2014 you will need VS2013.
Hope this helps!
I just installed SQL Server 2014 and now I'm trying to import an Access database. To do the import I use the SQL Server 2014 Import and Export Data Wizard. I can go trough all steps of the wizard except the step below, which gives me this error.
The red underlined text is Dutch the translation for this line is: Cannot read the records. U don't have permission for tblAanmaningHistorie to read the data.
tblAanmaningHistorie is the first table in the Access database, when I try to import other tables I get the same error.
Data source screen
How to fix this?
I have an SSIS Package that I created through the Import Export (32-bit) Tool. When I executed the package manually through the Execute Package Utility the package run successfully with no issues. However when I try to run the package through a Job Agent in SSMS I keep getting errors. The primary error I get seems to be:
Failed to decrypt protected XML node "DTS:Password" with error
0x8009000B "Key not valid for use in specified state" You may not be
authorized to access this information. This error occurs when there is
a cryptographic error. Verify that the correct key is available.
I'm using SQL Server 2008 R2.
I have researched this error to some degree and I think it has something to do with the package protection level. I feel like I've tried the configurations that make the most sense but none seem to be working for me. The Options are:
Encrypt sensitive data with user key
Do not save sensitive data
Encrypt sensitive data with password
Encrypt all data with user key
Encrypt all data with password
Rely on server storage and roles for access control
I feel like Ishould be using the last option here (Rely on server storage...) because I prefer to use SQL Server Authentication. I use SQL Server Authentication on the 'Choose Destination' window of the SQL Server Import and Export Wizard, and similarly I use this with the same username and password when I create the Job Agent in SSMS on the General Tab of the Job Step Properties. Is it possible that there is something that I need to add to the User I'm using in SSMS - even though it works outside of SSMS?
Something else I wondered that might have an impact is having the option "Drop and Re-create destination table" checked in the Column Mappings window of the Import and Export Tool. I was using a stored procedure to remove the tables before executing the Job Agent and I feel like ti was working at one point - could that have something to do with it?
Again the thing that baffles me most is that it runs no problem when I execute it manually through the 'SQL Server Execute Utility Package' tool.
I've included images of some of the windows I mentioned above if that helps.