May 11, 2015 at 3:49 am
I have somewhat of a dilemma to overcome. Basically the company I look after runs SQL 2014 they recently purchased a new company and now need to integrate services with the current 2014 platform and a SQL 2000 platform. There are no immediate plans to upgrade from 2000 to a supported platform due to the black box nature of the system and legacy code no longer in use in current SQL versions :angry:.
My task is to find a way where by SP’s can be executed on 2014 to SQL 2000. The only way I can think of doing this is by have a make shift SQL proxy of sorts where by SQL 2008 is installed and create a linked server to SQL 2000 and the 2008 can do all of the leg work and pass information from 2000 to 2014. I HATE this idea as it is extremely ugly is there another way of doing this calling SP’s from 2014 to execute on SQL 2000??
I know you can’t connect directly between the two hence the idea of a proxy, and I am continuing the fight to get the sql 2000 upgraded but I don’t see this getting signed of just yet.
Any help or advise would be appreciated.
May 11, 2015 at 10:17 am
I suppose this would depend on the nature of the SP's you need to run on the 2000 server, are these once a day batch jobs that are run, are these SP's that are run on demand by users?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply