Problems importing backup DB into Express

I am trying to import (unless there is a better way) a database (which I made a backup of) from a SQL Server 2005 v8.0 machine into my SQL Server Management Express 2005 machine so that I can have a full complete copy of the backup database in express. The purpose is so that I can treat it as a template, get rid of tables, views, columns I dont need and repopulate them with different data to compliment my other project, which involves auto tagging of .mp3's.

As an analogy: copy an Excel spreadsheet, open it in Excel, delete cells you dont need, keep the rest but fill in with different data. Kinda like that but with SQL.

I can't figure out exactly how to do this with Express 2005. How do you import or otherwise a backup database from SQL Server 2005 v8.0 and get it into Express?

My backup file is called: WebBackup_KUOW_Program_Full

I've tried renaming it using both .mdf and .bak when I Right-Click Databases and select Restore. Fill in everything then click ok. I keep getting this error message:

TITLE: Microsoft SQL Server Management Studio Express

Restore failed for Server 'INTRA\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program Files\Microsoft SQL Server\MSSQL\Data\kuow_program.mdf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476

BUTTONS:

OK

Can anyone help me with this please! Keep in mind I'm not a SQL guru. Thanks in advance for any assistance.

Thats pretty easy, the original data and log file is stored in the backup, if you want to store the file in another path than it was originally placed in (e.g. if you don′t have that drive letter on the new machine) you will have to change the path in the restore dialog. The data and logfiles will then be placed at the specified location.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Problems during the installation of Integration Services

Trying to install SQL Server 2005 on my machine,I installed each part (engine, reporting services, integration services etc) seperately.

During the installation of Integration Services I got the following message

failed to install and configure assemblies D:\Microsoft SQL Server 90\90\DTS\Tasks\Microsoft.Sqlserver.MSMQTasks.dll in the COM+ catalog. Error: -2146233087

ErrorMessage: Unknown Error 0x80131501

ErrorDescription: You must have administrative credentials to perform this task. Contact your system administrator for assistance

I am administrator of my machine an i tried to install SQL usign this account.

I selected IGNORE and the installation continued. Will I have any problem with Integration Services in the future because of this error?

What is the source of this problem? How could I solve this problem?

Thank You Very Much

I had the same problem but i didnt find any solution.

Did you? Could you please post the solution when you find it?

Thank you

|||

I, too, am getting the same error under the same circumstances (logged in with admin priviledges). Using the help button on the error notification sent me to a web page to directs the user to confirm that the Distributed Transaction Coordinator service is logged in as "Network Service", which it is, so the help advice was useless.

Does anyone know the real source of this error?

Thanks

|||What OS?|||

I'm running XP Pro and Studio 2005 .NET. I found a different note that suggested uninstalling SQL Server, Studio and, .NET, and then reinstalling in that order. I'd really like to avoid uninstalling Studio if possible, though.

I did go back and uninstall all SQL servers (SQL Express was previously installed), and attempt the SQL 2005 install again and got the same error. I pressed "Ignore" and the complete install proceeded to the end without a problem. However, I suspect that MSMQTask.dll, the file that was causing the error, is going to needed at some point and I'll get failures.

Thanks

|||I'm getting the same problem with XP Pro.

I'm surprised it took 6 months for anybody showing interest in this problem. Usually this forum is awesome for solutions.

- Thanks.

Problems during the installation of Integration Services

Trying to install SQL Server 2005 on my machine,I installed each part (engine, reporting services, integration services etc) seperately.

During the installation of Integration Services I got the following message

failed to install and configure assemblies D:\Microsoft SQL Server 90\90\DTS\Tasks\Microsoft.Sqlserver.MSMQTasks.dll in the COM+ catalog. Error: -2146233087

ErrorMessage: Unknown Error 0x80131501

ErrorDescription: You must have administrative credentials to perform this task. Contact your system administrator for assistance

I am administrator of my machine an i tried to install SQL usign this account.

I selected IGNORE and the installation continued. Will I have any problem with Integration Services in the future because of this error?

What is the source of this problem? How could I solve this problem?

Thank You Very Much

I had the same problem but i didnt find any solution.

Did you? Could you please post the solution when you find it?

Thank you

|||

I, too, am getting the same error under the same circumstances (logged in with admin priviledges). Using the help button on the error notification sent me to a web page to directs the user to confirm that the Distributed Transaction Coordinator service is logged in as "Network Service", which it is, so the help advice was useless.

Does anyone know the real source of this error?

Thanks

|||What OS?|||

I'm running XP Pro and Studio 2005 .NET. I found a different note that suggested uninstalling SQL Server, Studio and, .NET, and then reinstalling in that order. I'd really like to avoid uninstalling Studio if possible, though.

I did go back and uninstall all SQL servers (SQL Express was previously installed), and attempt the SQL 2005 install again and got the same error. I pressed "Ignore" and the complete install proceeded to the end without a problem. However, I suspect that MSMQTask.dll, the file that was causing the error, is going to needed at some point and I'll get failures.

Thanks

|||I'm getting the same problem with XP Pro.

I'm surprised it took 6 months for anybody showing interest in this problem. Usually this forum is awesome for solutions.

- Thanks.

Problems deploying website

My ASP.NET application runs fine within the VS2005 IDE; but, when I deploy to my local machine to try to run it under IIS and calling it up in a browser, I'm getting the following exception:

Exception Details: System.Data.SqlClient.SqlException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734979
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838
System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +137
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +83
System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1770
System.Web.UI.WebControls.ListControl.OnDataBinding(EventArgs e) +92
System.Web.UI.WebControls.ListControl.PerformSelect() +31
System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +70
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
System.Web.UI.WebControls.ListControl.OnPreRender(EventArgs e) +26
System.Web.UI.Control.PreRenderRecursiveInternal() +77
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360

I'm a novice at this and really need some help. What stupid newbie mistake am I making here? Thanks in advance for any guidance/assistance rendered.

When you deplyed the app you left the same SQL trusted connection, and most probably there is no local SQL server running in the same machine. Make sure to change the SQL string to the IP, username and password of the database and will work really well

Al

|||

I remember I got this problem too when I did my first try. It seems that your are using trusted connection, you need assign the domain user in your database with appropriate access right. Or you can create a database user in the database to use standard User/password connection method in your database is in mixed mode..

You can easily find the syntax for the connection string. As to create user in database, you need to create a login account under Security on the Server, in the database, you assign this user for access under database security tab.

Limno

problems connection to Informix database

Hi,

I have a MS SQL 7 running on one machine and want to connect to a Informix database on another machine.

But I always get the error
Server: Msg 7319, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' returned a 'NON-CLUSTERED and NOT INTEGRATED' index 'ind_new_id' with incorrect bookmark ordinal 0.

I have installed the newest version of "Microsoft Data Access Components" and I have the latest Informix odbc driver

When I try to test the connection in the ODBC Data Source Administrator the test returns fine.

Anyone knows what my problem might be?One of the post in this forum refers
The problem is caused because most providers including SQL Server OLE DB provider do
not support index seek.

The 'index as access path' should not be checked when creating a linked server using
the SQL OLEDB. There is a provider level option which is read by the SQL Server from
the following registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Providers\SQLOLEDB\IndexAs
Accesspath. Please check whether the value of the above registry key is 0. If it
isn't , please change it to 0 and try the remote query again.

If it doesn't work, I suggest you rebuild a linked server using the SQL OLEDB without
checking 'index as access path'.

Problems connecting with VS.NET Server Explorer

I have SQL Server SPK3 and Visual Studio.NET running on the same machine.
When I try to connect to my SQL Server from the VS.NET Server Explorer I can
expand the server and look at the SQL Server instance on my computer but when
I try to expand the instance, I get a login dialog entitled "SQL Server
Login" which asks for Login and Password. When I put in what I think the
Login and Password should be, it tells me, "The specified procedure could not
be found". If I check the option that says, "Use Windows NT Integrated
Security" it tells me "The specified procedure could not be found". I need
some assistance from some gurus. What's going on here?!!
I cannot help you but have a similar problem. I can add servers, but never
connect and see details. Worse yet, I cannot create a connection. I go
through the dialog and click test connection and get connection "test
connection succeeded" message. When I try to finish the task I get a message
twice saying "Unable to connect to database. The connection failed. Check
your username and password, and try again." Using either Enterprise Manager
or Query Analyzer, I can connect to the server and databases and see whatever
I need to.
I have Visual Studio 2003, I am trying to connect to both a MSDE SP3 (same
machine) and SQL Enterprise SP3 (different machine).
I am not sure when exactly this occurred as in the past I had created some
connections. I noticed it within the last couple weeks as I have gotten back
into .Net for my current project. I cannot use the old connections and once
deleted cannot recreate them as above.
"DBase_Tron" wrote:

> I have SQL Server SPK3 and Visual Studio.NET running on the same machine.
> When I try to connect to my SQL Server from the VS.NET Server Explorer I can
> expand the server and look at the SQL Server instance on my computer but when
> I try to expand the instance, I get a login dialog entitled "SQL Server
> Login" which asks for Login and Password. When I put in what I think the
> Login and Password should be, it tells me, "The specified procedure could not
> be found". If I check the option that says, "Use Windows NT Integrated
> Security" it tells me "The specified procedure could not be found". I need
> some assistance from some gurus. What's going on here?!!
|||

Quote:

Originally posted by DBase_Tron
I have SQL Server SPK3 and Visual Studio.NET running on the same machine.
When I try to connect to my SQL Server from the VS.NET Server Explorer I can
expand the server and look at the SQL Server instance on my computer but when
I try to expand the instance, I get a login dialog entitled "SQL Server
Login" which asks for Login and Password. When I put in what I think the
Login and Password should be, it tells me, "The specified procedure could not
be found". If I check the option that says, "Use Windows NT Integrated
Security" it tells me "The specified procedure could not be found". I need
some assistance from some gurus. What's going on here?!!

|||I have been searching news groups and Microsoft support sites for two days now and finally found a solution to our problem. You should download MDAC 2.8 and install. Apparently a new procedure has been included in this release. Good Luck.|||I had the same problem and what did to solve it was removing the Alias in
the SQL Server Client Network Utility, done.
Hope it helps
Javier.
"Matt Wyncoop" <Matt Wyncoop@.discussions.microsoft.com> wrote in message
news:E55058DA-AA95-48BA-930C-0726BDCAEA28@.microsoft.com...[vbcol=seagreen]
>I cannot help you but have a similar problem. I can add servers, but never
> connect and see details. Worse yet, I cannot create a connection. I go
> through the dialog and click test connection and get connection "test
> connection succeeded" message. When I try to finish the task I get a
> message
> twice saying "Unable to connect to database. The connection failed. Check
> your username and password, and try again." Using either Enterprise
> Manager
> or Query Analyzer, I can connect to the server and databases and see
> whatever
> I need to.
> I have Visual Studio 2003, I am trying to connect to both a MSDE SP3 (same
> machine) and SQL Enterprise SP3 (different machine).
> I am not sure when exactly this occurred as in the past I had created some
> connections. I noticed it within the last couple weeks as I have gotten
> back
> into .Net for my current project. I cannot use the old connections and
> once
> deleted cannot recreate them as above.
>
> "DBase_Tron" wrote:
|||I looked there and I have no aliases.
"Javier Troconis" wrote:

> I had the same problem and what did to solve it was removing the Alias in
> the SQL Server Client Network Utility, done.
> Hope it helps
> Javier.
> "Matt Wyncoop" <Matt Wyncoop@.discussions.microsoft.com> wrote in message
> news:E55058DA-AA95-48BA-930C-0726BDCAEA28@.microsoft.com...
>
>

Problems connecting to local SQL server [HELP!]

Hi all,

I have the developer edition of Visual Studio 2005. After successfully installing it in my local machine, I wanted to create a small application which connects to a database. I accessed the Server Explorer tool, right clicked on Data Connections and brought up the Create New SQL Server Database option.

The issue now is that I don't see a list of servers in the "Server Name" drop down box although in the Server Explorer itself, I have a server listed (your-c6b5e4eabc - The default computer name of my local machine).

I am given to believe that SQL server is unable to make a connection because I have not configured something which is essential.

I hope someone can point me as to how to make databases using SQL server and connect them to the application the way developers usually do. I'm a complete novice to VS 2005, and the SQL server configuration options have got me confused.

I'm not sure if this will help, but I'll include this here anyway :

When I tried copying and pasting the server name (your-c6b5e4eabc) into the "Server Name" drop down box and creating a database by entering a name in the "Enter database name" textbox, I get the following error message -

An error occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings, SQL server does not allow remote connections. provider : Named Pipes Provider error : 40 Error : Could not open a connection to SQL Server.

I'm running Windows XP Media Center Edition v2002 SP 2.

I just want to be able to create and work with databases from within the applications I create in Visual Studio 2005. I played around with the configuration options (like enabling some protocols, the SQL server browser etc., but to no avail.) Is there a way to revert back to the default settings in an easy way? Thanks in advance for all your guidance...

Have a look in my screencasts section on my site showing you the way to enabled remote connections.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||

Hey there,

Thanks very much for your screencast link. I think we should have more such user-friendly guides for first timers to Visual Studio. Unfortunately, I'm still facing the same problem creating a database from the Server Explorer.

I also have a rider question here : Although I've made a typical installation of Visual Studio 2005, the service I seem to be running isn't MSSQLSERVER, but rather SQLEXPRESS. I really need someone to throw more light on this aspect of Visual Studio 2005...or is my case an aberration?

Also, I mentioned playing around with the settings of the SQL Server 2005 Configuration Manager...can that be affecting things in any way? What are the ideal settings to connect to the server from within the server explorer in VS 2005? Most notably, I've set the SQL Server 2005 Services (SQLExoress and SQLBrowser) to log on as "NT Authority/LocalService"...is this the right setting?

Thanks again.

|||

Hi, thanks for the feedback, if you have any upcoming ideas about screencasts, feel free to contact me :-).

1.
SQL Server Express comes with VS 2005, you can use SQL Server Express at no charge. The SQL Server instances are reflected in the Service names, which are for a default instance MSSQLSERVER and for named Instances MSSQL$InstanceName. Named instances can be accessed by using the MachineName\InstanceName (and in addition if you don′t use the default port the ",portnumber" addition to the) name.

2.
Sure, changing the configuration will affect the current SQL Server instance (some changes might be reflected after the next reboot, like the remote connections setting). Local Services is fine if you don′t need any network ressources.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Problems after moving rebuilding a server and reconnect to old DBs

Hello,
I've the following problem:
running sql server on machine A
running reportservices on machine B
machine B is a week one, so I ordered from our IT a bigger server and
reinstall everything (win2003 / reportservices ...)
after setup everything works fine! (remember sql DBs on machine A,
webservice on machine B => "webfarm")
so I started take my midnight backup of the "old" reportserver-DB /rs-temp-
DB and restore them on machine A, I've followd all the steps in kb-artikle
842425 "how to move a rs database ..."
everthings works fine, but when I try to open the
http:/localhost/reports/pages/folder.aspx
I got the following strange error:
Diese Edition von Reporting Services unterstützt keine
Webfarmbereitstellungen. (rsInvalidRSEditionConfiguration)
(its german an means: This edition of reporting services does not provide
webfarm constellation)
WHY?
before restoring the DBs, the same constellation works fine! Does my
Reporting Service now think he has to use 2 different DBs? How can I fix it?
I have SQL SERVER Standart Edition (2 licenses)/ Reporting Services Standart
Edition
thanks for forcomming help
sequalDONE!!!
I've found a post from Brian Hartmann!
THANXS!!!!
"sequal" wrote:
> Hello,
> I've the following problem:
> running sql server on machine A
> running reportservices on machine B
> machine B is a week one, so I ordered from our IT a bigger server and
> reinstall everything (win2003 / reportservices ...)
> after setup everything works fine! (remember sql DBs on machine A,
> webservice on machine B => "webfarm")
> so I started take my midnight backup of the "old" reportserver-DB /rs-temp-
> DB and restore them on machine A, I've followd all the steps in kb-artikle
> 842425 "how to move a rs database ..."
> everthings works fine, but when I try to open the
> http:/localhost/reports/pages/folder.aspx
> I got the following strange error:
> Diese Edition von Reporting Services unterstützt keine
> Webfarmbereitstellungen. (rsInvalidRSEditionConfiguration)
> (its german an means: This edition of reporting services does not provide
> webfarm constellation)
> WHY?
> before restoring the DBs, the same constellation works fine! Does my
> Reporting Service now think he has to use 2 different DBs? How can I fix it?
> I have SQL SERVER Standart Edition (2 licenses)/ Reporting Services Standart
> Edition
> thanks for forcomming help
> sequal

Problem with win2000 and xp seeing the server

I have sql server 8.0 installed on my win2000 machine and a xp machine trying to access that server. I have my network connected through a linksys router. I can connect to the internet but can not access the server.
Mike,
Not clear. Did you mean the WinXP client cannot access the SQLServer in
Win2000? If so, what is the error?
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:16317F90-3264-4C74-B73C-38383992615B@.microsoft.com...
> I have sql server 8.0 installed on my win2000 machine and a xp machine
trying to access that server. I have my network connected through a linksys
router. I can connect to the internet but can not access the server.

Problem with win2000 and xp seeing the server

I have sql server 8.0 installed on my win2000 machine and a xp machine trying to access that server. I have my network connected through a linksys router. I can connect to the internet but can not access the server.Mike,
Not clear. Did you mean the WinXP client cannot access the SQLServer in
Win2000? If so, what is the error?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:16317F90-3264-4C74-B73C-38383992615B@.microsoft.com...
> I have sql server 8.0 installed on my win2000 machine and a xp machine
trying to access that server. I have my network connected through a linksys
router. I can connect to the internet but can not access the server.

Problem with win2000 and xp seeing the server

I have sql server 8.0 installed on my win2000 machine and a xp machine tryin
g to access that server. I have my network connected through a linksys rout
er. I can connect to the internet but can not access the server.Mike,
Not clear. Did you mean the WinXP client cannot access the SQLServer in
Win2000? If so, what is the error?
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:16317F90-3264-4C74-B73C-38383992615B@.microsoft.com...
> I have sql server 8.0 installed on my win2000 machine and a xp machine
trying to access that server. I have my network connected through a linksys
router. I can connect to the internet but can not access the server.

Problem with website and db

I am new to .NET and the Visual Web Developer Express and what not...I have created a website on my machine which works wonderfully...however, and I'm sure this is somewhere but I can't find it, I cannot get it to work on my host server...the Default page comes up, but when I try to sign in it says:

"An attempt to attach an auto-named database for file c:\hosting\webhost4life\member\harrison0801\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share."

The host support tells me to change the db name from aspnetdb to something else...I do this and when I run the site again or try to log in, I get the exact same error message...then they go on to tell me that I have to remove the LocalSqlServer in the web.config file which now looks like this:

<connectionStrings>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="Data Source=.\SQLEXPRESS;Integrated Security=True;AttachDbFilename=|DataDirectory|aspnetdb.mdf;User instance=true;" providerName="System.Data.SqlClient" />

<add name="Example" connectionString="Data Source=.\SQLEXPRESS;Integrated Security=True;AttachDbFilename=|DataDirectory|example.mdf;User instance=true;Initial Catalog=example;" providerName="System.Data.SqlClient" />

</connectionStrings>

Of course this isn't working either...otherwise I would off playing on my server, and not posting here. Also, when I set up all the roles, users, and what not on my machine...does this carry over to the host machine?

Desperately needing massive help here...

Not a DBA and no expert in .NET

Thank you very much in advance,

Darren

Rename the .mdf file from aspnetdb.mdf to harrison0801.mdf and change your connection string to

<add name="LocalSqlServer" connectionString="Data Source=.\SQLEXPRESS;Integrated Security=True;AttachDbFilename=|DataDirectory|harrison0801.mdf;User instance=true;" providerName="System.Data.SqlClient" />

|||

Okay...renamed the ASPNETDB.MDF and changed the config connection string to the above...hit CTRL F5 to run it...and guess what magically appeared? ASPNETDB without regard to the one I just changed the name on.

Also, when I run the ASP NET Configuration utililty in the VWD...walks me through all the roles, users, etc...it loads all that info into the ASPNETDB...is there something in the default config for the DB creator that can be changed? Perhaps this is something that the ASPNET creators can work out...maybe like allow the developers to name there own DB in the process of creating websites? Would be nice...less of a headache.