June 7, 2009 at 12:32 pm
When I started installing SQL 2005 Dev Ed on Vista I got a compatability warning. Clicked on the link and it said I need to install SP2 before running SQL Server on this edition of Windows.
I wound up downloading Service Pack 3 as it said it was cumulative. After the installation I specified that I did not want to start any service after the install is done which is what happened. I installed SP3 and restarted the computer. I opened up the management studio and I was not able to login.
I changed the SQL Server account to run by my login and then attempted to login with the same credentials and again was denied.
This installation is on my home laptop so my wife and I can work/learn. There's no domain or network accounts.
Thanks,
Peter
June 7, 2009 at 12:47 pm
I know SQL Server but I would not install with all services off, so you need to go to configuration manager and turn on at least the SQL Server service by default only the Agent and SSIS is off in the developer edition. You must know you need to go into surface area configuration to enable all you need because the developer edition and Express comes with all features disabled.
Kind regards,
Gift Peddie
June 7, 2009 at 1:05 pm
On Vista the administrator user no longer has automatic rights to SQL. The provisioning tool should have come up at the end of the service pack installation to allow you to add an administrative user.
Search for the file 'sqlprov.exe'. Make sure that the SQL service is runnign and run that program. It will allow you to add local machine or domain accounts to SQL. What ever users you add will be part of the sysadmin group.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 7, 2009 at 3:50 pm
I'm about to do a new installation. This time I'll enable SQL Server Engine afterwards. I'll only install the DB Enging, Client Tools, and SSIS.
In regards to the provisioning tool I did a search for it because I saw it was mentioned in another article. The application didn't exist. This was after installing SP3. I tried to see if the Surface Configuration would help but I didn't see anything to help manage user accounts.
We'll see what happens this time around.
June 7, 2009 at 4:04 pm
Try installing SP2 before SP3. The prov tool launches automatically at the end of SP2
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 7, 2009 at 5:30 pm
I'm wondering if I should install each SP by itself (1 then 2 then 3). I was under the impression the SP's are cumulative.
In this case I'll only run SP2.
June 8, 2009 at 2:50 am
They are. I'm just wondering if there's something missing around the provisioning tool with SP3. It's not something I've ever tested, so can't be sure either way.
Install SP2, make sure that either the provisioning tool runs at the end or that you run it yourself, then install SP3 afterwards.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply