locked
SQL Server installation on Vista RRS feed

  • Question

  • Two questions : 1) Is it possible to go back to XP if I've bought a laptop with Vista Basic on it. 2) Can we install SQL Server 2005 on Vista Basic operating system? thanks
    • Edited by RajKS Friday, July 31, 2009 12:42 AM
    Friday, July 31, 2009 12:41 AM

Answers

  • If you have a license for XP then yes, and SQL Server 2005 requires SP2 on Vista and you need to run the Vista Provisioning tool to add Administrators as Sysadmins in SQL

    Jonathan Kehayias
    http://sqlblog.com/blogs/jonathan_kehayias/
    http://www.twitter.com/SQLSarg
    http://www.sqlclr.net/
    Please click the Mark as Answer button if a post solves your problem!
    Friday, July 31, 2009 1:11 AM
  • Hi RajKS

    This is Mark, Microsoft SQL Support Engineer. I'm glad to assist you.

    in order to address your concern, I would like to explain the following
    1 Q:Is it possible to go back to XP if I've bought a laptop with Vista Basic on it.
       A: if you have the licens of the XP, you just need to re-install the OS with the installation of the XP OS.

    2 Q:Can we install SQL Server 2005 on Vista Basic operating system?
       A: it is based on what edition of the SQL Server you would like to install; for more information, there is an article to share with you:http://msdn.microsoft.com/en-us/library/ms143506(SQL.90).aspx

    if you have any questions on my reply, please let me know. once your concerns addressed, I appreciate your confirmation.

    I look forwar to your reply.

    Regards
    Mark Han
    Monday, August 3, 2009 9:36 AM

All replies

  • If you have a license for XP then yes, and SQL Server 2005 requires SP2 on Vista and you need to run the Vista Provisioning tool to add Administrators as Sysadmins in SQL

    Jonathan Kehayias
    http://sqlblog.com/blogs/jonathan_kehayias/
    http://www.twitter.com/SQLSarg
    http://www.sqlclr.net/
    Please click the Mark as Answer button if a post solves your problem!
    Friday, July 31, 2009 1:11 AM
  • Hi RajKS

    This is Mark, Microsoft SQL Support Engineer. I'm glad to assist you.

    in order to address your concern, I would like to explain the following
    1 Q:Is it possible to go back to XP if I've bought a laptop with Vista Basic on it.
       A: if you have the licens of the XP, you just need to re-install the OS with the installation of the XP OS.

    2 Q:Can we install SQL Server 2005 on Vista Basic operating system?
       A: it is based on what edition of the SQL Server you would like to install; for more information, there is an article to share with you:http://msdn.microsoft.com/en-us/library/ms143506(SQL.90).aspx

    if you have any questions on my reply, please let me know. once your concerns addressed, I appreciate your confirmation.

    I look forwar to your reply.

    Regards
    Mark Han
    Monday, August 3, 2009 9:36 AM
  • Hello Mark,

    Really glad that you are out to help us.

    I am installing Sql Server 2008 on Vista Business Edition, after the installation, when I tried to start the service, I got error (from errorlog file) as following.
    (I have researched the internet to find any ideas to fix the problem with no vail, any assistance would be appreciated. - Steve)

    2009-09-03 14:20:45.44 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
     Jul  9 2008 14:43:34
     Copyright (c) 1988-2008 Microsoft Corporation
     Developer Edition on Windows NT 6.0 <X86> (Build 6002: Service Pack 2)

    2009-09-03 14:20:45.44 Server      (c) 2005 Microsoft Corporation.
    2009-09-03 14:20:45.44 Server      All rights reserved.
    2009-09-03 14:20:45.44 Server      Server process ID is 5320.
    2009-09-03 14:20:45.44 Server      System Manufacturer: 'System Manufacturer', System Model: 'System Models'.
    2009-09-03 14:20:45.44 Server      Authentication mode is WINDOWS-ONLY.
    2009-09-03 14:20:45.44 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2009-09-03 14:20:45.44 Server      This instance of SQL Server last reported using a process ID of 17700 at 8/29/2009 5:28:03 PM (local) 8/29/2009 9:28:03 PM (UTC). This is an informational message only; no user action is required.
    2009-09-03 14:20:45.44 Server      Registry startup parameters:
      -d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2009-09-03 14:20:45.49 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2009-09-03 14:20:45.49 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2009-09-03 14:20:45.61 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2009-09-03 14:20:45.68 Server      Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2009-09-03 14:20:45.72 spid7s      Starting up database 'master'.
    2009-09-03 14:20:45.85 spid7s      Resource governor reconfiguration succeeded.
    2009-09-03 14:20:45.85 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2009-09-03 14:20:45.85 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2009-09-03 14:20:45.86 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2009-09-03 14:20:45.89 spid7s      SQL Trace ID 1 was started by login "sa".
    2009-09-03 14:20:45.89 spid7s      Starting up database 'mssqlsystemresource'.
    2009-09-03 14:20:45.91 spid7s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
    2009-09-03 14:20:46.08 spid10s     Starting up database 'model'.
    2009-09-03 14:20:46.08 Server      Error: 26057, Severity: 16, State: 1.
    2009-09-03 14:20:46.08 Server      Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network configuration of the computer. Error: 0x2.
    2009-09-03 14:20:46.08 Server      Error: 17182, Severity: 16, State: 1.
    2009-09-03 14:20:46.08 Server      TDSSNIClient initialization failed with error 0x2, status code 0x80. Reason: Unable to initialize SSL support. The system cannot find the file specified.

    2009-09-03 14:20:46.08 Server      Error: 17182, Severity: 16, State: 1.
    2009-09-03 14:20:46.08 Server      TDSSNIClient initialization failed with error 0x2, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The system cannot find the file specified.

    2009-09-03 14:20:46.08 Server      Error: 17826, Severity: 18, State: 3.
    2009-09-03 14:20:46.08 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2009-09-03 14:20:46.08 Server      Error: 17120, Severity: 16, State: 1.
    2009-09-03 14:20:46.08 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Thursday, September 3, 2009 6:43 PM