Developing a SQL server DB (noob question)

I'm beginning development on a medium/ sized in-house web based system. Well moving from asp/mysql to asp.net/sql server. Re-doing DB design as well.

My question is does it make sense for me to develop the SQL DB in Visual Studio 2005 pro, and then later move it to a real SQL server? Or basically what is the best and/or most practical way to do this development. Any other IDE's out there?

Thanks

I'd just use SQL Server from the outset. I find Entreprise Manager cumbersome to use, so I just use it to create the database, then create an Access adp file as my main interface to create tables, views and stored procedures. adp files give you the speed and functionality of Access when manipulating SQL Server DB's. I do go back to Entreprise Manager to do things like create table relationships.

|||

So you're basically suggesting developing the DB using the Access IDE, correct? I fail to see how that would be beneficial, Access has different data types than SQL server. When using an ADP file would Access then know the correct column types? Also, how would that ease the development of my web application?

Does anyone else agree with the above comment? The lack of responses makes me feel like everyone else thinks that is the best answer.

|||

With an adp file, you are essentially using the interface of Access to manage your SQL Database. It is still a full SQL Server database; it is not an mdb with native Access types. This means that the datatypes available and field options are all from SQL Server, (e.g. you have VARCHAR instead of Text, etc). You can also do things that create Stored Procedures. It has most of the functionality of Entreprise Manager for creating and maintaining your database.

Reasons I like adp files over Entreprise Manager:

1. adp files allow you to build forms for basic data entry / editing

2. Entreprise Manager Stored Procedure windows are modal. If you are writing a procedure and need to look up a field name in a table, you have to close the window (which you can't do with partially written syntax) first. with an adp the Procedure window can be minimized or tiled.

3. adp files allow you to sort and filter tables in datasheet view. Entreprise Manager doesn't.

4. Speed. adp files are faster for looking up data.

adp files do lack some features, such as the ability to build relationships or triggers. For this use Entreprise Manager.