Re: Connecting to SQL Server Express 2005

Tech-Archive recommends: Speed Up your PC by fixing your registry


See also: http://www.sqlservercentral.com/Forums/Topic713473-146-1.aspx

However, as you have only one user permission to transfert, don't bother
yourself too much with a script.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)


"Sylvain Lafontaine" <sylvainlafontaine2009@xxxxxxxx> wrote in message
news:uQbOpWD$JHA.3320@xxxxxxxxxxxxxxxxxxxxxxx
See also:

http://www.databasejournal.com/features/mssql/article.php/2228611/Migrating-Logins-from-One-SQL-Server-to-Another.htm

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)


"hedera" <hedera@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:418C96AC-1801-4EC8-A63C-AE750194B8E5@xxxxxxxxxxxxxxxx
Thank you, Sylvain, I will read that article and see what I can do about
it!
This is the first suggestion I've gotten that looks as though it might
lead
somewhere...
--
hedera

Nature bats last.


"Sylvain Lafontaine" wrote:

You have a problem with the SID here: when you recreate the user
account,
even if you use the same name for the user account, it gets created with
a
different SID so SQL-Server see it as a different user. See the
following
article on how to solve this problem:

http://msmvps.com/blogs/greglow/archive/2007/04/09/sql-server-logins-and-sids-a-quiet-change-in-sp2.aspx

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam
please)
Independent consultant and remote programming for Access and SQL-Server
(French)


"hedera" <hedera@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:801D4985-0AB1-473C-8F7D-244F8F933953@xxxxxxxxxxxxxxxx
I support a web site (http://www.oaklandsymphonychorus.org) built on a
backleveled version of DotNetNuke, using SQL Server 2000. I want to
upgrade
the DNN, so I've been trying to build a copy of the site on my Vista
laptop,
so I can work out and test the upgrade procedure. Because this is all
volunteer work, I downloaded SQL Server Express 2005 and the SQL tool
suite
(management studio express, configuration manager, surface area
configuration).

The DNN install instructions tell me to create a blank database,
create a
new login using SQL server authentication, create a database user
under
the
blank database, associate the new user with the login just created,
and
give
the user the privilege db_owner under both Schemas Owned by User and
Database
Role Membership. After all this, I'm supposed to restore the blank
database
from the backup of my production (sql 2000) database, and I should be
able
to
bring up the site. The database, login and password, and database
user
are
all identical to my production versions, which are working.

I've done all this, necessarily connected to the SQL engine as sa; but
I
have never been able to connect to the database as my test user. I
connect
to the SQL server (using Management Studio Express) as the userid I
created,
and I can't open the database. This also means that I can't restore
the
database logged in as oscuser; I can't even look at the database
unless
I'm
logged in as sa. Connection attempts in Management Studio Express get
this
error, unless I'm connected as sa:

TITLE: Microsoft SQL Server Management Studio Express
------------------------------

The database oaklandsymphonychorus is not accessible.
(Microsoft.SqlServer.Express.ObjectExplorer)

------------------------------
BUTTONS:

OK
------------------------------


I've been playing with connection strings, my current version, which I
think
is working, looks like this:

<add name="SiteSqlServer"
connectionString="Server=(local);Database=oaklandsymphonychorus;uid=oscuser;pwd=mozart;"
providerName="System.Data.SqlClient" />

The error I'm currently getting when I try to browse port 80 on
localhost
is:

DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database
Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

A network-related or instance-specific error occurred while
establishing a
connection to SQL Server. The server was not found or was not
accessible.
Verify that the instance name is correct and that SQL Server is
configured
to
allow remote connections. (provider: Named Pipes Provider, error: 40 -
Could
not open a connection to SQL Server)

I realize this is a DNN error but I'm almost certain there's also a
SQL
error, because I can't open the database when connected to the SQL
engine
as
oscuser in Management Studio Express. Can anybody give me any
guidance?
Is
anything I'm doing obviously wrong? I am an almost complete novice in
SQL
and am finding the documentation impenetrable - except that I do get
that
a
user with the db_owner role ought to be able to open and manipulate
the
database, and it can't.
--
hedera

Nature bats last.







.

Quantcast