On Sat, Dec 13, 2008 at 10:00 AM, Allen <[email protected]> wrote: > Hi Steve thanks for taking the time. > SQL 2008 express does have some tools. But I want to be able to allow the > program to create what it needs much like I do now with VFP tables. Ask > where the data is to go and deal with it. This is because the names are > created by the program. > I assume that if I want to use sql / sql express then that would have to go > on where the data goes and I would have to access that data as if its on a > server. But using c# 2008 express (or the full as if it works I will get it) > can I create databases on the server once the sql server is installed and > providing the rights are correct. > My problem at the moment is I'm away from the server so cant really test it. ---------------------------------------
Breaking this out as I read it: > But I want to be able to allow the > program to create what it needs much like I do now with VFP tables. Ask > where the data is to go and deal with it. This is because the names are > created by the program. I read this as deployment of your application to a customer. Am I on target? If so do you have to install the server engine for the client, or is that running for you already? If the server already has SQL installed, they you have three options. 1) Attach a copy of your db for their use. 2) Restore from a backup of the database you supply to a container on their server. 3) Supply setup script to generate the schema and data you want to deploy. Only issues you will run across are location of database file(s) and log(s) on the server. This is where your performance can be impacted just by location on the RAID. SQL Server will generate the schema script for you via a wizard it has to generate this script(s). You just indicate what you want it to create for you. This was the old school methodology. Run script and it's done. 100% code and no problems. hahahahaha. I like the option #2 above myself. I have the scripts to generate the DB container for me, I then know where my backup is located so I just tell it to restore from it and go live. Last aspect of potential problems you will face is security. This is a major aspect of why you would consider leaving 2000 and upgrading to 2005 or 2008. Yes it is harder! DO NOT RUN as sa in your application. I have worked with two organizations that still do. Makes no sense to the right minded person. But they just are to lazy to set rights properly. Another part of 2005/2008 is the use of the Instance on the server. Quick translation is that you can install MULTIPLE INDEPENDENT SQL Engines on the same server. \\MyServer\Production \\MyServer\Stage \\MyServer\Test You do your dev work locally and when you are ready to push up to Test you can. If your testers find a broken faucet in one of your apps you can contain it now without having to DOWN your server. That server was also running production so this is a huge thing for you so try to work with it. You can have your production system data and restore it to your stage instance put your changes to it and then point your updated application to work with the stage instance for a day or a week allowing the customer to feel comfortable with it till you switch it over to Prod. Granted it is a lot more complex than this write up, but this is a good heads up on what to do and why to do it a particular way. HTH -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
