March 28, 2014 at 9:00 am
We have a sql instance "A" in server "1", where we have jobs that run stored procs locally and also ssis packages. These jobs read data from a separate server lets say server "X" and writes the processed data into server "1". We want to relieve some of the processing in this server by having the jobs be processed in another server, lets say sql instance "B" server 2".
Correct me if I'm wrong but if I just create a linked server connection from server "2" to "1" and then run the stored procs which are in server "1" from within server "2", the processing task will still be done in server "1" because that is where the stord procs are located at, correct?
In order to really process the job in server "2", the store procs should be located in server "2". Again note that these stored procs are reading data from server "x" and writing it into server "1". So I do understand that the part which writes the data will still take some processing resources from server "1", but at least the rest of the processing is done in server "2".
Is my head on the right spot here?
March 28, 2014 at 9:05 am
The better way to go about this is to determine why your server is having performance issues. Are people running massive amounts of ad-hoc queries? Have you reviewed your indexes? Do you have a lot of large databases with small autogrowth size? Are queries hitting your server poorly written? Etc (tons of stuff you can check).
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply