Friday, July 31, 2009

SQL Server upgrade versions

Reference: http://msdn.microsoft.com/en-us/library/ms143393.aspx

Notes from VMware VSphere Tour

In no particular order
  • Fault Tolerance (FT) can only be enabled for 1-CPU VMs and must used shared storage.
  • Data Recovery (DR) images cannot be backed up to tape.
  • With Netapp storage, the have Snap Manager for Virtual Infrastructure (SMVI) that plugs into vCenter APIs to backups for VMs.

SQL Service account requirements

If you don't want to just make your service account(s) part of the local administrators group, here are the user rights that you need to know...

For SQL 2000, a service account requires these user rights:

  • Act as Part of the Operating System = SeTcbPrivilege
  • Bypass Traverse Checking = SeChangeNotify
  • Lock Pages In Memory = SeLockMemory
  • Log on as a Batch Job = SeBatchLogonRight
  • Log on as a Service = SeServiceLogonRight
  • Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
For SQL 2005, it's somewhat more complicated, depending on what service the account is for:

SQL Server

Default instance: SQLServer2005MSSQLUser$ComputerName$MSSQLSERVER
Named instance: SQLServer2005MSSQLUser$ComputerName$InstanceName

  • Log on as a service
  • Act as part of the operating system (only on Windows 2000)
  • Log on as a batch job
  • Replace a process-level token
  • Bypass traverse checking
  • Adjust memory quotas for a process
  • Permission to start SQL Server Active Directory Helper
  • Permission to start SQL Writer

SQL Server Agent

Default instance: SQLServer2005SQLAgentUser$ComputerName$MSSQLSERVER
Named instance: SQLServer2005SQLAgentUser$ComputerName$InstanceName

  • Log on as a service
  • Act as part of the operating system (only on Windows 2000)
  • Log on as a batch job
  • Replace a process-level token
  • Bypass traverse checking
  • Adjust memory quotas for a process

Analysis Services

Default instance: SQLServer2005MSOLAPUser$ComputerName$MSSQLSERVER
Named instance: SQLServer2005MSOLAPUser$ComputerName$InstanceName

  • Log on as a service

Reporting Services

Default instance: SQLServer2005ReportServerUser$ComputerName$MSSQLSERVER and SQLServer2005ReportingServicesWebServiceUser$ComputerName$MSSQLSERVER
Named instance: SQLServer2005ReportServerUser$ComputerName$InstanceName and SQLServer2005ReportingServicesWebServiceUser$ComputerName$InstanceName

  • Log on as a service

Integration Services

Default or named instance: SQLServer2005DTSUser$ComputerName

  • Log on as a service
  • Permission to write to application event log
  • Bypass traverse checking
  • Create global objects
  • Impersonate a client after authentication

Full-Text Search

Default instance: SQLServer2005MSFTEUser$ComputerName$MSSQLSERVER
Named instance: SQLServer2005MSFTEUser$ComputerName$InstanceName

  • Log on as a service

SQL Server Browser

Default or named instance: SQLServer2005SQLBrowserUser$ComputerName

  • Log on as a service

SQL Server Active Directory Helper

Default or named instance: SQLServer2005MSSQLServerADHelperUser$ComputerName

  • No special rights

References: http://support.microsoft.com/kb/283811

http://msdn.microsoft.com/en-us/library/ms143504(SQL.90).aspx

Thursday, July 30, 2009

User rights required for IIS

Below are User Rights required for an IIS server:

  • Log on Locally
    Administrators
    IUSR_ (Anonymous)
    Users (authentication required)
  • Access this computer from the Network
    Administrators
    ASPNet (.NET Framework)
    IUSR_ (Anonymous)
    IWAM_
    Users
  • Log on as a Batch Job
    ASPNet
    Network
    IUSR_
    IWAM_
    Service
  • Logon as a Service
    ASPNet
    Network
  • Bypass Traverse Checking
    Administrators
    IUSR_ (Anonymous)
    Users (Basic, Integrated, Digest)
    IWAM_
Reference: http://support.microsoft.com/kb/271071

Wednesday, July 29, 2009

Moving event log files

To move Event Viewer log files to another location on the hard disk, follow these steps:

  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate and click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
  4. Click the subkey that represents the event log that you want to move, for example, click Application.
  5. In the right pane, double-click File.
  6. Type the complete path to the new location (including the log file name) in the Value data box, and then click OK. For example, if you want to move the application log (Appevent.evt) to the Eventlogs folder on the E drive, type e:\eventlogs\appevent.evt.
  7. Repeat steps 4 through 6 for each log file that you want to move.
  8. Click Exit on the Registry menu.
  9. Restart the computer.
Reference: http://support.microsoft.com/kb/315417

Automatic backup of event log files

At registry entery: HKLM/System/CurrentControlSet/Services/Eventlog:
  • Add regkey: AutoBackupLogFiles <> 0 to logfile you want to setup auto-backup for.
Reference: http://msdn.microsoft.com/en-us/library/aa363648(VS.85).aspx

Multiple IP websites on a single server

Reference: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/b77cf015-017f-489c-9b5b-65ca4a679392.mspx?pf=true