Distributed Database Development?

  • I am working on developing an application.  I know the input database structure, and I know my database structure I am creating, however for my clients, I don't know where they will put my application. 
     
    They may put it on the same SQL Server as the input database, or they may put it in a different SQL server instance.  I also don't know what the name / owner of my input DB will be. 
     
    So my question, is if all I know is the input table / column names, how should I build my stored procedures to access this so that when I go to install this at a client site, there is minimal or no code change required based on where they install my application?
     
    Thanks!
  • Your application uses a connection string specifying the server and database name. Since that can be set dynamically (through a config file for example), I don't think you have a problem.

    The table names, column names and stored procedures won't change.

    I was developing a web-site with a database backend on my local machine. When it came time to deploy to a web site, the host gave me a database with a completely different name than on my development machine. However, all I had to do was set my config file to this new server and database names and no other changes were needed.

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

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