The architecture we are using is the following:
a.- 2 SQL Server servers.
b.- 1 SQL servers where is the integration server catalog (dtsx) and Jobs.
I need to execute from the SQL servers a stored procedure that executes one of the DTSX that is in the other server, I can perform this action by linked server.
But:
1.- If I execute via linked server in which server the execution is carried out? Will the performance of my SQL servers decrease?
2.- Is there another way to run dtsx and jobs that is not linked server?
Related
I have SSIS packages in SSIS catalog on SQL Server, Serv1. The packages, while executing, establish connection to SQL Server, Serv2. And they fail while acquiring connection.
I know a little bit about linked server that is to run query from one server on another the latter one has to be a linked server to former one. The above scenatrio looks the same but i didn't find any information related to it. Do i have to add Serv2 as Linked Server for Serv1?
No. Linked server scenario is used when you need to access DB from the outer server inside SQL query run on local server.
SSIS packages are built with goal that it access some DB server, possibly a remote one, fetch data from it, transform and store results somewhere - in files, DB etc. Accessing a remote SQL DB is a normal scenario.
Moreover, using Linked server in SSIS package is a bad practice. You move control of DB access from SSIS catalogue to DB server, in case of any problems - it is more difficult to trace and investigate.
In your case - SSIS packages in SSIS catalogue - check in package execution log which connection string is used to connect to the remote server. Is it an integrated authentication? Does the account under which SSIS package is executed have an access to the DB? If using SQL auth - are login and password valid?
I need to make a procedure or find a solution in order to copy, at the end of each day, data that was added to my local MySQL server over to a Remote SQL server.
I am likely going to code a small app in .net to simply pull the data from the local MySQL server and insert it into the Remote SQL server, and just run the app on a schedule.
However, If I can avoid doing this and move the data with a procedure or a job that would be preferable.
Any suggestions for a solution?
I have created one project for SSIS and deployed that on sql server 2014. When I am running packages from sql server data tool its running fine and performing all operations, but when I am running from catlog procs [SSISDB].[CATALOG].[Create_execution] its shows run successful but I can't see any data into my staging tables. I have used configuration tables to configure connection and files path.
Any idea.
PLease check the user privileges (file system, etc.) - if you call the procedures with another user than you execute the package from within Data Tools, this might be the reason.
I have two data servers which are placed remotely in different locations. One server is SQL Server 2008 R2 and the other one is SQL Azure.
SQL Server contains more than 50000000 records and I want to sync that data into the SQL Azure server.
What are the best ways to do so that we did not face following problems
Data loss
Duplications or data redundancy
Delays
Thanks in advance
You can use SQL Data Sync by installing the sync agent on your SQL Server 2008 R2 machine and point the agent to your SQL Azure database.
Check this link for all the details http://azure.microsoft.com/en-us/documentation/articles/sql-database-get-started-sql-data-sync/
Additionally, you can use an SSIS job on the SQL Server to copy the data to your SQL Azure database.
We are going to use different SQL servers for SSIS and database. Currently both are in same servers. We have a package which calls another package inside that. But I am not able to select the secondary package location from SQL server option in the editor as the MSDB is in SSIS server not in database server. Should the MSDB in database server for me to select it or can we use SSIS server to deploy MSDB?
Thanks
Ajeesh
So first, create a connection to your SSIS Server in your package. Let's name it SSISServer.
Create your Execute Package task.
In the editor, under the Package Tab, under ReferenceType, choose External Reference.
Under Location, choose SQL Server.
Under Connection, choose SSISServer.
Under PackageName, browse to your package.
This is how you execute packages on different servers from the package that is running.