SQL Server Q&A

Symptoms
You may receive an access violation exception if all the following conditions are true:You connect to a linked SQL server by using remote access.You run the DBCC FREEPROCCACHE Transact-SQL statement on the linked server to remove all elements from the procedure cache.The remote access connection is interrupted when you remove all elements from the procedure cache.You may notice the following short stack dump file that corresponds to the access violation:

* Short Stack Dump* 004AE996 Module(sqlservr+000AE996) (CLob::DestroyDeep+00000026 Line 907+0000000F)* 008CB71E Module(sqlservr+004CB71E) (CXVariant::ClearDeep+00000116 Line 4519+00000000)* 004A4D82 Module(sqlservr+000A4D82) (CXVariant::Clear+00000022 Line 325+00000000)* 004C6F66 Module(sqlservr+000C6F66) (CAutoClearXVariant::~CAutoClearXVariant+00000016 Line 2020+00000016)* 006936A8 Module(sqlservr+002936A8) (CParamExchange::RestoreFromDbParams+00000588 Line 1168+0000000F)* 00692787 Module(sqlservr+00292787) (CRpcInterfaces::Relay+00000AC1 Line 814+00000000)* 00691C80 Module(sqlservr+00291C80) (CStmtExec::XretRemoteExec+00000422 Line 579+00000000)* 00674325 Module(sqlservr+00274325) (CStmtExec::XretExecute+00000465 Line 561+00000041)* 00608FD2 Module(sqlservr+00208FD2) (CMsqlExecContext::ExecuteStmts+00000560 Line 1578+00000010)* 00608657 Module(sqlservr+00208657) (CMsqlExecContext::Execute+00000368 Line 1227+0000000C)* 0063FAA0 Module(sqlservr+0023FAA0) (CSQLSource::Execute+000006D6 Line 1265+00000013)* 007DEAFE Module(sqlservr+003DEAFE) (language_exec+00000A2B Line 735+00000000)* 007E075E Module(sqlservr+003E075E) (process_commands+000001A1 Line 1765+00000009)* 04CF74BD Module(ums+000074BD) (ProcessWorkRequests+00000292 Line 449+0000000D)* 04CF6852 Module(ums+00006852) (ThreadStartRoutine+000000BD Line 263+00000007)* 77C07E53 Module(MSVCRT+00027E53) (endthread+000000AA)* 77E5D33B Module(kernel32+0001D33B) (RegisterWaitForInputIdle+00000043)
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

DateTimeVersionSizeFile name——————————————————————-31-May-200318:452000.80.818.078,400Console.exe25-Jun-200301:012000.80.818.033,340Dbmslpcn.dll25-Apr-200302:12786,432Distmdl.ldf25-Apr-200302:122,359,296Distmdl.mdf30-Jan-200301:55180Drop_repl_hotfix.sql23-Jun-200322:402000.80.837.01,557,052Dtsui.dll23-Jun-200322:402000.80.837.0639,552Dtswiz.dll24-Apr-200302:51747,927Instdist.sql03-May-200301:561,581Inst_repl_hotfix.sql08-Feb-200306:402000.80.765.090,692Msgprox.dll01-Apr-200302:071,873Odsole.sql05-Apr-200301:462000.80.800.062,024Odsole70.dll07-May-200320:412000.80.819.025,144Opends60.dll07-May-200318:47132,096Opends60.pdb02-Apr-200321:482000.80.796.057,904Osql.exe02-Apr-200323:152000.80.797.0279,104Pfutil80.dll22-May-200322:5719,195Qfe469571.sql11-Jul-200317:041,084,147Replmerg.sql04-Apr-200321:532000.80.798.0221,768Replprov.dll08-Feb-200306:402000.80.765.0307,784Replrec.dll11-Jul-200316:561,085,925Replsys.sql01-Jun-200301:012000.80.818.0492,096Semobj.dll31-May-200318:272000.80.818.0172,032Semobj.rll29-May-200300:29115,944Sp3_serv_uni.sql01-Jun-200301:012000.80.818.04,215,360Sqldmo.dll07-Apr-200317:4425,172Sqldumper.exe19-Mar-200318:202000.80.789.028,672Sqlevn70.rll02-Jul-200300:182000.80.834.0180,736Sqlmap70.dll08-Feb-200306:402000.80.765.057,920Sqlrepss.dll25-Jul-200321:452000.80.845.07,553,105Sqlservr.exe25-Jul-200321:4512,755,968Sqlservr.pdb25-Jul-200321:442000.80.845.0590,396Sqlsort.dll08-Feb-200306:402000.80.765.045,644Sqlvdi.dll25-Jun-200301:012000.80.818.033,340Ssmslpcn.dll01-Jun-200301:012000.80.818.082,492Ssnetlib.dll01-Jun-200301:012000.80.818.025,148Ssnmpn70.dll01-Jun-200301:012000.80.818.0158,240Svrnetcn.dll31-May-200318:592000.80.818.076,416Svrnetcn.exe30-Apr-200323:522000.80.816.045,132Ums.dll30-Apr-200323:52132,096Ums.pdb02-Jul-200300:192000.80.834.098,816Xpweb70.dllNote Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
This article describes the Microsoft support policy for SQL Server failover clustering. Microsoft Customer Support Services (CSS) supports SQL Server failover clustering that is based on the failover clustering features of the Microsoft Cluster Service in the following products: Windows 2000 Advanced ServerWindows 2000 Datacenter EditionWindows Server 2003 Enterprise EditionWindows Server 2003 Datacenter EditionWindows Server 2008 Enterprise EditionNote Windows Server 2008 failover clusters only support SQL Server 2005 Service Pack 2 or later versions.
Important Upgrading SQL Server 2000 Enterprise Edition to SQL Server 2005 Standard Edition is not a supported upgrade path. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms143393.aspx(http://msdn2.microsoft.com/en-us/library/ms143393.aspx) If you want a fallback solution when you upgrade the SQL Server 2000 failover cluster instance,we recommend that you perform a new installation of the SQL Server 2005 failover cluster instance because ofextreme recovery measures. Then, migrate the data to the new installation. The current installation will remain intact if unforeseen circumstances prevent the SQL Server 2005 installation from completing in a timely manner.
Microsoft server clusters are only supported on cluster solutions that are listed in the Windows Server Catalog under Cluster Solutions. To view the Windows Server Catalog, visit the following Microsoft Web site:
http://www.windowsservercatalog.com/(http://www.windowsservercatalog.com/)The term “server clusters” means computers that run the Microsoft Cluster Service. The Windows Server 2003 family provides the following types of clustering services: Server Cluster (Failover Cluster) Network Load BalancingCompute Cluster ServerOnly the Server Cluster solutions can be used together with SQL Server for high availability if a node is lost or if a problem exists with an instance of SQL Server. Network Load Balancing may be used in some cases together with stand-alone read-only SQL Server installations. SQL Server Failover Clustered Instances each require a unique group. This requirement is true on cluster disk resources that use drive letters that are unique to the cluster and to each SQL Server Failover Clustered Instance. Each Failover Clustered Instance of SQL Servermust also have at least one unique IP address. Depending on the version that is installed, multiple unique IP addresses may be possible. Additionally, each Failover Clustered Instance must have both virtual server and instance names that are unique to the domain to which the cluster belongs.
Supported SQL Server failover clustering installations must also follow the Microsoft support policy for server clusters, and the Windows Server Catalog/Hardware Compatibility List.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
309395?(http://support.microsoft.com/kb/309395/) The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server CatalogStarting with Windows Server 2003, Microsoft SQL Server 6.5 and Microsoft SQL Server 7.0 clustering will no longer be supported, as noted in the following Microsoft Knowledge Base article:
810391?(http://support.microsoft.com/kb/810391/) SQL Server 6.5, SQL Server 7.0, and MSDE 1.0 support on Windows Server 2003If you cluster SQL Server with any clustering product other than Microsoft Server Clustering, your primary support contact is the third-party cluster solution provider for any support issues that are related to SQL Server. SQL Server was developed and tested by using Microsoft Server Clustering. Third-party clustering solutions that support SQL Server installations should be your primary contact for any installation issues, performance issues, or cluster behavior issues. CSS provides commercially reasonable support for third-party cluster installations in same manner that we do for a stand-alone version of SQL Server.Number of supported nodesThe following is a list of the number of nodes that are supported by each version of Microsoft SQL Server: Microsoft SQL Server 7.0
Microsoft SQL Server 7.0 supports up to two nodes in a failover cluster.Microsoft SQL Server 2000 Enterprise Edition (32-bit)
Microsoft SQL Server 2000 Enterprise Edition (32-bit) supports up to four nodes in a failover cluster.Microsoft SQL Server Enterprise Edition (64-bit)
Microsoft SQL Server Enterprise Edition (64-bit) supports up to eight nodes in a failover cluster.Microsoft SQL Server 2005 Standard Edition (32-bit or 64-bit)
Microsoft SQL Server 2005 Standard Edition supports up to two nodes in a failover cluster.Microsoft SQL Server 2005 Enterprise Edition (32-bit or 64-bit)
Microsoft SQL Server 2005 Enterprise Edition supports up to eight nodes in a failover cluster.Note If you upgrade Microsoft SQL Server 2000 (32-bit) to Microsoft SQL Server Enterprise Edition (64-bit), SQL Server will still only support four nodes.Mounted drivesThe use of mounted drives is not supported on a cluster that includes a Microsoft SQL Server installation. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
819546?(http://support.microsoft.com/kb/819546/) SQL Server 2000 and SQL Server 2005 support for mounted volumes
Note SQL Server 2005 failover cluster instances are not supported on failover cluster instance nodes that are used as domain controllers.
Resolution
SQL Server failover clustering for clusters that are not listed on the HCL in the cluster categoryIf your SQL Server failover cluster solution is not listed in the Windows Server Catalog/Hardware Compatibility List. as a supported “Cluster Solution”, it is considered unsupported and may yield unexpected behavior. However, CSS will offer troubleshooting tips and provide reasonable support if requested. However, CSS does not guarantee that a resolution will be found for non-Windows Server Catalog/HCL cluster solutions.
For support, follow these steps: Before any troubleshooting begins, you must contact the Original Equipment Manufacturer (OEM) to discuss whether your particular cluster implementation is supportable. The OEM can best answer configuration and supportability questions for the cluster hardware.Upon agreement that no solution is guaranteed, and that no incident refund will be provided, CSS can troubleshoot the issue. Microsoft does not guarantee a solution with non-HCL clusters. If no resolution is found, the incident will not be refunded.
If it is not agreed that a solution is not guaranteed, CSS will not troubleshoot the issue and will refund the incident.CSS will use standard troubleshooting processes to isolate the server cluster issue. Some typical troubleshooting methods that are used by CSS include: Use of the Microsoft Knowledge Base. The Microsoft Knowledge Base is available to customers through Microsoft TechNet, or you can visit the following Microsoft Web site:
http://support.microsoft.com(http://support.microsoft.com/)Determine whether the problem can be replicated on supported clusters (where possible).Note If the cluster is not certified, there is no hotfix support available. CSS cannot determine whether the problem is caused by hardware incompatibility or by unwanted software behavior.If there is no solution to the problem, CSS may recommend some constructive alternatives, which include: Having you reproduce the problem on a cluster that is on the Cluster HCL.Asking you to use a cluster solution that is on the Cluster HCL.Having you work with the OEM to get the cluster on the Cluster HCL.Asking you to work with the OEM for a solution. The hardware specifications for server clusters are extremely stringent. The Cluster HCL contains a list of known acceptable cluster configurations that have been tested. You can waste a lot of time by trying to troubleshoot perceived server cluster issues that are being caused by the cluster hardware that you are using.
Some examples of hardware incompatibilities that can cause cluster problems include: SQL Server Failover Clustering installation failures.The cluster solution does not correctly isolate the shared disk and host bus adapters (HBAs) from other devices on the shared bus.The SCSI controller does not support operating in a multiple-initiator environment.The HBA does not correctly handle reservations or release or renew a device on the shared bus.The caching mechanism on the controller is incompatible with the cluster configuration.The network adapters for intra-cluster communication have too high a latency.The RAID controller does not correctly replicate configuration information between controllers.The PCI bus is incorrectly configured and has incorrect adapters in the wrong bus (primary, secondary, tertiary).The controllers are incompatible with the “Physical Disk Resource” type.The SCSI controller does not deploy proper termination. This list does not include all the issues that can cause problems with a server cluster. None of these issues can be detected by CSS. All these issues would typically be discovered if the complete cluster solution were tested for Cluster HCL compatibility.
If a complete cluster configuration is listed for an earlier operating system but is not listed for the newer operating system that you are using, support as documented in this section will be followed.
SQL Server 2005 support for mixed 32-bit and 64-bit SQL Server failover cluster instancesYou must be running Windows Server 2003 Service Pack 1 or a later version. For more information, see the following Microsoft Knowledge Base articles. For IA-64 installations, see the following article in the Microsoft Knowledge Base:
312090?(http://support.microsoft.com/kb/312090/) Cannot use 32-bit resources on a 64-bit server clusterFor X64 installations, see the following article in the Microsoft Knowledge Base:
875423?(http://support.microsoft.com/kb/875423/) Support for 32-bit programs on 64-bit server clusters is included in Windows Server 2003 Service Pack 1 and in x64-based versions of Windows Server 2003Warning Resource DLLs for 32-bit programs cannot run on a 64-bit computer that is running a 32-bit version of Windows Server 2003 without any service packs installed. Therefore, you cannot run 32-bit programs on a 64-bit server cluster. In this scenario, you must use a 64-bit version of the resource DLL.
Limitations of using mixed SQL Server 2000 and SQL Server 2005 failover cluster instancesWhen you use SQL Server 2000 installations and SQL Server 2005 installations on the same cluster, the SQL Server 2000 installations must be installed before you install SQL Server 2005 instances locally or as failover cluster instances. All failover cluster instances will use the SQL Server 2005 Server Cluster resource. This includes the instances of SQL Server 2000.
Additionally, after SQL Server 2005 is installed, SQL Server Native Client is the primary protocol that is used. The changes to the Server Cluster resource DLL and the primary protocol that is used will prevent installation of SQL Server 2000 or re-addition of nodes to SQL Server 2000 failover cluster instances. This occurs because neither the resource DLL nor the primary protocol existed at the time SQL Server 2000 was released and will not be recognized as a valid Server Cluster resource DLL or as a primary protocol for SQL Server failover cluster instances.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
905618?(http://support.microsoft.com/kb/905618/) You may receive a connection error message when you try to connect to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed after you installed SQL Server 2005Stand-alone installations are not affected during initial installation like virtual failover cluster instances. In virtual failover cluster instances, this will prevent the initial installation from completing.
Note After you install SQL Server 2005, SQL Server Service Manager displays the node name instead of the virtual SQL Server 2005 server name. It does this because SQL Server Service Manager was not coded to handle SQL Server 2005, and SQL Server 2005 does not include SQL Server Service Manager.
Windows Server 2008 Failover ClustersOnly SQL Server 2005 Service Pack 2 (SP2) or later versions of SQL Server 2005 are supported with Windows Server 2008 Failover Clusters.
Migrating SQL Server Failover Cluster Instances to New Domain SQL Server 2000, 2005, and 2008 can be migrated to a new domain while clusterd is using domain users for service accounts on Windows 2000 and Windows 2003 Server Failover Clusters. SQL Server installations on Windows 2008 Failover Cluster will require uninstalling SQL Server Database Engine and Analysis Services if installed since Cluster will need to be uninstalled per
269196?(http://support.microsoft.com/kb/269196/) How to move a Windows Server cluster from one domain to anotherPrior to uninstalling SQL Server must be set to use mixed mode security or new domain accounts added to the SQL Server logins and the DATA folder containing system databases must be renamed prior to uninstalling so this folder may be swapped back in once reinstalled to reduce down time. No removal of SQL Server support files, SQL Server Native Client, Integration Services or Workstation Components should be done.

Symptoms
Consider the following scenario:On a Microsoft Windows-based computer, you apply Cumulative Update 3 for SQL Server 2008 Service Pack 1 by using a slipstream installation.For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491?(http://support.microsoft.com/kb/971491/) Cumulative update package 3 for SQL Server 2008 Service Pack 1You tryto uninstall this cumulative update after the slipstream installation.In this scenario, the Full-Text Search component is not completely rolled back to the SQL Server 2008 Service Pack 1 version.
To confirm whether you are encountering this issue, you can check the SQL Server Full-Text Key file (Sql_fulltext_keyfile.dll) in theSQL Server 2008 Installation folder. Typically, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10.<Instance Name>\MSSQLIf this file has a file version that is greater than 10.00.2531.00, the Full-Text Search component is not completely rolled back to the SQL Server 2008 Service Pack 1 version.
Resolution
To work around this problem, follow these steps: In Control Panel, open Add or Remove Programs.
Note For Windows Vista or for Windows Server 2008, open Programs and Features.In the Currently installed programs list, click Microsoft SQL Server 2008, and then click Change/Remove.
Note For Windows Vista or Windows Server 2008, right-click Microsoft SQL Server 2008, and then click Change.In the SQL Server 2008 dialog box, click Remove.Select the appropriate instance or instances, and then click Next.In the Select Features window, select Full-Text Search from the Features list.Complete the Remove SQL Server 2008 wizard, as appropriate for your configuration.Click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Installation Center.Click Installation, and then click New SQL Server stand-alone installation or add features to an existing installation.In the Browse For Folder dialog box, locate the SQL Server 2008 installationfolder that you want, and then click OK.In the SQL Server 2008 Setup window,click Next to move to the Installation Type phase.Click Add Features to an existing instance of SQL Server 2008, select the appropriate instance in the drop-down list, and then click Next to move to the Feature Selection phase.Select Full-Text Search from the Features list.Follow the steps in the Full-Text Search installation wizard.Note There is no workaround for cluster scenarios. To roll back the cumulative update, you must reinstall the clustered instance of SQL Server.

Symptoms
This article describes one possible reason as to why a Data Transformation Services (DTS) package created in Microsoft Visual Basic code may fail with an access violation (AV) error message.
When you create a DTS package by using the WITHEVENTS keyword, and you then run the DTS package from within Microsoft Visual Basic code, the package fails with an access violation and the following error message occurs:

Microsoft dts package provider generated code execution exception;
exception access violation 2147221499.Need to run the object to
perform this operation.
Resolution
The following five events are associated with a DTS package when the DTS package is created by using the WITHEVENTS clause:

Private Sub <object>_OnError(ByVal EventSource As String, _ByVal ErrorCode As Long, _ByVal Source As String, _ByVal Description As String, _ByVal HelpFile As String, _ByVal HelpContext As Long, _ByVal IDofInterfaceWithError As String, _ByRef pbCancel As Boolean)Private Sub <object>_OnFinish(ByVal EventSource As String)Private Sub <object>_OnProgress(ByVal EventSource As String, _ByVal ProgressDescription As String, _ByVal PercentComplete As Long, _ByVal ProgressCountLow As Long, _ByVal ProgressCountHigh As Long)Private Sub <object>_OnQueryCancel(ByVal EventSource As String, _ByRef pbCancel As Boolean)Private Sub <object>_OnStart(ByVal EventSource As String)If code for these events is not present, the error message described in the “Symptoms” section occurs.
For more information about these events, please see the following article in the Microsoft Knowledge Base:
221193?(http://support.microsoft.com/kb/221193/) How to install Data Transformation Services (DTS) event handlers in Visual Basic

Symptoms
This article provides general guidelines to help you decide which type of antivirus software to run on the computers that are running SQL Server in your environment.
Resolution
Microsoft strongly recommends that you individually assess the security risk for each computer that is running SQL Server in your environment and that you select the tools that are appropriate for the security risk level of each computer that is running SQL Server. Additionally, Microsoft recommends that before you roll out any virus protection project, test the whole system under a full load to measure any changes to stability and performance.
Virus protection software requires some system resources to execute. You must perform testing before and after you install your antivirus software to determine if there is performance impact to the computer that is running SQL Server.
Security risk factorsThe value to your business of the information that is stored on the computer.The required security level for that information.The cost of losing access to that information.The risk of either virus or bad information propagating from that computer.
High-risk serversAny server is at some risk of infection. The highest risk servers generally meet one or more of the following criteria:The servers are on the public Internet.The servers have open ports to servers that are not behind a firewall.The servers read or execute files from other servers.The servers run HTTP servers, such as Microsoft Internet Information Services (IIS) or Apache. (For example: SQL XML for SQL Server 2000.)The servers are also hosting file shares.The servers use SQL Mail to handle inbound or outbound e-mail messages.Servers that do not meet the criteria for a high-risk server are generally at a lower risk, although not always.
Virus tool typesActive virus scanning: This type of scanning checks incoming and outgoing files for viruses.Virus sweep software: Virus sweep software scans existing files for file infection. It detects files after they are infected with a virus.This type of scanning may cause the following SQL Server database recovery and SQL Server full-text catalog file issues:If the virus sweep has opened a database file and still has it open when SQL Server tries to open the database (such as when SQL Server starts or when SQL Server opens a database that AutoClose has closed), the database to which the file belongs might be marked suspect. The SQL Server database files typically have the .mdf, .ldf, and .ndf file suffixes.If the virus sweep software has a SQL Server full-text catalog file open when the Microsoft Search service (MSSearch) tries to access the file, you may experience problems with the full text catalog.Vulnerability scanning software: The Microsoft Security Tool Kit CD includes best practice guidelines, information about securing your system, and service packs and patches that can protect your system against virus attacks. It also provides Microsoft tools to help you secure your systems and keep them secure. To download it, visit the following Microsoft Web site:
http://www.microsoft.com/security/(http://www.microsoft.com/security/)Antispyware software: Spyware and unwanted software refers to software that performs certain tasks on your computer, typically without your consent. For more information about how to help protect the computer from spyware and unwanted software, visit the following Microsoft Web site:
http://www.microsoft.com/protect/computer/spyware/default.mspx(http://www.microsoft.com/protect/computer/spyware/default.mspx)Additionally, Microsoft has released the Microsoft Windows Malicious Software Removal Tool to help remove specific, prevalent malicious software from computers that are running Microsoft Windows Server 2003, Microsoft Windows XP, or Microsoft Windows 2000. For more information about the Microsoft Windows Malicious Software Removal Tool, click the following article number to view the article in the Microsoft Knowledge Base:
890830?(http://support.microsoft.com/kb/890830/) The Microsoft Windows Malicious Software Removal Tool helps remove specific, prevalent malicious software from computers that are running Windows Vista, Windows Server 2003, Windows XP, or Windows 2000
Directories to exclude from virus scanningWhen you configure your antivirus software settings, make sure that you exclude the following files and directories from virus scanning. Doing this improves the performance of the files and helps make sure that the files are not locked when the SQL Server service must use them. However, if these files become infected, your antivirus software will not unable to detect the infection.SQL Server data files
These files usually have one of the following file name extensions:.mdf.ldf.ndfSQL Server backup files
These files frequently have one of the following file name extensions:.bak.trnFull-Text catalog filesThe directory that holds Analysis Services data
Note The directory that holds all Analysis Services 2005 data and Analysis Services 2008 data is specified by the DataDir property of the Analysis Services instance. By default, the path of thisdirectory is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Data.If you use Analysis Services 2000, you can view and change the data directory by using Analysis Manager. To do this, follow these steps:In Analysis Manager, right-click the server, and then click Properties.In the Properties dialog box, click the General tab.The directory appears under Data folder.The directory that holds Analysis Services temporary files that are used during Analysis Services processing
Note The directory that holds all Analysis Services 2005 and Analysis Services 2008 temporary files during processing is specified by the TempDir property of the Analysis Services instance. By default, this property is empty. When this property is empty, the default directory is used. This directory is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Data. If you use Analysis Services 2000, you can view and change the directory that holds temporary files in Analysis Manager. To do this, follow these steps:In Analysis Manager, right-click the server, and then click Properties.In the Properties dialog box, click the General tab.On the General tab, notice Note the directory under Temporary file folder.
Optionally, you can add a second temporary directory for Analysis Services 2000 by using the TempDirectory2 registry entry. If you use this registry entry, consider excluding from virus scanning the directory to which this registry entry points.For more information about the TempDirecotry2 registry entry, see the “TempDirectory2″ section of the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa902654(SQL.80).aspx#sql2k_anservregsettings_topic52(http://msdn.microsoft.com/en-us/library/aa902654(SQL.80).aspx#sql2k_anservregsettings_topic52)Analysis Services backup files
Note By default, in Analysis Services 2005 and in Analysis Services 2008, the backup file location is the location that is specified by the BackupDir property. By default, this directory is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Backup. You can change this directory in the Analysis Services instance properties. Any backup command can point to a different location. Or, the backup files may be copied elsewhere.The directory that holds Analysis Serviceslog files
Note By default, in Analysis Services 2005 and in Analysis Services 2008, the backup file location is the location that is specified by the LogDir property. By default, this directory is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Log.Directories for any Analysis Services 2005 or Analysis Services 2008 partitions that are not stored in the default data directory
When you create the partitions, these locations are defined in the Storage location section of the Processing and Storage Locations page of the Partition Wizard.
Considerations for clusteringYou can run antivirus software on a SQL Server cluster, but you must make sure that the antivirus software is a cluster-aware version. Contact your antivirus vendor about cluster-aware versions and interoperability.
If you are running antivirus software on a cluster, make sure that you also exclude these locations from virus scanning:Q:\ (Quorum drive)c:\Windows\ClusterIf you back up the database to a disk or if you back up thetransaction log to a disk, you can exclude the backup files from the virus scanning.

Symptoms
When you use SQL Server Management Studio in Microsoft SQL Server 2005 to connect to an instance of Microsoft SQL Server 2008, you may experience the following problems.
Problem 1When you open or delete a maintenance plan, you receive the following error message:

Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
While trying to find a folder on SQL an OLE DB error was encountered with error code 0×80040E14 (Could not find stored procedure ‘msdb.dbo.sp_dts_getfolder’.).
Problem 2When you copy a database from an instance of SQL Server 2008 to an instance of SQL Server 2005, you receive the following error message:

Message:Executed as user: UserName. …0.0.1080.5 for 32-bitCopyright (C) Microsoft Corp 1984-2005. All rights reserved.Started:TimeProgress: Date TimeSource: SATEESP-MAIN_SATEESP-MAIN_Transfer Objects TaskTask just started the execution.: 0% completeEnd ProgressError: Date TimeCode: 0×00000000Source: SATEESP-MAIN_SATEESP-MAIN_Transfer Objects TaskDescription: An exception occurred while executing a Transact-SQL statement or batch.StackTrace:at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand)at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query)at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)at Microsoft.Sq…The package execution fa…The step failed.
Problem 3When you create a table or a view, you receive the following error message:

Microsoft.SqlServer.Types (Error)
Messages
Either the object or one of its properties is not supported on the target server version. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3207.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.UnsupportedVersionException&LinkId=20476
Resolution
The fix for this issue was first released in Cumulative Update5. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
943656?(http://support.microsoft.com/kb/943656/LN/) Cumulative update package 5 for SQL Server 2005 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137?(http://support.microsoft.com/kb/937137/LN/) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was releasedMicrosoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.