I need to know how to pass parameters that could tell an executable through the task scheduler, to initiate the ODBC connection first and execute the executable. I do not want to leave a PC, server, terminal server session or similar mechanism running and logged into DB prior to the scheduled task running. This keeps the ODBC connection initialized and available for the Import executable to use when it runs (as a scheduled task). However, that will not be a reliable, long term solution for automating the import as the session would be killed if the server is rebooted, somebody may accidentally close it or a number of other scenarios could cause it to get closed.
Question How do you make the ODBC connection to the database when running the schedule task function, prior to the software executable running. I am using the scheduled function to automactically excute a xml import every 10 minutes. My software keeps stating no db connection. I have looked everywhere and can not find how to tell in this schedule task function command line how to connect to the DB prior to running the process. Does any one know how to fully automating the connection to a ODBC prior to running the executable.
thanks techbk
Are you using any SQL Server tools here?
No comments:
Post a Comment