August 12, 2009 at 9:25 am
Hi All,
I am currently working on a script that will automate the creation/configuration of replication; the problem that I am currently facing is that if I setup replication, the corresponding sql agent jobs are created with my domain login account.
When this jobs try to run, it comes up with the error message, cannot get information about the domain account. The workaround to the problem has always been to change the job owner to SA.
The process of generating the replication script would normally ask for a sql login and password for replication setup, I want to use windows authentication for the creation of replication. Are there any workarounds to this problem?
Thanks in advance guys.
August 17, 2009 at 10:19 am
can you give me a little more info on what you are actually scripting and how as I have automated this before...
I dont ever recall having to add a login/password in order to generate replication scripts...
Let me know
Oraculum
August 17, 2009 at 4:17 pm
Thanks for the reply, basically I have tables/stored procedures/functions/views that I need to automate the scripting for replication, there are over 700 articles. I mainly have a lookup table which holds the name of the object across different DB's, I then use a cursor to auto-create the replication scripts.
At the moment, I am thinking whats the best way for me to do this, should i use GUI to create the replication, script it out and try to re-create the scripts dynamically using T-SQL. I seem to be running into problems if i try to use T-SQL to generate replication scripts, mainly to do with the schame option parameter the one that looks like this 000000001A or some long alpha numeric string.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply