|
|
|
date: Tue, 1 Apr 2008 12:31:04 -0700,
group: microsoft.public.sqlserver.tools
back
Re: SQL Server 2005 can't attach database on Windows Vista
Hi,
Did you install the latest service pack SP2 for your SQL Server 2005
Express instance?
I performed a test at my side with SQL Server 2005 Developer Edition SP2
installed on Windows Vista Enterprise SP1, however I could not reproduce
your issue. Everything worked fine.
Now I recommend that you first run "SELECT @@VERSION" in SSMS to check if
your SQL Server 2005 instance version number is equal to or over 9.0.3042.
If not, please install SQL Server 2005 SP2 first. You can download SQL
Server 2005 SP2 from the following links:
Microsoft SQL Server 2005 Express Edition Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyID=31711d5d-725c-4afa-
9d65-e4465cdff1e7&displaylang=en
Microsoft SQL Server 2005 Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-
8f0c-63fa18f26d3a&displaylang=en
You may also try using T-SQL statements to see if it helps. You can attach
your database with the following T-SQL statement:
EXEC sp_attach_db @dbname = N'Northwind',
@filename1 = N'C:\DevNet2008\Data\northwnd.mdf',
@filename2 = N'C:\DevNet2008\Data\northwnd.ldf' ;
Go
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
date: Wed, 02 Apr 2008 07:08:44 GMT
author: (Charles Wang[MSFT])
Re: SQL Server 2005 can't attach database on Windows Vista
Daniel Grassick (dmgrass@community.nospam) writes:
> SQL Server (MSSQLSERVER) uses account ".\Daniel"
> SQL Server (SQLEXPRESS) used account "NT AUTHORITY\NetworkService"
>
> These settings work fine on my Windows XP machines but I changed the
> account for SQL Express to ".\Daniel" on the Vista machine and now the
> DB attach works!
>
> I don't understand how "NT AUTHORITY\NetworkService" can work on the XP
> machines since I don't see any user or group with that name nor any
> login or role under server permissions in SSMS. Should I have done
> something different?
NetworkService is something built in.
I guess it works on XP, but not on Vista because Vista is stricter
on security and permissions.
The recommendation is to run SQL Server from a domain account, but
not one that has admin rights. I usually create a separate account
to run SQL Server from. The problem if you do this now, you would
have to grant that account the Windows privileges you need, or at
least I think so. When you specify an account at setup, Setup does
that for you.
The problem with using your own account is that you may change your
password some day (well, at least you should), and in this case, you
need to change the password for the service as well, or SQL Server won't
start.
> I assume I need to change the account for the
> following services which currently use "NetworkService":
>
> SQL Server Integration Services
> SQL Server Browser
Integration Services, yes. But I think NetworkService (or is that
LocalService) is preferred for the Browser service.) The Browser is
the one that tells a connecting client that instance ABC is on port
4711.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
date: Fri, 04 Apr 2008 15:23:05 -0700
author: Erland Sommarskog
|
|