Is there a way to export data from couchDB to Sql Server ?
We tried with SSiS using http connection manager, JSON component source etc. But the problem is that couchDB has some security and we can't retrieve data info. We tried installing their certificates no success.
Any other suggestions?
CounchDB has a number of .net client libraries you can use. I would get that working in a console app and then just write that to a csv on the disk and use SSIS to import it.
If you don't want the additional step you could write a .net script source component that used the .net client to retrieve data but get it working in a console app first so you know it is good before bringing SSIS into the equation.
Getting started with CouchDb and c#:
https://wiki.apache.org/couchdb/Getting_started_with_C%23
ed
Related
I've been trying to get the File System Endpoint to work for a migration I'm working on and so far have been unsuccessful getting the configuration to work right.
Situation: We have a Azure DevOps Service instance that contains our work items and we are now directed to migrate these work items to an instance of Azure DevOps Server that is in an "airgapped" environment. So the plan is to export the workitems via the FileSystemEndpoint and then run the reverse on the private environment.
My ask is has anyone used the FileSystemEndpoint for either export or import outside of the Tests?
I m using blazor server app and importing large files. During import operation service will be logged errors and warnings. Users want me to show logs real time.Should I use Signal-R. Because I needed updates one way.
I'm using pentaho BI server 7 EE.
I have uploaded a simple transformation (.ktr) and run it successfully throught PUC.
But when I try to call it throught REST service (http://localhost:8080/pentaho/kettle/runTrans?trans=%3Apublic%3Ademo%3AsimplePdiJob.ktr) it fails with the following response:
<webresult>
<result>ERROR</result>
<message>!RunTransServlet.Error.UnexpectedError!</message>
<id/>
</webresult>
I didn't find any exception in the log.
What can be the cause of this problem?
Thanks
Hi I do not know if you still have this problem but I managed to solve it these days doing an xaction and inserting in the in the XML code that I inserted a PHP script that made the call of my .ktr file and uploaded to the server a file Csv that was with which I would perform my ETL. I know that is not the best solution but for my case there is no way even in version 7 of bi server to upload csv files or some other extension.
I'm sure this has been answered before, but every example I try I can't seem to connect to my SQL Server.
I'm using SQL Server 2014, and the webpage is being hosted in IIS on Windows 7 x64.
I'm trying to get my webpages to build themselves recursively from information in a database, I've configured IIS to run ASP pages (I believe its classic ASP as opposed to ASP.net, but I may be wrong)
I started by looking at examples that basically returned all entries in in a particular column in a table, however when i got error messages on trying to load the page:
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.
I tried stripping it down to bare minimum, i.e. just opening the connection to the database.
And even then I get the same error, here are a few of the examples I tried:
Example-1
Example-2
Example-3
Firstly if anyone could tell me how to debug it further, i.e. getting proper error messages that actually tell me something useful, that would be a good start.
If there's any information I missed then please ask.
If you've given your files the extension .asp then it is Classic ASP
Do you know what version of SQL Server you're using? If it's express then you need to say so in your connection string eg Data Source=yourserveraddress\SQLEXPRESS
I recommend using the OLEDB method in Example 3 rather than the ODBC method in 1 and 2 but they should all work. This is a good resource for Connection Strings
http://www.connectionstrings.com/sql-server/
If you follow the steps on this page you will be able to see more useful error messages
http://www.chestysoft.com/asp-error-messages.asp
We are in the process of completing SSIS packages. However as we move towards the deployment phase surprisingly we realized that deployment of SSIS package is not really straight forward as terms of security.
we need to run a SSIS package using either batch file or .NET program in production server. The caller (batch or .NET) should call the SSIS package by supplying parameters (such as source file, destination database, userid, password etc) and also read return code (Success/Error) from SSIS. The user id and password should not be in clear text format visible to anyone. We did some research and found that deployment can be done using many options such as XML config, SQL server Configuration, environment variables, Registry etc but did not mentioned any about password encryption. How can we achieve security and ensure flexibility deploying same package in multiple environment (DEV,UAT,PROD) and simple changing the environment specific variables at the time of deployment.
I am looking for somthing where MVC/Entity framework the connection strings are automatically encypted when the application is run first time using following code.
Configuration config = WebConfigurationManager.OpenWebConfiguration("~");
ConfigurationSection section = config.GetSection("connectionStrings");
if (!section.SectionInformation.IsProtected)
{
section.SectionInformation.ProtectSection("DataProtectionConfigurationProvider");
config.Save();
}
Your question confuses things.
By default, SSIS is going to encrypt anything that could be of a sensitive nature by using the author's Active Directory, AD, account. SSIS Packages Using Package Protection Level This Package Protection Level is EncryptSensitiveWithUserKey If you're using a SQL Server user and password in your connection string, the at-rest value in your SSIS package is going to be encrypted. Don't believe, me, open the file and find the Connection Manager's ConnectionString property.
Deployment is not done through XML, SQL Server, Registry etc. Those refer to methods of creating and storing configuration values that an SSIS package may access during run-time. Configuration has no concept of decrypting values. That isn't to say you can't encrypt values and have them decrypted for the caller, just that there is not built in mechanism for signifying "decrypt using this key."
An approach we are using is to use SQL Server for the holding of encrypted data. We create roles authorized to use the keys and then have computed columns that automatically decrypt the data based on role membership. A person not in that role querying the column will only ever get NULL back as the decrypted value. It's working well for use. EncryptionPOC
Deployment is done through
file copy
dtutil.exe
dtsinstall.exe
.NET api