SQL Server patching - Should I update our builds to latest SP? or latest SP + latest CU?
Micosoft Cumulative Updates come with the following recommendation:
“A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. This cumulative update
package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2008 R2 service pack that contains the hotfixes in this cumulative update package.”
However, I've talked with a number of SQL Server DBAs from a variety of organizations and many seem to patch their servers right to the lastest CU available regardless of whether their servers have experienced any of the problems that the hotfixes in the
CUs are suppose to fix.
What should we be doing? Only applying CUs if we specifically need them (like Microsoft recommends)? Or applying the latest CU available? What do most SQL Server DBAs do?
Hello,
I only install service packs and CU1 of each service pack. I have had some bad experiences with cumulative updates and I installed them
only when needed. If a CU has a fix for a specific performance issue an instance has, then I install the CU.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Similar Messages
-
Failing - SQL Server Patch Installation
Hi Team:
We are trying to install SQL Server Patch --> SQL Server 2012 SP1 CU3 --> KB2812412 but it is failing with the below issue (error message find in screen shot)
Our Database Engine is running with --> SQL Server 11.0.3350
SSAS is running with --> SSAS 11.0.21600.60
Please through some lights on this...
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)Hi Team:
We are trying to install SQL Server Patch --> SQL Server 2012 SP1 CU3 --> KB2812412 but it is failing with the below issue (error message find in screen shot)
Our Database Engine is running with --> SQL Server 11.0.3350
SSAS is running with --> SSAS 11.0.21600.60
Please through some lights on this...
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)
Hello Satish,
I guess when you installed SP1 for SQL server 2012 you missed to apply for Analysis service .Now what you have to do is first run SQL serevr 2012 SP1 setup and update Anaysis service to latest SP i.e SP1 .After you are done with SP1 installation for
Analysis service then proceed with SQL server 2012 CU3 installation
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Whenever an slowness issue came in sql server how should I start?
whenever a slowness issue or performance issue came in sql server how should I start?
Please guide.
ThanksHi Ajay,
All answer given above would be useful to you in some or the other scenario. if you are facing performance issue the approach you take determines how easily and quickly you can find solution.
First thing is know your system how it works for that you need to first baseline a system. A system with 70 % CPU utilization would not always be issue but for some environment it can be. If you know your system very well moment performance issue comes
you would know where is the problem. Wait stats alone is never helpful you must be able to correlate wait stats to what is going on your system. If you know which query is causing issue its easy to see execution plan and tune it. If issue is server wide it
can be due to missing index outdated stats slow disk subsystem etc. So first step is finding the cause. As Uri suggested wait stats are always helpful I use wait stats and refer to below whitepaper by Microsoft for SQL Server troubleshooting
http://technet.microsoft.com/en-us/library/dd672789%28v=sql.100%29.aspx
Remember important thing is knowing your system and that can come from base lining.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
What SQL server version should be installed in BW 3.5?
Dear all,
What SQL server version should be installed in BW 3.5?
1.Does it must install with enterprice version? Or can it use standand version?
2.SQL 2000 is ok? or must use SQL 2005?
3.x32 is ok? or must use x64?
Best regards!
Brian
Edited by: brian allen on Jun 24, 2009 9:22 AM> What SQL server version should be installed in BW 3.5?
>
> 1.Does it must install with enterprice version? Or can it use standand version?
Read the installation guide - Enterprise version only.
> 2.SQL 2000 is ok? or must use SQL 2005?
Both work but I would go for SQL 2005 (or even SQL 2008).
> 3.x32 is ok? or must use x64?
You should use 64bit wherever possible on new installations.
Makrus -
SQL Server 2012 SP2 Cumulative Update 5
We are starting to take a look at Cumulative update 5 for SQL Server 2012 SP2. The Installation was going smooth until the very in, where it sat on trying to start MSSQLServer for several minutes and finally timed out. Why does Cumulative
patch 5 says it failed to start the service when the server is already running? Version number changed, and everthing looks ok, except for the error message in the log file.
Is this a valid installation or do I need to try again?
Thanks.
DJThanks for the reply. The ErrorLog is too large to post in 1 reply. Will post multiple times.
Version of the SQL Server shows 11.0.5582.0
Dj
Post 1
2015-03-24 14:13:23.82 Server Microsoft SQL Server 2012 - 11.0.5582.0 (X64)
Feb 27 2015 18:10:15
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-03-24 14:13:23.82 Server (c) Microsoft Corporation.
2015-03-24 14:13:23.82 Server All rights reserved.
2015-03-24 14:13:23.82 Server Server process ID is 37184.
2015-03-24 14:13:23.82 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-03-24 14:13:23.82 Server Authentication mode is MIXED.
2015-03-24 14:13:23.82 Server Logging SQL Server messages in file 'L:\SQL Server\Log Files\ERRORLOG'.
2015-03-24 14:13:23.82 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2015-03-24 14:13:23.82 Server Registry startup parameters:
-d H:\\System DB\Data\master.mdf
-e L:\SQL Server\Log Files\ERRORLOG
-l G:\\System DB\Logs\mastlog.ldf
2015-03-24 14:13:23.82 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2015-03-24 14:13:24.15 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational
message; no user action is required.
2015-03-24 14:13:24.15 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-24 14:13:24.15 Server Detected 8191 MB of RAM. This is an informational message; no user action is required.
2015-03-24 14:13:24.15 Server Using locked pages in the memory manager.
2015-03-24 14:13:24.15 Server Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
2015-03-24 14:13:24.22 Server This instance of SQL Server last reported using a process ID of 39820 at 3/24/2015 2:09:46 PM (local) 3/24/2015 6:09:46 PM (UTC). This is an informational message only; no user action is required.
2015-03-24 14:13:24.23 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2015-03-24 14:13:24.23 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.
2015-03-24 14:13:24.24 Server Software Usage Metrics is disabled.
2015-03-24 14:13:24.24 spid4s Starting up database 'master'.
2015-03-24 14:13:24.30 spid4s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 14:13:24.32 spid4s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 14:13:24.32 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-03-24 14:13:24.33 Server CLR version v4.0.30319 loaded.
2015-03-24 14:13:24.36 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-24 14:13:39.41 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\\System DB\Data\master.mdf] in database [master] (1). The OS file handle is 0x0000000000000598.
The offset of the latest long I/O is: 0x0000000002a000
2015-03-24 14:13:53.94 spid4s Recovery completed for database master (database ID 1) in 29 second(s) (analysis 3 ms, redo 39 ms, undo 8 ms.) This is an informational message only. No user action is required.
2015-03-24 14:13:54.19 spid4s CHECKDB for database 'master' finished without errors on 2015-03-06 08:35:22.387 (local time). This is an informational message only; no user action is required.
2015-03-24 14:13:54.19 spid4s Resource governor reconfiguration succeeded.
2015-03-24 14:13:54.19 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-03-24 14:13:54.19 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-03-24 14:13:54.21 spid4s Server name is 'Server'. This is an informational message only. No user action is required.
2015-03-24 14:13:54.22 spid4s Failed to verify Authenticode signature on DLL 'S:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.
2015-03-24 14:13:54.22 spid9s Starting up database 'mssqlsystemresource'.
2015-03-24 14:13:54.22 spid14s Starting up database 'msdb'.
2015-03-24 14:13:54.23 spid15s Starting up database 'Mgmt'.
2015-03-24 14:13:54.24 spid16s Starting up database 'Web2'.
2015-03-24 14:13:54.24 spid12s The certificate [Cert Hash(sha1) "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"] was successfully loaded for encryption.
2015-03-24 14:13:54.24 spid18s Starting up database 'Web2A'.
2015-03-24 14:13:54.24 spid9s The resource database build version is 11.00.5582. This is an informational message only. No user action is required.
2015-03-24 14:13:54.25 spid12s Server is listening on [ 'any' <ipv6> 1433].
2015-03-24 14:13:54.25 spid12s Server is listening on [ 'any' <ipv4> 1433].
2015-03-24 14:13:54.25 spid12s Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2015-03-24 14:13:54.26 spid12s Server local connection provider is ready to accept connection on [
\\.\pipe\sql\query ].
2015-03-24 14:13:54.26 Server Server is listening on [ ::1 <ipv6> 1434].
2015-03-24 14:13:54.26 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-03-24 14:13:54.26 Server Dedicated admin connection support was established for listening locally on port 1434.
2015-03-24 14:13:54.26 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This
is an informational message. No user action is required.
2015-03-24 14:13:54.33 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Server.local ] for the SQL Server service.
2015-03-24 14:13:54.33 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Server.local:1433 ] for the SQL Server service.
2015-03-24 14:13:54.39 spid9s Starting up database 'model'.
2015-03-24 14:13:54.42 spid4s 1 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.42 spid4s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2015-03-24 14:13:54.46 spid9s 1 transactions rolled forward in database 'model' (3:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.47 spid9s 0 transactions rolled back in database 'model' (3:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.62 spid9s Clearing tempdb database.
2015-03-24 14:14:17.34 spid9s Starting up database 'tempdb'.
2015-03-24 14:14:27.05 spid19s The Service Broker endpoint is in disabled or stopped state.
2015-03-24 14:14:27.06 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2015-03-24 14:14:27.07 spid19s Service Broker manager has started.
2015-03-24 14:14:27.21 spid15s CHECKDB for database 'Mgmt' finished without errors on 2014-09-14 00:02:54.637 (local time). This is an informational message only; no user action is required.
2015-03-24 14:14:27.58 spid16s CHECKDB for database 'Web2' finished without errors on 2015-03-22 00:00:43.253 (local time). This is an informational message only; no user action is required.
2015-03-24 14:14:27.65 spid4s Database 'master' is upgrading script 'ProvisionAgentIdentity.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.65 spid4s Database 'master' is upgrading script 'no_op.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.93 spid4s Database 'master' is upgrading script 'no_op.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.94 spid4s -----------------------------------------
2015-03-24 14:14:27.94 spid4s Starting execution of dummy.sql
2015-03-24 14:14:27.94 spid4s -----------------------------------------
2015-03-24 14:14:27.94 spid4s Database 'master' is upgrading script 'repl_upgrade.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.94 spid4s Executing replication upgrade scripts.
2015-03-24 14:14:27.99 spid4s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 14:14:28.07 spid4s Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-03-24 14:14:28.09 spid4s Executing sp_vupgrade_replication.
2015-03-24 14:14:28.50 spid4s Upgrading publication settings and system objects in database [Mgmt].
2015-03-24 14:14:28.89 spid4s Upgrading publication settings and system objects in database [Web2].
2015-03-24 14:14:29.98 spid4s Upgrading publication settings and system objects in database [Web2A].
2015-03-24 14:14:30.48 spid4s Could not open database [LEGACY_DSS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_1]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_LS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_NG]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_RSV]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.52 spid4s Upgrading subscription settings and system objects in database [Mgmt].
2015-03-24 14:14:31.17 spid4s Attempting to load library 'xprepl.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 14:14:31.19 spid4s Using 'xprepl.dll' version '2011.110.5582' to execute extended stored procedure 'xp_repl_encrypt'. This is an informational message only; no user action is required.
2015-03-24 14:14:31.19 spid4s Upgrading subscription settings and system objects in database [Web2].
2015-03-24 14:14:31.75 spid4s Upgrading subscription settings and system objects in database [Web2A].
2015-03-24 14:14:32.31 spid4s Could not open database [LEGACY]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_1]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_LS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_NG]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_RSV]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.33 spid4s Attempting to copy article resolvers from SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Replication\ArticleResolver
2015-03-24 14:14:32.59 spid4s sp_vupgrade_replication executed successfully
2015-03-24 14:14:32.59 spid4s Saving upgrade script status to 'SOFTWARE\Microsoft\MSSQLServer\Replication\Setup'.
2015-03-24 14:14:32.59 spid4s Saved upgrade script status successfully.
2015-03-24 14:14:32.59 spid4s Database 'master' is upgrading script 'upgrade_ucp_cmdw_discovery.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:32.92 spid4s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:32.92 spid4s ----------------------------------
2015-03-24 14:14:32.92 spid4s Starting execution of PRE_MSDB.SQL
2015-03-24 14:14:32.92 spid4s ----------------------------------
2015-03-24 14:14:33.08 spid4s Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2015-03-24 14:14:33.17 spid4s -----------------------------------------
2015-03-24 14:14:33.17 spid4s Starting execution of PRE_SQLAGENT100.SQL
2015-03-24 14:14:33.17 spid4s -----------------------------------------
2015-03-24 14:14:33.17 spid4s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
2015-03-24 14:14:33.22 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:14:33.22 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:15:00.06 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\\System DB\Logs\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000790.
The offset of the latest long I/O is: 0x00000000efac00
2015-03-24 14:16:00.87 spid4s DBCC TRACEOFF 1717, server process ID (SPID) 4. This is an informational message only; no user action is required.
2015-03-24 14:16:00.87 spid4s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2015-03-24 14:16:00.88 spid4s
2015-03-24 14:16:00.88 spid4s Creating table temp_sysjobschedules
2015-03-24 14:16:01.00 spid4s
2015-03-24 14:16:01.00 spid4s Alter table sysdownloadlist...
2015-03-24 14:16:01.00 spid4s
2015-03-24 14:16:01.00 spid4s Alter table sysjobhistory...
2015-03-24 14:16:01.02 spid4s
2015-03-24 14:16:01.02 spid4s Alter table systargetservers...
2015-03-24 14:16:01.02 spid4s
2015-03-24 14:16:01.02 spid4s Alter table sysjobsteps...
2015-03-24 14:16:01.09 spid4s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.09 spid4s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.09 spid4s
2015-03-24 14:16:01.09 spid4s -----------------------------------------
2015-03-24 14:16:01.09 spid4s Execution of PRE_SQLAGENT100.SQL complete
2015-03-24 14:16:01.09 spid4s -----------------------------------------
2015-03-24 14:16:01.10 spid4s DMF pre-upgrade steps...
2015-03-24 14:16:01.25 spid4s DC pre-upgrade steps...
2015-03-24 14:16:01.25 spid4s Check if Data collector config table exists...
2015-03-24 14:16:01.25 spid4s Data Collector state before upgrade: 0
2015-03-24 14:16:01.25 spid4s pre_dc100::Check if syscollector_collection_sets_internal table exists...
2015-03-24 14:16:01.25 spid4s pre_dc100::Capturing Collection set status in temp table...
2015-03-24 14:16:01.33 spid4s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2015-03-24 14:16:01.33 spid4s End of DC pre-upgrade steps.
2015-03-24 14:16:01.33 spid4s DAC pre-upgrade steps...
2015-03-24 14:16:01.33 spid4s Starting DAC pre-upgrade steps ...
2015-03-24 14:16:01.33 spid4s End of DAC pre-upgrade steps.
2015-03-24 14:16:01.33 spid4s ----------------------------------
2015-03-24 14:16:01.33 spid4s Starting execution of MSDB.SQL
2015-03-24 14:16:01.33 spid4s ----------------------------------
2015-03-24 14:16:01.39 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.39 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.42 spid4s Checking the size of MSDB...
2015-03-24 14:16:01.60 spid4s
2015-03-24 14:16:01.60 spid4s Setting database option TRUSTWORTHY to ON for database 'msdb'.
2015-03-24 14:16:01.60 spid4s Setting database option RECOVERY to SIMPLE for database 'msdb'.
2015-03-24 14:16:01.63 spid4s ----------------------------------
2015-03-24 14:16:01.63 spid4s Finished execution of MSDB.SQL
2015-03-24 14:16:01.63 spid4s ----------------------------------
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Starting execution of MSDB_VERSIONING.SQL
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Finished execution of MSDB_VERSIONING.SQL
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Dropping view MSdatatype_mappings...
2015-03-24 14:16:01.63 spid4s Dropping view sysdatatypemappings...
2015-03-24 14:16:30.94 spid4s Dropping table MSdbms_datatype_mapping...
2015-03-24 14:16:30.95 spid4s Dropping table MSdbms_map...
2015-03-24 14:16:30.96 spid4s Dropping table MSdbms_datatype...
2015-03-24 14:16:30.96 spid4s Dropping table MSdbms...
2015-03-24 14:16:30.99 spid4s Creating table MSdbms
2015-03-24 14:16:31.00 spid4s Creating table MSdbms_datatype
2015-03-24 14:17:30.96 spid4s Creating table MSdbms_map
2015-03-24 14:17:30.96 spid4s Creating table MSdbms_datatype_mapping
2015-03-24 14:17:30.97 spid4s Definining default datatype mappings
2015-03-24 14:17:30.98 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE8
2015-03-24 14:17:31.08 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE9
2015-03-24 14:17:31.12 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE10
2015-03-24 14:17:31.17 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE11
2015-03-24 14:17:31.22 spid4s Creating datatype mappings for MSSQLSERVER to DB2
2015-03-24 14:17:31.28 spid4s Creating datatype mappings for MSSQLSERVER to SYBASE
2015-03-24 14:17:31.33 spid4s Creating datatype mappings for ORACLE8 to MSSQLSERVER
2015-03-24 14:17:31.38 spid4s Creating datatype mappings for ORACLE9 to MSSQLSERVER
2015-03-24 14:17:31.45 spid4s Creating datatype mappings for ORACLE10 to MSSQLServer
2015-03-24 14:17:50.00 spid4s Creating datatype mappings for ORACLE11 to MSSQLServer
2015-03-24 14:17:59.30 spid4s Creating view MSdatatype_mappings
2015-03-24 14:17:59.31 spid4s Creating view sysdatatypemappings
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_enum_proxy_for_subsystem
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_enum_login_for_proxy
2015-03-24 14:17:59.89 spid4s Dropping signature from: sysmail_delete_mailitems_sp
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_get_startup_info
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_has_server_access
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_get_perf_counters
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_notify
2015-03-24 14:17:59.89 spid4s Dropping signature from: sysmail_delete_log_sp
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_is_sqlagent_starting
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_verify_job_identifiers
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_verify_schedule_identifiers
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_jobproc_caller
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_downloaded_row_limiter
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_post_msx_operation
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_performance_condition
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_job_date
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_job_time
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_alert
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_update_alert
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_job_references
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_all_msx_jobs
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_accountparams_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_generate_target_server_job_assignment_sql
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_generate_server_description
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_principal_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_set_account
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_get_account
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_account_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_operator
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_add_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_defect
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_update_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_enlist
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_delete_profile_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetserver
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_profile_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_enlist_tsx
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_create_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_get_sqlagent_properties
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_alter_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_set_sqlagent_properties
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_drop_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_add_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_add_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_update_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_update_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_delete_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_help_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_add_targetsvrgrp_member
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_admin_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetsvrgrp_member
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_add_profileaccount_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_verify_category
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_update_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_add_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_delete_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_update_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_delete_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_configure_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_configure_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_targetserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_configure_value_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_resync_targetserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_add_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_purge_jobhistory
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_update_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory_full
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_delete_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory_summary
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_logmailevent_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_add_jobserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_start_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_delete_jobserver
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_stop_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_help_jobserver
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_help_status_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_help_downloadlist
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_help_queue_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_enum_sqlagent_subsystems_internal
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_SendMailMessage
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_enum_sqlagent_subsystems
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_isprohibited
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_verify_subsystem
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_SendMailQueues
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_verify_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_ProcessResponse
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_add_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_MailItemResultSets
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_attach_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_process_DialogTimer
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_detach_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_readrequest
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_update_replication_job_parameter
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_GetAttachmentData
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_update_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_RunMailQuery
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_schedule
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_validate_user
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_get_jobstep_db_username
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_send_dbmail
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_verify_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_ExternalMailQueueListener
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobstep_internal
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_sysmail_activate
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_update_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_help_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_write_sysjobstep_log
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_delete_log
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_help_jobsteplog
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_delete_subplan
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_jobsteplog
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_update_subplan_tsx
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_get_schedule_description
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_subplans_by_job
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobschedule
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_open_logentry
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_update_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_close_logentry
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_update_log
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_schedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_update_subplan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_delete_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_verify_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_start
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_get_script
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_update_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_clear_dbmaintplan_by_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_get_composite_job_info
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_maintenance_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobcount
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_maintenance_plan_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobs_in_schedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_manage_jobs_by_login
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_maintenance_plan_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_apply_job_to_targets
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_help_maintenance_plan
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_remove_job_from_targets
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_get_job_alerts
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_start_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_stop_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_monitor_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_cycle_agent_errorlog
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_primary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_get_chunked_jobstep_params
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_secondary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_check_for_owned_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_monitor_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_check_for_owned_jobsteps
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_primary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_sqlagent_refresh_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_secondary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_jobhistory_row_limiter
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_log_shipping_in_sync
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_sqlagent_log_jobhistory
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_log_shipping_get_date_from_file
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_sqlagent_check_msx_version
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_get_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_sqlagent_probe_msx
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_update_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_set_local_time
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_delete_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_multi_server_job_summary
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_remove_log_shipping_monitor_account
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_target_server_summary
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_log_shipping_monitor_backup
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_uniquetaskname
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_log_shipping_monitor_restore
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_addtask
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_change_monitor_role
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_droptask
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_create_log_shipping_monitor_account
2015-03-24 14:17:59.97 spid4s Dropping signature from: trig_targetserver_insert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_add_alert_internal
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_addlogentry
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_add_alert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_listpackages
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_delete_alert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_listfolders
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_alert
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_deletepackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_deletefolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_add_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_sqlagent_is_srvrolemember
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_getpackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_update_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_category_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_getfolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_putpackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_operator_jobs
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_proxy_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_operator_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_credential_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_addfolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_notify_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_subsystems
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_renamefolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_notification
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_subsystem_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_setpackageroles
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_add_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_login_identifiers
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_ssis_getpackageroles
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_update_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_delete_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_add_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_delete_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_jobactivity
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_update_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sqlagent_is_member
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_proxy_permissions
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sem_add_message
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sem_drop_message
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_get_message_description
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_grant_proxy_to_subsystem
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_jobhistory_sem
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_grant_login_to_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_convert_jobid_to_char
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_revoke_login_from_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_revoke_proxy_from_subsystem -
Warning in log after updating SQL server when installing cumulative updates
Every time I install cumulative updates for Lync 2013, when I run the command to update the SQL database which is
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SQLLYNPROD1.domain.local -Verbose
I get the two warnings below in the log. The update works OK and I don't have any issues. I get a warning just for this database for the database itself and the log path. Can't find anything on it searching. Any idea where to start looking
Warning: The
database rtcxds being updated has data file path at
\\SQLLYNPROD1.domain.local\E$\SQLData\rtcxds.mdf and supplied data file path is
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\DbPath\rtcxds.mdf.
Supplied path will be ignored.
Warning: The
database rtcxds being updated has log file path at
\\SQLLYNPROD1.domain.local\F$\SQLLog\rtcxds.ldf and supplied data file path is
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\LogPath\rtcxds.ldf.
Supplied path will be ignored.There is only one CsData folder on the Lync server but the install program is complaining about the RTCXDS database which is on our enterprise backend SQL server. The path above is correct.
\\SQLLYNPROD1.domain.local\E$\SQLData\rtcxds.mdf for data and
\\SQLLYNPROD1.domain.local\F$\SQLLog\rtcxds.ldf for logs
but a bogus path of
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\DbPath\rtcxds.mdf for data and
\\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\LogPath\rtcxds.ldf for logs is being supplied from somewhere to the install program.
Fortunately, the install program knows enough to ignore the supplied path and take what it is given from SQL. Just trying to figure out where this supplied path is coming from. It could be anywhere. As I said, needle in a haystack. -
Which version of SQL Server 2014 should I be using?
Hello,
I'm writing a Visual Basic.NET application for a school network. I am new to databases and made the assumption that I need Microsoft SQL Server (I've gone for the express edition). My plan is to run a copy on the school's server and connect to it through
several instances of my program, each on their own computer on the school network. The server is 64bit so I know I should be getting the 64bit edition. However, I'm not sure whether I should choose LocalDB, Express, Express with Tools, Management Studio Express
or any of the other versions.
Which one should I choose?Hi 08robertsj,
Based on your description, you can install SQL Server 2014 Express with Tools (SQLEXPRWT _x64_ENU.exe)
or SQL Server 2014 Express with Advanced Services (SQLEXPRADV_x64_ENU.exe) on the 64-bit server.
SQLEXPRWT _x64_ENU.exe package contains everything needed to install and configure SQL Server as a database server including the full version of SQL Server 2014 Management Studio. SQLEXPRADV_x64_ENU.exe package is a larger download than “with Tools,” as it
also includes both Full Text Search and Reporting Services.
LocalDB is meant for developers, with it you can simply create and work with databases from code. Express edition includes the SQL Server database engine only. SQL Server Management Studio Express doesn’t not contain the database, but only the tools to manage
SQL Server instances.
For more details about the difference between Express editions, please review the following link.
http://msdn.microsoft.com/en-us/evalcenter/dn434042.aspx
Thanks,
Lydia Zhang -
JOB in Sql Server Agent should run multiple times.
Hi Guys,
I have a ETL SSIS job in Sql Server Agent, Which should run multiple times.
1. For Example : I scheduled a job at 10:00 PM, If the job fails at 10:00 PM it should run automatically again at 10:10 PM, if the job fails again at 10:10 PM then the job should run at 10:40 PM.
If the job gets success at first attempt i.e 10:00 PM, then it should not run at 10:10 PM.
Note : The time difference between jobs is 10 minutes and 30 minutes. And i know that we can run the job at regular intervals.
Thanks in advanceJust add retry attempts to whatever number you want (2 as per your original explanation) in Job step properties as below
Have a logic to include a delay of 10 mins . You can make use of WAITFOR function for that
see
http://www.mssqltips.com/sqlservertip/1423/create-delays-in-sql-server-processes-to-mimic-user-input/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs -
SQL Server 2012 unable to update cumulative update for sql server 2012
Here is the version
Microsoft SQL server 2012 11.02.2100.60X64
Trying to install the update to install sccm2012
Error
There are no SQL server instance or shared feature that can be update on this computer.Hello,
You need CU2 for SQL Server 2012 RTM or later to be able to install SSCM 2012. You can install SP1 for SQL Server 2012 too.
CU2 can be downloaded from the following link:
http://support.microsoft.com/kb/2703275/en-us
When you click on the “Hotfix Download Available” button, make sure you make a click on the “"Show hotfixes for all platforms and languages
(8) " link, then download and install the following file:
SQLServer2012_RTM_CU2_2703275_11_0_2325_x64
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server Express 2012 SP2 Update Only download
where can i find just the SP2 update. We have the base only installed . All I can locate is the full 2012 express with SP2 already installed. Also, I'm assuming I can go right to SP2
Thank you,
RichardIt's here
Microsoft® SQL Server® 2012 Service Pack 2 (SP2)
There is not a separate Service Pack for the different editions.
David
David http://blogs.msdn.com/b/dbrowne/ -
Hi All,
I have patched my 2012 SQL instances running with RTM version to SP2, after the patching got complete i was seeing below messages from summary logs and restarted the server post that, but even after that i see the same messages and the summary.txt file has
not got updated.
My question here is do i need to worry about this or not? I have verified server health check post patching both the instances got upgraded to the new version
11.0.5058.0 and the server health check looks good.
Overall summary:
Final result:
Passed but reboot required, see logs for details
Exit code (Decimal): 3010
Start time: 2015-03-20 16:04:15
End time: 2015-03-20 16:30:15
Requested action: Patch
Instance MSSQLSERVER overall summary:
Final result:
Passed but reboot required, see logs for details
Exit code (Decimal): 3010
Start time: 2015-03-20 16:04:15
End time: 2015-03-20 16:30:15
Requested action: Patch
Instance P001 overall summary:
Final result:
Passed but reboot required, see logs for details
Exit code (Decimal): 3010
Start time: 2015-03-20 16:04:15
End time: 2015-03-20 16:30:15
Requested action: Patchbut even after that i see the same messages and the summary.txt file has not got updated.
Summary.txt is summary report of SQL setup you ran and shows the end result of update. It will not be updated outside setup.
The final result of upgrade was just to reboot. That you have done.
As you confirmed SQL shows new version 11.0.5058.0(SP2)
and the server health check looks good. You are good and need not worry about anything. Patching was completed successfully. -
SQL Server Data Warehouse Creation External or Build Your own
Hi,
In our firm we have a data warehouse which has been created by an external supplier.
The warehouse is being used for some reporting and dashboards but only for a single client, we have yet to fully utilize it.
My question is should we build a new data warehouse or should we push forward with the data warehouse created by the external supplier. I know it would take some time to build a data warehouse however it means we will have full control over it and could
overcome any issues we have with it in house.
It would really help if someone could offer some advice.
ThanksHi Nasa1999,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
How to change sql server reports parameter direction in report builder 3.0
Hi All,
I have created few reports using Report Builder 3.0 with the data source as SharePoint list. i have created a web part page and added the ".rdl"
file, everything is working as expected. Later, i got a requirement to add a parameter to the report , i did that and when i ran the report in SharePoint page, the parameters shows right side and the parameter ribbon shows the dropdown control on top and "Apply
button" at the bottom. When i presented this to my manager, he says the parameter ribbon looks bad and suggested to put both the controls together and also instead of displaying at right side vertical, display it horizontal.
I have below queries
How can i change the direction of parameter ribbon from vertical to horizontal
How can i bring the controls together (e.g. dropdown list control and button)
How can i add buttons on the report in report builder 3.0
How to get/reflect the data in report without refreshing the page.
Can someone please guide me, how to achieve the above functionalities..
MercuryManUnfortunately, where the parameters are located and the button distance away from the parameters are not something you can customize. Here are the options available for customization:
http://msdn.microsoft.com/en-us/library/bb326214.aspx
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
Auto update stats disabled for a user Database in Sql server
While trying to improve the performance of few queries, we found via execution plan that there were lot of Index/Clustered index seeks. Therefore:
First thing we did, was to check our Re-indexing and update stats job which runs weekly for this user DB ( Around 400 GB in size and is used 24*5). The job was running fine.
Later when we ran SP_Blitz, we came to know that auto-update-stats is disabled for this user DB. We expected this to be a possible cause and change it from false to TRUE(Auto update stats)
Also, per SP_blitz there are user-created statistics for this DB. When ran the query to check how many, we saw around 7K user stats out there.
So my question would be 1) setting the Auto update stats to TRUE would require a reboot or once changed i need to track the performance and 2) Should we consider dropping those user created stats or manually look into them one by one.
How should we proceed on this, please suggest, thanks!There may be good reasons for having auto-stats off, but those cases are not very common. It makes a little more sense to turn if off on table level. An example of the latter is a relatively small table, say < 100000 rows where not many new rows are added,
but the existing rows are being updated frequently. This will trigger autostats, but probably without much benefit.
But if you have a system which is very busy during peak times, you may not want autostats take resources during those hours. But if you turn off autostats, you will need to make sure that stats are updated in some other fashion.
Here is a query that you can use review when your statistics last were updated:
SELECT o.name, s.name, stats_date(o.object_id, s.stats_id) AS lastupdated
FROM sys.objects o
JOIN sys.stats s ON s.object_id = o.object_id
--WHERE s.user_created = 1
ORDER BY lastupdated
7000 user-created statistics sounds a little excessive, but I guess they were added to compensate for the autostats that SQL Server were not permitted to create. I would not recommend dropping these statistics, as SQL Server would spend cycles on recreating
them.
You should not have to restart SQL Server for the Auto-update stats setting to take effect; it takes effect immediately.
Erland Sommarskog, SQL Server MVP, [email protected] -
Security Update for SQL Server 2005 SP3 (KB2494113) failed
Here is the Error, Can't get the update install, please help.
KB Number: KB2494113
Machine: MJA01
OS Version: Server 4.0 Service Pack 1 (Build 7601)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4060
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (BKUPEXEC) ENU SP3 2005.090.4035.00 x86 EXPRESS
SQL Server Tools and Workstation Components 2005 ENU SP2 9.2.3042 x86 EXPRESS
Products Disqualified & Reason
Product Reason
SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 4035 installed. Update 4060 is dependent on prerequisite update 4035. Exit setup and refer to the Knowledge Base article to find the prerequisite
patch. Install the prerequisite and rerun the installation.
Processes Locking Files
Process Name Feature Type User Name PID
Product Installation Status
Product : SQL Server Database Services 2005 (BKUPEXEC)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Product : SQL Server Tools and Workstation Components 2005
Product Version (Previous): 3042
Product Version (Final) :
Status : NA
Log File :
SQL Express Features :
Error Description : The product instance SQL Tools does not have prerequisite update 4035 installed. Update 4060 is dependent on prerequisite update 4035. Exit setup and refer to the Knowledge Base article to find the prerequisite
patch. Install the prerequisite and rerun the installation.
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29528Hi Bhanu,
I have uninstall the SQL Server Tools and Workstation Components 2005.
But still unable to upg the SQL Server with the KB249411. Any more ideas?
This is the Summary log.
Time: 09/10/2014 11:09:48.218
KB Number: KB2494113
Machine: MJA01
OS Version: Server 4.0 Service Pack 1 (Build 7601)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4060
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (BKUPEXEC) ENU SP3 2005.090.4035.00 x86 EXPRESS
Products Disqualified & Reason
Product Reason
Processes Locking Files
Process Name Feature Type User Name PID
Product Installation Status
Product : SQL Server Database Services 2005 (BKUPEXEC)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29528
Here is what is log in the SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files (x86)\Common Files\
MSI (s) (B8:F0) [11:09:39:826]: Product: Microsoft SQL Server 2005 Express Edition - Update 'GDR 4060 for SQL Server Database Services 2005 ENU (KB2494113)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program
Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log.
MSI (s) (B8:F0) [11:09:39:827]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.3.4035.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: GDR 4060 for SQL Server Database
Services 2005 ENU (KB2494113). Installation success or error status: 1603.
MSI (s) (B8:F0) [11:09:39:828]: Note: 1: 1729
MSI (s) (B8:F0) [11:09:39:828]: Product: Microsoft SQL Server 2005 Express Edition -- Configuration failed.
MSI (s) (B8:F0) [11:09:39:829]: Windows Installer reconfigured the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.3.4035.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error
status: 1603.
MSI (s) (B8:F0) [11:09:39:829]: Attempting to delete file C:\Windows\Installer\63906e.msp
MSI (s) (B8:F0) [11:09:39:829]: Unable to delete the file. LastError = 32
MSI (s) (B8:F0) [11:09:40:092]: Deferring clean up of packages/files, if any exist
MSI (s) (B8:F0) [11:09:40:092]: Attempting to delete file C:\Windows\Installer\63906e.msp
MSI (s) (B8:F0) [11:09:40:094]: MainEngineThread is returning 1603
MSI (s) (B8:6C) [11:09:40:097]: RESTART MANAGER: Session closed.
MSI (s) (B8:6C) [11:09:40:097]: No System Restore sequence number for this installation.
=== Logging stopped: 9/10/2014 11:09:39 ===
MSI (s) (B8:6C) [11:09:40:098]: User policy value 'DisableRollback' is 0
MSI (s) (B8:6C) [11:09:40:098]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:6C) [11:09:40:098]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (B8:6C) [11:09:40:099]: Restoring environment variables
MSI (s) (B8:6C) [11:09:40:099]: Destroying RemoteAPI object.
MSI (s) (B8:30) [11:09:40:099]: Custom Action Manager thread ending.
MSI (c) (FC:60) [11:09:40:100]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (FC:60) [11:09:40:101]: MainEngineThread is returning 1603
Thanks,
Alice
Maybe you are looking for
-
Can anyone help me with why I can no longer use pages after the latest upgrade to iOS 7.04. I have restored my ipad three times and it still won't work. It s ahuge inconvenience when all my documents are on pages. If you can get back to me as soon as
-
I have an iMac and MBP. I use the imac 7 days a week and the laptop when ever I need to, maybe 3 days a week and all the time when I go away. It'll be in use every day when I get to college next year. I take a huge amount of photos and use the iMac f
-
Windows live messenger for 8130
This is my first blackberry and its verrry confusing lol. I've downloaded live messenger etc but it says service not enabled for this handheld. Any hints please? Solved! Go to Solution.
-
Help on DBMS_JOB in Forms 6i
Hi all, I am trying to use the DBMS_JOB but I am having a bit of difficult. I read the Notes on 'How to use DBMS_JOB package from Forms', I have forgotten the Notes number and followed it and it worked very well for me. For the benefit of those who c
-
Web Gallery and Album pics in sync?
Is there some way to have pictures on my web gallery synced with an album page in iWeb (so I dont take up twice the amount of space)?