>Jim,
>
>I guess I'm asking about running scripts. What is a "best practice" for executing that script? Should my application run it? Should someone run it from the command prompt?

I've seen it done all three ways...

1. Ship the script as a text file, have the users open Query Analyzer and run it.

2. Shipt an exe (this is what we do) that sends the script to the server. This also allows us to encrypt our SP's.

3. Include the script in the ap, on connect read a db version, and run the script if it doesn't match. (My main concern with this is if I am using 1.5, and you log in with 1.6 and change the DB schema, then my 1.5 will break.)

BOb


>
>Thanks,
>Dan
>
>>Not sure if I follow you here. Deploying a SQL Server database either requires SQL Server or MSDE to be installed on the server you want to place the DB on. Installing SQL Server is pretty straightforward and MSDE can be installed using Windows Installer modules.