Manage Multiple SQL Server Installations and Databases with OSQL

  • Comments posted to this topic are about the content posted at

  • I've also been using these types of .bat files for a short while for production rather than admin purposes. I've recently had to transfer all my print & file interfaces (written in cobol on our mainframe) to SQLServer and found that I could call these batch files from within ftp scripts. So I'd use one ftp script to move a file from one server to an sqlserver, call in the .bat script to load & process the file and then move the output to another server or printer. not only was it quicker than running the interface jobs on the mainframe (bull dps7000), it also reduced the task of importing/exporting files and issuing console commands down to one double-click of the mouse on the ftp script icon.

  • I agree with this method 100%. Also to alleviate files on the server you can call stored procedures also, and I love getting my output to a text file and being able to use windows findstr function to look for errors.

    Mainly I write database maintenance scripts this way. It saves a lot of time I just implement the files and forget, and I don't have to use a gui and wonder what it is really doing or working!

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply