1. Problems outputting job to text file
Hi, there's a nice script on the knowledge base for exporting the logins
from a primary server to a 'warm standby' which fixes the unmatching or
'orphaned' SID problem you get when adding logins to a standby server. The
script creates a couple of stored procedures on the primary server and you
then type 'exec master..sp_help_revlogin' in query analyser on the master
which outputs a script which you copy and paste into a new query analyser
window and run on the standby server, and it fires in any missing logins and
matches them to the users in the standby database.
Everything works great but I want to automate the creation of this script so
that I have it in a file on the standby, then should the primary completely
crash and burn I still have an up to date one to run. I have created a job
on the primary which simply runs the command 'exec master..sp_help_revlogin'
and then I told the job to output to text file so it sticks it on the
standby server. Here's where it all goes legs up though, the script wont run
correctly after creation using this method and when I review it something
has tagged '[SQLSTATE 01000]' to every single line.
Why is the agent doing this when it created the script and is there any way
I can persuade it to stop?
Thanks in advance for any help!
Paul
2. No response from oracle adodb call that updates User Password via an Alter User Command.
3. help to create stored proc for linked server
4. output query results to a text file
6. Sending output to a text (or other) file
7. 2 CRecordsets under 1 CDatabase
8. Column names in text file output
9. Export to text file from output
10. Outputting text file showing new record(s)
11. How to output results onto a TEXT file?
12. How to direct output of PRINT to a text file