This is probably a simple question for the SQL Server veterans, but am a bit confused about directories.  I have searched all over, and there is very little information about optimizing this, unless you have an unlimited number of drives (I don't).  I read that it is best to split the log files and data files between two drives.

1)  Since I only have two 15K drives, where should Temp DB go for best performance, on the drive with the log files or data files?  I'm thinking probably the data drive.  I do have a third drive, but it only a 7200 rpm drive, versus 15K for the other two, so probably too slow.

2)  Should the Temp DB Log file go on the Log file drive?

3)  While I am splitting data and log files, is there a preference for drives for the System Database directory?  This is just used for access control, and is not very big, right?

4)  Any suggestions for directory naming conventions when splitting drives?  E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQL_SERVER\MSSQL\Data seems a bit clumsy and long.

Thanks.

Michael

hi All,

Lat week we have upgraded sql server 2008 with sp3.but now user asking us to roll back to sp1.

Please let me know the step by step process for rollback to sp1.

Regards,

Maheshwar Reddy

while installing sql server 2008 r2 i'm getting Not applicable errors, 

The system is  I7 64bit, windows 7 pro.

Microsoft SQL Server 2008 R2 Setup - System Configuration Check Report

Computer Name(s): YONI 
Report Date/Time: 08/04/2013 13:17
Saved to Directory: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130408_131615\SystemConfigurationCheck_Report.htm

Rule Name		Rule Description	Result	Message/Corrective Action
GlobalRules: SQL Server 2008 R2 Setup configuration checks for rules group 'GlobalRules'
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	Passed	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	HasSecurityAndBackupPrivilegesCheck	Checks whether the account that is running SQL Server Setup has the right to back up files and directories, and the right to manage auditing and the security log.	Passed	The account that is running SQL Server Setup has the right to back up files and directories, and the right to manage auditing and security log.
	MediaPathLength	Checks whether the SQL Server installation media is too long.	Passed	The SQL Server installation media is not too long.
	OsVersionCheck	Checks whether the computer meets minimum operating system version requirements.	Passed	The operating system version meets the minimum requirements for this product.
	RebootRequiredCheck	Checks if a pending computer restart is required. A pending restart can cause Setup to fail.	Passed	The computer does not require a restart.
	SetupCompatibilityCheck	Checks whether the current version of SQL Server is compatible with a later installed version.	Passed	Setup has not detected any incompatibilities.
	ThreadHasAdminPrivilegeCheck	Checks whether the account running SQL Server Setup has administrator rights on the computer.	Passed	The account running SQL Server Setup has administator rights on the computer.
	WmiServiceStateCheck	Checks whether the WMI service is started and running on the computer.	Passed	The Windows Management Instrumentation (WMI) service is running.
InstallGlobalRules: SQL Server 2008 R2 Setup configuration checks for rules group 'InstallGlobalRules'
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	Passed	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	Bids2008InstalledCheck	Checks if any of SQL Server 2008 Business Intelligence Development Studio installation exists.	Passed	SQL Server 2008 Business Intelligence Development Studio is not installed.
	BlockInstallSxS	Checks whether there is an existing SQL Server 2008 CTP installation.	Passed	There are no previous CTP installations of SQL Server 2008.
	FacetDomainControllerCheck	Checks whether the computer is a domain controller. Installing SQL Server 2008 R2 on a domain controller is not recommended.	Passed	This computer is not a domain controller.
	FacetPowerShellCheck	Checks whether Windows PowerShell is installed. Windows PowerShell is a pre-requisite of SQL Server 2008 R2 Express with Advanced Services.	Passed	Windows PowerShell is installed or not required.
	FacetWOW64PlatformCheck	Determines whether SQL Server Setup is supported on this operating system platform.	Passed	SQL Server Setup is supported on this operating system platform.
	FusionRebootCheck	Checks if a computer restart is required because of broken fusion ATL. A pending restart can cause SQL Server Setup to fail.	Passed	The computer does not require a restart.
	PerfMonCounterNotCorruptedCheck	Checks if existing performance counter registry hive is consistent.	Passed	The performance counter registry hive is consistent.
	SqlUnsupportedProductBlocker	Checks whether SQL Server 7.0 or SQL Server 7.0 OLAP Services is installed. SQL Server 2008 R2 is not supported with SQL Server 7.0.	Passed	SQL Server 7.0 or SQL Server 7.0 OLAP Services is not installed.
	SSMS_IsInternetConnected	Verifies that the computer is connected to the Internet. When a Microsoft .NET application like Microsoft Management Studio starts, there maybe be a slight delay while the .NET security check validates a certificate.	Passed	The computer is connected to the Internet and .NET security checks can be completed.
	IsFirewallEnabled	Checks whether the Windows Firewall is enabled.	Warning	The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/fwlink/?LinkId=94001 for information about ports to open for each feature.
InstallFeatureSpecificRules: SQL Server 2008 R2 Setup configuration checks for rules group 'InstallFeatureSpecificRules'
	ASSPI64bitsMachineCheck	Checks whether the computer processor meets the 64-bit requirement for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPIExistingFarmMustBeAvailableCheck	Checks to see that SharePoint Server 2010 farm is presently available.	Not applicable	This rule does not apply to your system configuration.
	ASSPIExistingFarmRequiresMoss14FarmCheck	Checks for membership in a SharePoint Server 2010 farm.	Not applicable	This rule does not apply to your system configuration.
	ASSPIExistingFarmRequiresUpgradeCheck	Checks existing farm for SharePoint Server 2010.	Not applicable	This rule does not apply to your system configuration.
	ASSPIIISVersionCheck	Checks for Internet Information Services 7.0 or later. IIS 7.0 or later is required for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPIInstanceNameNotInUseCheck	Checks for the required instance name.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmNeedsUpgradeToO14MossEnterpriseCheck	Checks for an un-configured SharePoint Server 2010.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmRequiresMoss14BitsCheck	Checks whether SharePoint Server 2010 is installed.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmRequiresMossBitsCheck	Checks whether the SharePoint server can be configured.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmRequiresNewAdminSiteCheck	Checks whether the SharePoint Central Administration site name is available.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewO14EnterpriseFarmUnconfiguredCheck	Checks whether Setup will be able to configure the local SharePoint server.	Not applicable	This rule does not apply to your system configuration.
	ASSPINo32BitsOrWowCheck	Checks whether Setup is running in a 64-bit process on a computer that is running a 64-bit operating system. This is required for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPINoExistingIMBICheck	Checks for an existing instance of SQL Server PowerPivot for SharePoint. You can have only one instance of PowerPivot for SharePoint on a computer.	Not applicable	This rule does not apply to your system configuration.
	ASSPIOperationSystemCheck	Checks for the Windows Server 2008 or later operating system. This operating system is required for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPIProvisionResultValidCheck	Checks whether all of the SQL Server PowerPivot for SharePoint instances in the farm are the same version.	Not applicable	This rule does not apply to your system configuration.
	ASSPIRequiresCompleteFarmCheck	Checks whether SharePoint Server 2010 was installed with the "Farm", "Complete" option.	Not applicable	This rule does not apply to your system configuration.
	ASSPISharePointPlatformSupportedCheck	Checks whether SharePoint supports current .Net Framework version.	Not applicable	This rule does not apply to your system configuration.
	ASSPIUserIsFarmAdminCheck	Checks whether the user running Setup is also a SharePoint farm administrator.	Not applicable	This rule does not apply to your system configuration.
	EditionRequirementCheck	Checks whether the SQL Server edition is supported on this operating system.	Passed	This SQL Server edition is supported on this operating system.
	RS_W2K3IA64InstallCheck	Checks whether the operating system is Window 2003 and the architecture is IA64.	Passed	The operating system is not Windows 2003 IA64.
	SharedComponentsUpgradeRule	Checks whether SQL Server 2008 shared components (such as IS, BIDS, Tools, SSMS, or BOL) are present on the machine, because installing SQL Server 2008 R2 shared components will automatically upgrade the existing shared components.	Passed	There are no shared components of SQL Server 2008 already on the machine.
	SlipstreamMediaInfoCheck	Checks whether the language of the original media is the same as the language of the service pack for updating the setup media.	Passed	The language of the original SQL Server 2008 R2 media and the service pack match.
	Sql2005SsmsExpressFacet	Checks whether SQL Server 2005 Express Tools are installed.	Passed	The SQL Server 2005 Express Tools are not installed.
	VSShellInstalledRule	Checks for previous releases of Microsoft Visual Studio 2008	Passed	Previous releases of Microsoft Visual Studio 2008 is not installed or already upgraded to SP1.

Rules Documentation: http://go.microsoft.com/fwlink/?LinkId=157129 
Community: http://go.microsoft.com/fwlink/?LinkId=157128 
Setup Help File: http://go.microsoft.com/fwlink/?LinkId=157127

I have moved the model database by using following method

1. For each file to be moved, run the following statement.

ALTER DATABASE model
 MODIFY FILE ( NAME = modeldev , FILENAME = 'G:\model\model.mdf' )
ALTER DATABASE model
 MODIFY FILE ( NAME = modellog , FILENAME = 'G:\model\modellog.ldf' )

2. Stop the instance of SQL Server to perform maintenance.
3. Move the file or files to the new location.
4. Restart the instance of SQL Server or the server.

While restarting instance of server i am getting following error.

How to solve this error?

I currently have sql 2008 R2 RTM running on Windows Server 2008r2 sp1.  I attempting to install sql 2008r2 sp2.  However, it failed.  I looked at error log.  This is the error that jumped out at me--The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure the specified path is valid and different than the INSTALLSHAREDDIR path.

I have seen some other post about this error, but it seems to be related to installing SQL from the setup and installing a service pack. 

Has anyone run into this installing SP2?  Do you know how I can resolve it?  

Below is the summary log:

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068578304
  Exit facility code:            1204
  Exit error code:               0
  Exit message:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Start time:                    2013-04-07 19:37:52
  End time:                      2013-04-07 19:41:11
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068578304
  Exit facility code:            1204
  Exit error code:               0
  Exit message:                  The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure the specified path is valid and different than the INSTALLSHAREDDIR path.
  Start time:                    2013-04-07 19:40:43
  End time:                      2013-04-07 19:41:09
  Requested action:              Patch

Machine Properties:
  Machine name:                  SYSDB
  Machine processor count:       2
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
  Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                   1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text Search                         1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                        1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services                       1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Management Tools - Basic                 1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Management Tools - Complete              1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Client Tools Connectivity                1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Client Tools Backwards Compatibility     1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Integration Services                     1033                 Standard Edition     10.50.1600.1    No       

Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL2008
  Type:                          RTM
  Version:                       10
  SPLevel:                       2
  KBArticle:                     KB2630458
  KBArticleHyperlink:           http://support.microsoft.com/?kbid=2630458
  PatchType:                     SP
  AssociatedHotfixBuild:         0
  Platform:                      x64
  PatchLevel:                    10.52.4000.0
  ProductVersion:                10.50.1600.1
  GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
  PackageName:                   SQLServer2008R2-KB2630458-x64.exe
  Installation location:         e:\8b0813e6770181867286c924\x64\setup\

Updated product edition:
  Instance             Edition            
  MSSQLSERVER          STANDARD           

User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  False
  CLUSTERPASSIVE:                False
  CONFIGURATIONFILE:            
  ENU:                           True
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  PASSPHRASE:                    *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  UIMODE:                        Normal
  X86:                           False

Rules with failures:

Global rules:

There are no scenario-specific rules.

RODD

newbie:

We need to move a user db from an old server (Win2003 Standard 32bit) to a new one  (Win2008R2 64bit) and I'm asking for suggestions, tips, hints on how to do this with the least amount of problems.

The old server has the entire volume set up as drive C. And it's running SQL Server 2008 Standard unpatched.

The new server has multiple volumes setup, C for the o/s, D for the apps, E for the data, F for the log files, G for the backups.  We've installed SQL Server 2008 Standard, and patched it with SP3 and cumulative update 10.  Pointed the destination folders to the respective drives - App and shared apps on drive D, Data dirs to drive E, log files to drive F, backup to drive G.

So what's the best way to go about doing this with the least amount of problems?  Backup and Restore, Copy, or Copy Wizard, Move, SSIS Import and Export Wizard etc.

I've read these doc's, and they describe different methods for different scenarios which makes me wonder which way is best for what we need to do.

kb189624 Copying Databases to Other Servers. kb190436 Copying Databases with Backup and Restore, kb190923 Copying Data Between Servers, kb 274188 Troubleshooting Orphaned Users".

I'm trying to Install SQL Server 2012.  I have reached Installation Configuration rules and recieved two failures:

"Reporting Services Catalog Database Existence" Failed (A Reporting Services Catalog database exists.  Select a Reporting Services files-only mode installation)

"Reporting Services Catalog Temporary Database File Exists" Failed (The Reporting Services catalog database file exists.  Select a Reporting Services files-only mode installation)

These correspond to:

I'm unsure of what the error reports mean.  Do I run through the installation process again and search out these options?

I'm trying to install a SQL test version.  When doing so I encounter the following error:

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

Data error (cyclic redundancy check).

A link is inclued from MS which indicates that they have no information.  Does anyone have any ideas?

Thank you...

Hi,

I need to organise to patch an SQL 2008 R2 environment up to SP2 level. It is a 4 node active/active/active/active configuration, with 4 named instances. One of the named instances is a distributor, the rest are both publishers and subscriber

I understand that the 'method' of patching replicated servers is distributor -> publisher -> subscriber - however my main question in this scenario is around timeframes and affects on replication.

If I was to patch the distributor first, how long could I leave the distributor at a different version from the publisher and subscriber? I'm assuming for patching the distributor like a normal cluster patch installation I will need to patch and failover to each node in order to ensure they are all patched which I can do - can the distributor be 'left' for potentially a few days to a week on a different SP than the publishers/subscribers?

More than 1 of the named instances are a publisher and a subscriber as well, so would I need to patch all the publishers first, then the subscribers - or should I patch the whole lot (publishers and subscribers) at once?  What is the risk of the publishers/subscribers being on different SP levels - is it only changes to the publication that could affect the replicated environment?

I'm pretty much after a solution with least downtime, and potentially a solution where the 'downtime' can be 'staged', as well as potentially the work so I am not patching for 24 hours straight!

Thanks!
Melissa

Hi,

I got a 2-node sql server 2008 R2 failover cluster (64 bit) to patch SP2. One of the node failed with error during sp2 installation as below. Please check and help.

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
  Start time:                    2013-03-07 20:09:53
  End time:                      2013-03-07 20:19:46
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  The directory 'f:\275f14ca3bc4000435db3d388419a854\' doesn't exist.
  Start time:                    2013-03-07 20:16:40
  End time:                      2013-03-07 20:18:48
  Requested action:              Patch

Detail:

2013-03-07 20:16:00 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:16:00 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:16:00 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:16:00 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:16:00 Slp: Sco: Returning service status Running
2013-03-07 20:16:00 Slp: The following NT service was in a running state prior to patch action: ReportServer
2013-03-07 20:16:00 Slp: Attempting to run patch request for instance: MSSQLSERVER
2013-03-07 20:18:48 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2068709375)
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLBrowser
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLBrowser
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Restoring the following NT service to a running state after patch action: SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser, start parameters
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Service SQLBrowser started
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLWriter
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLWriter
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Restoring the following NT service to a running state after patch action: SQLWriter
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter, start parameters
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter
2013-03-07 20:18:49 Slp: Sco: Service SQLWriter started
2013-03-07 20:18:49 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:49 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:49 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:49 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:49 Slp: Restoring the following NT service to a running state after patch action: ReportServer
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer, start parameters
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer
2013-03-07 20:18:59 Slp: Sco: Service ReportServer started
2013-03-07 20:18:59 Slp: Completed Action: RunPatchAllInstanceAction, returned True
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidatePatchInstanceName due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ExecutePatchCalculateWorkflow due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalCalculateSettings due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidateFeatureSettings due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: AddPackageInstallerEnginesAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: SchedulePackageInstallActionsAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ScheduleUpgradePackageInstallActionsAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: NotifyProgressCountDisplay due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ScheduleConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidationTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PreMsiTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StopPatchedServices due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: CachePatchPage due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: InitializeMsiAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: MsiTimingAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalizeMsiAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PostMsiTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: DowntimeTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StartPatchedServices due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StartupTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PreUninstallTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: UninstallTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: UpgradeMsiTimingAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalizeTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: CreateARPRegKeyAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: NotifyProgressComplete due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Running Action: FinalizeProgressStatus
2013-03-07 20:18:59 Slp: Completed Action: FinalizeProgressStatus, returned True
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Running Action: CloseUI
2013-03-07 20:18:59 Slp: Stop action skipped in UI Mode Full
2013-03-07 20:18:59 Slp: Completed Action: CloseUI, returned True
2013-03-07 20:19:00 Slp: Received request to add the following file to Watson reporting: C:\Users\cwsmain\AppData\Local\Temp\tmp29B5.tmp
2013-03-07 20:19:00 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2013-03-07 20:19:00 Slp: Inner exceptions are being indented
2013-03-07 20:19:00 Slp:
2013-03-07 20:19:00 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
2013-03-07 20:19:00 Slp:     Message:
2013-03-07 20:19:00 Slp:         Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
2013-03-07 20:19:00 Slp:     Stack:
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.GetInputSettingValue(String settingName)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WriteInputSettings(LogProviderSummaryFile summaryLog)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WritePatchSummaryLog(Int32 resultCode, Exception exception)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WriteSummaryLog(Int32 resultCode, Boolean finalResult, Exception exception)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.WriteStatusLogs(Int32 resultCode, Exception e)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.Start()
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
2013-03-07 20:19:00 Slp:     Inner exception type: System.Runtime.InteropServices.ExternalException
2013-03-07 20:19:00 Slp:         Message:
2013-03-07 20:19:00 Slp:                 Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
2013-03-07 20:19:00 Slp:         Stack:
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.Executor.ExecWaitWithCapture(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.Compile(CompilerParameters options, String compilerDirectory, String compilerExe, String arguments, String& outputFile, Int32& nativeReturnValue, String trueArgs)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
2013-03-07 20:19:00 Slp:                 at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
2013-03-07 20:19:45 Slp: Watson Bucket 1
 Original Parameter Values

2013-03-07 20:19:45 Slp: Parameter 0 : SQL2008@RTM@KB2630458

2013-03-07 20:19:45 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject

2013-03-07 20:19:45 Slp: Parameter 2 : System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated

2013-03-07 20:19:45 Slp: Parameter 3 : Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1

2013-03-07 20:19:45 Slp: Parameter 4 : System.Runtime.InteropServices.ExternalException@267

2013-03-07 20:19:45 Slp:
 Final Parameter Values

2013-03-07 20:19:45 Slp: Parameter 0 : SQL2008@RTM@KB2630458

2013-03-07 20:19:45 Slp: Parameter 1 : 0x055C02AC

2013-03-07 20:19:45 Slp: Parameter 2 : 0x86203738

2013-03-07 20:19:45 Slp: Parameter 3 : 0xDF039760@1201@1

2013-03-07 20:19:45 Slp: Parameter 4 : 0xD95CEA3F

2013-03-07 20:19:45 Slp: The following exception occurred while preparing status logs during Watson failure processing: Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\edxytlec.cmdline".
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2013-03-07 20:19:46 Slp: The following exception occurred during Watson failure processing: The directory is not empty.

2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: ----------------------------------------------------------------------
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: Error result: -2068774911
2013-03-07 20:19:46 Slp: Result facility code: 1201
2013-03-07 20:19:46 Slp: Result error code: 1
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: ----------------------------------------------------------------------
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: Error result: -2068774911
2013-03-07 20:19:46 Slp: Result facility code: 1201
2013-03-07 20:19:46 Slp: Result error code: 1

Good day!

I've ran into a serious discussion on SQL server licensing. Even from Microsoft I'm getting controversal answers.

In our organization, we have ISA server 2004 installation acting as a proxy server at our corporate network. Also, we have SQL server 2000 standard installation on the same server; it is used for storing access logs (approx. 15Gb/monthly). An important point is that no user content is stored in the SQL database, no web-cache, only access logs generated by the ISA server.

Now I have two controversal opinions on the licensing. Some people say that the log entries are generated by the users; so, ISA server acts as a "multiplexing device" and therefore we need SQL user CALs for all of our employees who are accessing internet via that ISA server. Others say that as far as the logs are generated by the ISA server itself, it is not "user data", and so far we need only 1 device CAL for the SQL server connection.

At least, they all agree that if SQL server stores turnstile entries, you don't need a license for everyone who passes it.

Would you please help to find out the apropriate licensing scheme?

Hi All,

while installing reporting services to the existing sql server 2008R2 i got the below options.

1>Install the native mode default configuration

2>Install the SharePoint integrated mode default configuration

3>Install,but don't configure Report Server

The above two options are disabled 1>Install the native mode default confirguration2>Install the Sharepoint intergrated mode default confirguration.so i selected the last optionInstall,but don't configure Report Server.Then the installation is completed successfully.

My question is that when am trying to connect to reporting services through the management studio.Am getting below error and not able to see the Reportserver and Report servertemp databases in database engine.

Error:The report services Instance could not be found(Microsoft.Sqlserver.Management.UI.RSClient).

But from Reporting server configuration Manger am able to connect to the report server.

Maheshwar Reddy

Hi, folks

I have been using Arcserve V12 on a Windows 2008 storage server. Arcserve used SQL Express 2005.

Last week I upgraded Arcserve to V16 and during the installation it tried to upgrade SQL 2005 Express to SQL 2008 Express but it failed.

I have been working with Arcserve Support to fix this but we have been going round in circles. Using the domain administrator account initially failed because it did not have the neccessary permissions, but we fixed this. I have also tried uninstalling using the server's local administrator account but we get the same results:

We got to a state were using the Uninstall/Change option from within Programs and Features would successfully report that SQL Server Express has been successfully removed: 'Your SQL Server 2008 removal completed successfully'. However, all the entries are still present in the Programs list:

Microsoft SQL Server 2008
Microsoft SQL Server 2008 Browser
Microsoft SQL Server 2008 Native Client
Microsoft SQL Server 2008 Setup Support Files
Microsoft SQL Server Native Client
Microsoft SQL Server VSS Writer

And, all the folders are still present off Program Files:

C:\Program Files (x86)\Microsoft SQL Server>dir
 Volume in drive C is OS
 Volume Serial Number is 1252-E50F

 Directory of c:\Program Files (x86)\Microsoft SQL Server

15/03/2013  14:49    <DIR>          .
15/03/2013  14:49    <DIR>          ..
09/03/2013  08:17    <DIR>          100
09/03/2013  08:18    <DIR>          80
09/03/2013  12:17    <DIR>          90
04/05/2010  13:37    <DIR>          MSSQL.1
09/03/2013  08:18    <DIR>          MSSQL10.ARCSERVE_DB

The services window shows the following:

Attempting to start a service results in an error message stating the file cannot be found.

I have now uninstalled Arcserve and would like to completely remove SQL Server Express 2008 and start again. Can someone assist me with this please?

I am a complete noob when it comes to SQL Server and have never needed to install or uninstall it on it's own before. If you need further information please ask.

Thanks!

Mark

The installation has been going on for about 2 hours now.  I am wondering for how long I should wait before assuming something is wrong and stop the installation. It is a quad-core machine running Windows 7.  

Hong

Hi gurus

I am new to cluster and Sql, so learning as I go, so take it easy on me

I have a sql cluster already setup and with a few instances on it ,but I need to add a new instance to this cluster, the only problem I have right now is the network name, as I don't understand very well the meaning of this.

1) if I go into my cluster how do I see what network name were used on the existing sql instances, so I can see the Naming Conv they were using

2) if is a new instance that is been created what is the best practice for this network name .

3) can you please bullet the step to add a new instance

again Thanks a bunch for all your help on this 

I'm installing SQL Server 2012 in the lab as an evaluation copy. This is the second time I've done this - did it a very weeks ago as a test install and didn't have any trouble. Now I'm doing it again, making notes this time and it's taking forever to do the "Product update" at the very start of the installation. It's attempting to download a mere 26MB but so far it's taken an hour to download 4MB. I've stopped and restarted the set-up a few times, same result. This is installating from an ISO on Windows Server 2012 running on Hyper-V 2012. All the latest - no expense spared. The internet connection is fine - can download other files from Microsoft (e.g. service packs) at the full speed of the lab internet link: about 5MBit/s.

Any ideas?

Cheers, Rob.

PS. I posted the same screenshot in reply to another message about slow updates but decided to start my own thread as I think this is a different problem.

Hi all,

I have a 2 node cluster. Windows server 2008 r2 and sql server 2012.

First I created the sql cluster with 2 instances DBA 1 and DAB2. then I decided to remove them and rebuild the cluster. I ran the remove node wizard twice for each node and deleted all sql server 2012 stuff from control panel. Now i'm trying to rebuild my instances but it wouldnt go through. the error " the instance name DBA2" is driving me crazy. I ran cluster res I can see my instance is offline but when I try to bring it online or remove it it gives me the message that the resource could not be found.

What Am I missing here?

PLZ help :( 

Hi,

I am getting the following error when trying to install SQL Server 2008 R2 Management Studio (SQLManagementStudio_x86_ENU.exe or SQLManagementStudio_x64_ENU.exe) on a new Toshiba Portege R830-10R:

Another version of Microsoft Visual Studio 2008 has been detected on this system that must be updated to SP1.  Please update all Visual Studio 2008 installations to SP1 level, by visiting Microsoft Update.

I have all Windows Updates installed on this machine and I DO NOT have VS 2008 installed on this computer (VS2008 was never installed on this computer), but VS 2010 SP1 with .Net Framework 4.0 SP1!

I have sent all day trying to install either ones of the above .exe, but always get the same error message.

I have checked the registry and see that I do not have a  HKLM\SOFTWARE\Microsoft\DevDiv\VS key but only a HKLM\SOFTWARE\Microsoft\DevDiv\VC key (probably since I configured VS1010 for C#).  The HKLM\SOFTWARE\Microsoft\DevDiv\VC\Servicing\9.0 contains SP = 1 and SPIndex = 1.

Please help.
Thanks.

Eric

win2008 SBS stand FE SP2 on a HP server. Now, the spare space is too small. I find there are SharePoint database and WSUS database on c drive are too big. I would like to move any of them to e drive. There are MS SQL Server 2005, 2008 and 2008r2 on the server. Unfortunately, both no management studio on 2005 and 2008, only 2008 r2 has it. But, both databases can't be fund on 2008 r2. So, I would like to reinstall 2005 and 2008 to see both databases then, move both of them or only one.

So, can I reinstall 2005 and 2008 or only the management studio of them?

or is there any better way to solve my issue?

Much thank in advance!

George

yxh