Correct SQL Server version to choose with VS2010

Discussion in 'Databases' started by rlcraven, Aug 2, 2010.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Hello,

    My site is ready to deploy and I need to add a database. I'm not sure if SQL Server 2008 or 2008 R2 is the correct choice.

    The development was done with VS2010, and there is no separate install of SQL Server on the machine. In control panel the base version of SQL server is 2008, there are also R2 components listed (such as Data Tier Application Framework).

    So, is a particular version required or optimal based on this information?

    Second, I will be using the standard ASPNETDB for registration plus a separate one for my app, I guess that is two databases?

    Thank you,

    Randy
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    1) To be honest, there's just not much feature enhancements between SQL2008 & R2 (as far as hosting concern; most of the enhancements are on the sysadmin side).

    If you do not have any database tools installed, i would recommend you get SQL Express 2008 R2 installed on your computer and order SQL 2k8 R2

    2) As for ASPNETDB , you can put the membership schema on the same database as your application.
     
  3. Thank You!

    As for ASPNETDB , you can put the membership schema on the same database as your application.

    In that event how does the app know to look for a database other than ASPNET.MDB to find the registration information? There is no mention of ASPNET in the web.config.

    Thanks,

    Randy
     
  4. Bruce,

    I figured this one out, as you suggested I loaded 2008 R2 and set VS2010 to look at it.

    Then I copied the tables from my database into ASPNETDB. I thought this would be easiest; in retrospect I see that it would have worked either way by explicitly setting the membership and role providers in the web.config.

    I'm still not 100% sure why the ASPNETDB works out of the box without anything in web.config; I am guessing there is something in machine.config that makes this work.

    Thanks again for your helpful suggestion.

    Randy
     
  5. Bruce

    Bruce DiscountASP.NET Staff

    You probably just added a "localSqlServer" connection string to point to your database.
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page