It depends on your set up on the other side. Possibilities:
1. Have a production server that allows database attach. If so, deploy with
the SQL database and change the connection string to use the attach syntax.
You wil then be up and running. This is common in scenarios with SQL Server
Express.
2. Have a database on the production server (or another machine). If this is
your network, you can copy the file and attach it. If an ISP, you can use
the SQL import/export to the address supplied for your database and migrate
all of the tables/data. You then adjust the connection string to fit the
connection string needed for this database.
Do you see a trend? It is always attach data or migrate data and then change
the connection string.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)
************************************************
Think outside the box!
************************************************
"Mahernoz" <ma******@gmail.comwrote in message
news:11**********************@p77g2000hsh.googlegr oups.com...
Hi Everyone!
I have a problem here.
I have used the latest asp.net membership & profiles functionality in
my site.
I have 2 roles admin and user.
I also have a user named admin.
Now, my website is running perfectly, but i want to deploy it.
My database has those tables developed by me and also membership
tables (which were
created by using aspnet_regsql wizard).
Do i need to run aspnet_regsql on hosted database? Is it possible to
do that?
Although i have programming experience. I have no deployment
experience.
How can i sucessfully deploy my website? So that i don't loose any of
my data and it works
fine with all the nice membership features?
2nd Question is just for my curiosity: is it necessary that i need sql
2005 only. Is Membership table supported in sql 2000?
Hope to receive a reply asap.
Regards,
Mahernoz