January 30, 2019 at 8:41 am
I have 2 servers, server A and server B.
Server A has a sql agent job that runs every morning moving large amounts of data from other SQL Servers to server B. Server B is where the linked server connections actually exist.
I am having problems wrapping my head around all of this. Do I need to have the linked servers on Server A or on Server B in order to best spread out the load and processing or do I need to move the agent jobs to server B.
January 30, 2019 at 9:57 am
You haven't really explained what is happening. Moving data from other servers to Server B, what does that mean? What do linked servers have to do with this?
The Agent job calls something. That something has to do the work. Where the agent calls from doesn't matter for processing load. Unless you can call things in two places, you aren't changing the load on the target machine doing the work.
January 30, 2019 at 10:44 am
Linked Severs have the data, data needs to end up on Server B.
The jobs are essentially just queries against the linked servers to pull the data into Sever B, the nature of the data mostly means that we dump and reload all of it as there is no way to discern what has changed, what has been added, or what has been deleted from the source.
I consult concerning the obstacles, challenges, and insecurities that come up against the simple act of delivering an element from one place to another. To name a few: attrition, gravity, mischief, calamity, incompetence … also, erosion, contraction, expansion, buffoonery.
Essentially, I exist because of the tremendous difficulty inherent in simply transporting any entity from A to B.
January 30, 2019 at 10:52 am
You need to have the agent job on the instance (Server B) which has the linked server connection to Server A.
Your queries will then be something like:INSERT INTO myDatabase.dbo.myTable
SELECT * FROM myLinkedServerA.myDatabase2.dbo.myTable2
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply