Hello Nanda,
1) please contact your Redwood account manager
2) the connector executes the stored procedure or query that you try to run, this automatically makes it wait for it to finish and catch the output and potential exceptions
3) None really
4) Using a JDBC process server gets around two issues you face with the MSSQL command line tooling, and there is an additional benifit.
a) the JDBC process server keeps checking the connection to the database, if the database is not there, the process server goes red and jobs will hold up until the database is available again. With command line script, they will just all fail and you will have to figure out which one you have to restart and make the process catch up again
b) the MSSQL command line tooling does not wait for stored procedures or MSSQL jobs to finish, so you have to customize additional controls around it
c) additional benefit is that you can directly interact with the remote database through RedwoodScript using a Credential to connect. This way it is even easier to do some smart dynamic processing
Regards Gerben
