Related
Scenario: Read Excel file from a shared folder on a different domain
Issue: SSIS Package works fine when run manually from SQL server but when I tried to run it using SQL job it fails.
The solution is Kerberos Authentication configuration between two domains so that the SQL Server Job agent can access the shared folder from another domain.
How to create a WordPress website when the hosting package that was given by T-Home (T-Mobile) only includes a FTP password and FTP username, but doesn't include an access to a hosting panel or a remote access to MySQL?
If you've been provided a MySQL database, but you just can't access it remotely then this shouldn't be a problem. You can just upload the Wordpress installation files via FTP and then open your website in your browser and you can configure everything with the WordPress installation wizard, which should automatically start once you uploaded everything to your webspace.
If your provider hasn't provided you a MySQL database I see no way to make this work. (You can create a Blog on http://wordpress.com though).
That is correct.
You can download WordPress installation zip in your local system, extract it and upload it on server using FTP account.
MySQL is generally installed in same server and you can use localhost as server name (no need to have remote access). Most of the providers do not provide remote mysql access to avoid security issues.
Once you have uploaded WordPress files on server, access your site with domain.com (if the domain is pointing to same server) OR if it does not point to server, you can access it with temporary URL and proceed with the installation steps.
I am working on using SSIS FTP task to uploading some files to sftp://apollo.xxx.xxx.com automatically.
I can do that successfully by manually specifying sever name, server port, user name and password in FileZilla.
However, when I setup in the FTP connection manager, the connection fails (could be the issue of SFTP?).
I am just wondering if anyone could provide me some tips?
The native FTP task is just FTP. It does not support sFTP.
As you are not allowed to use third party software, you will be unable to fulfill your request. Based on this question, there does not appear to be a base sftp module in the .NET framework How do I upload a file to an SFTP server in C# / .NET?
Is it possible to import files from an ftp server directly into a sql server 2008 table using perhaps an SSIS package or something? I have thought of transferring the files via ftp to a local server and then doing the import but just wondered if there was more economical way of doing this with regards to space and memory.
If you have access to the physical file location (i.e. you can map a drive to it) then yes you can bypass the FTP process. If not, SSIS does not support ftp as a source connection within data flow. You will need to use the FTP Task in the control flow to copy the file and then a File Source component within your Data Flow
We are a team working on a bunch of SSIS packages, which we share using version control (SVN). We have three ways of saving sensitive data in these packages :
not storing them at all
storing them with a user key
storing them with a password
However, each of these options is inconvenient while testing packages saved and committed by an other developer. For each such package, one has to update the credentials, no matter how the sensitive data was persisted.
Is there a better way to collaborate on SSIS packages?
Since my workplace uses file deployment, I use "Don't save sensitive" In order to make development easier, we also store config files with the packages in our version control system, and the connection strings for the development environment are stored in the config files. The config files are also stored in a commonly named folder, so if I retrieve the config files into my common config file area, then I can open any of our project packages and they will work for me for development. When the packages are deployed, they are secured by the deployment team on a machine where developers do not have access and the config file values for connection strings are changed to match the production environment.
We do somthing similar using database deployment. Each enviroment has a configuration database, and every package references a single xml config file in a common file path on every server/workstation, e.g., "c:\SSISConfig". This xml config file has one entry that points to the appropriate config database for that environment. All of the rest of the SSIS configs are stored in that config database. The config database in production is only accessible by the admin group, the developers do not have access. When new packages and configurations are deployed to prod, connection strings are updated by the admin group. The packages are all set to "Dont save sensitive".