Security patch MS11-049 needed for sql 2008 R2 SP2

My Database engine version is:
SQL
Server 2008 R2(SP2)
- 10.50.4260.0(X64)
Jul 11 2012 15:47:13
Copyright(c)
Microsoft Corporation Enterprise Edition(64-bit)
on
Windows NT 6.1
<X64>(Build
7601:
Service Pack 1)(Hypervisor)
According to KB2494086 this security patch is applicable for SQL Server 2008 R2 RTM. Does this vulnerability addressed in SQL 2008 R2 Service Pack 2?
Thanks,
TRouf

Hello,
That update was already part of SP1 and it is part of SP2 too.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Where is the management Studio for SQL 2008 Express?

Can anyone point me to where I can download the management studio for SQL 2008 Express.
I've downloaded and installed SQL 2008 Express without problem but can't find the management studio.
Help.

Paradox1 said:
The 2008 version of the Management Studio is not a stand alone installation and can only be installed as part of the SQL Server 2008 Express with Tools or Advanced installation.
Like many others, I spent countless hours trying to figure out how to install the Management Studio for SQL Server 2008 Express - Advanced installation (same should apply to the w/ Tools version). What happened in my case was that I installed Visual Studio 2008 Express and during that process a stripped down "Instance" of SQL Server 2008 was installed that did not include the Management Studio. Through much pain and torture I learned that the Management Studio can only be installed during installation of the first instance. To delete that first instance, you must go to "Add or Remove Programs" and remove "Microsoft SQL Server 2008". The removal process will only remove one instance at a time and if you have installed more than one instance you need to keep going until all instances have been removed and the application completely disappears from the Add or Remove Programs" dialog. Note: You do not need to uninstall any of the other SQL Server 2008 applications that also appear in the "Add or Remove Programs" dialog. Then go back through the install process as follows: Double click on SQLEXPRADV_x86_ENU.exe to load the SQL Server Installation Center and then go to Installation > New SQL Server stand-alone installation. Then proceed through all of the installation steps until you get to “Feature Selection” and click on “Select All” to toggle on all of the Shared Features, which should include Management Tools - Basic.Continue the process from there and you should be good to go. Hopefully this will help others to avoid much of the pain that many of us have already experienced.

Issue With Report Builder After Installing SP3 for SQL 2008 R2

Hello. We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend. You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
Application url   :
http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
  + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [10/15/2014 9:35:56 AM] : Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
* [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
* [10/15/2014 9:36:29 AM] : Installation of the application has started.
* [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
* [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Hi DMcGarveyt,
This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

What charger do I need for my 2008 macbook pro 15"

what charger do I need for my 2008 macbook pro 15"?

This one:
http://store.apple.com/us/product/MC556LL/B/apple-85w-magsafe-power-adapter-for- 15-and-17-inch-macbook-pro
Ciao.

SQL 2014 license for SQL 2008

Hi,
I'm purchasing SQL 2014 license.
Can I use the SQL 2014 license for SQL 2008 or 2012.
Thanks,
Sathish
Sathish

Hi Sathish,
For more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the
Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Regards,
Elvis Long
TechNet Community Support

Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

Hi Guys,
Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
it is fine to do but some feedback would be good, it is not something I have done before.
All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
using a separate dedicated SQL server.
Thanks, Chris.

As long as your collations and permissions are the same as before it
should not be a problem. That sad i could not find any other documentation saying it's not supported.
I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

SQL 2008 R2 SP2 release to WSUS

Hello,
With the recent release of SQL 2008 R2 SP2 I was curious as to when Microsoft will be pushing it out to WSUS services? I've already done some testing in our environment with a manual download of it, but I was hoping to release it to my production servers
for a upcoming maintenance night through the proper channels in WSUS. I haven't been able to find any further details on the average release to WSUS time-frame, so I was hoping someone here could shed some light on the matter.
Thanks in advance,

Hi everyone, here is the official word on this from Microsoft
Just finished the brainstorm with our security guys and did some internal search, please refer to below details.
Between June 21 2012 and August 14th 2012, the internal servers which sign Microsoft software were misconfigured, as a result the signatures on a significant number of internally and externally distributed software
by Microsoft will expire prematurely on 01/10/2013 . The result of the signature expiration is that software binaries will be viewed as untrusted, causing them to be invalidated by Microsoft Update, fail installation, and/or detected by 3rd party security
software. This issue is not limited to Windows operating systems nor is it limited to Security Updates; it may have unexpected consequences across all products, as a full listing of affected products is still under investigation. Depending on how the
different products were signed, there are several expiration “milestones” which will occur between November 2012 and summer 2013.
As a failsafe mitigation, Windows released a bulletin in October as Microsoft Security Advisory (2749655)
http://technet.microsoft.com/en-us/security/advisory/2749655
This effectively catches the WinVerifyTrust API calls in the operating system and returns success to the calling program (e.g. SQL Server) if a specific faulty certificate is detected.
What SQL Server Products were affected: One of the SQL Server components that was affected was SQL Server 2008 R2 SP2 that was released in July. For this reason, SQL Server 2008 R2 SP2 was scheduled
to be released via WSUS in August but was put on hold when this issue surfaced. During the testing, Other than Untrusted Publisher errors when executing a small number of affected release packages, and CAPI2 Event Log errors on WinVerifyTrust calls, no ‘hard’
SQL Server installation or runtime failures have been identified. For this reason, we are not re-releasing SQL Server 2008 R2 SP2.
SQL Server 2008 R2 SP2 is not being released to Windows update because it is affected by the issue described in the
Microsoft Security Advisory (2749655)
http://technet.microsoft.com/en-us/security/advisory/2749655.
Users are required to get the update via download center.
SP2 is the only update that is affected by this issue and future updates will continue to be made available via WSUS.
In a word, honest speaking, this is a Microsoft product issue, and so I’m afraid manual installation would be the only choice. I will mark this case as non-decrement. Sincerely apologize for the inconvenience for
you.
Thanks, Michael.

Problems install SCCM 2012 with remote sql 2008 r2 sp2

I am having issues installing sccm 2012 on a remote sql 2008 r2 sp2 server on a seperate instance.
I get the error "The network path was not found"
if i point it at the primary instance it will let me continue but i cannot install sccm into that instance.
I have turned off dynamic ports and set a static port but I do not see where i can enter that in the installer.
I cannot seem to verify is the ssb port is working correctly or not.
my account is local admin on both servers and a sql sysadm.
There is no firewall between servers.
Any suggestions?
Regards
Don

SPN is setup to AUTO register and is working. remote sql is not a cluster. Windows firewall on both servers is disabled. Sql browser is enabled and started. we have a group for system center that contains site servers and this group
is in the local admin of both servers and sysadm inside of sql server.
Why we are consolidating all or our lesser sql servers into a larger one.
Snipt of the log.
12/12/2012 2:57:37 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The network path was not found.
], Exception details: [System.IO.IOException: The network path was not found.
Server stack trace:
at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.GetSqlConnection(String databaseName, String serverName, Boolean encrypt)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.CheckSqlConnection(String serverName, String instanceName)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SystemCenter.ConfigMgr.Setup.CheckSqlAsync.EndInvoke(IAsyncResult result)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabasePage.ValidatePage()
at Microsoft.SystemCenter.ConfigMgr.SetupFramework.WizardForm.ActivatePage(String pageId, Boolean goingNext)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)].
12/12/2012 3:01:42 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database ADMIN\master on server YSQL030.srf.local.
12/12/2012 3:01:42 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The network path was not found.
], Exception details: [System.IO.IOException: The network path was not found.

SQL 2008 R2 SP2, CU 1 : There are no SQL Server instances or shared features that can be updated on this computer

Hi, I know this has been posted before, but I couldn't find a solution. Currently I have a SQL 2008 R2 SP2 Enterprise 2 node cluster.
I want to keep it updated, and downloaded CU 1 from here:
http://sqlserverbuilds.blogspot.com
Version from query:
Product Version       Service Pack       Edition
10.50.4033.0          SP2                    Enterprise Edition (64-bit)
When running the installation, I get the window attached.
Any clues?

As per the message you can only update your instance with a CU/KB if the build number will be above 10.52.4321.0 (which seems to be your current build) . As per
http://sqlserverbuilds.blogspot.co.uk/ you already have the latest one available for SQL Server. Hence you wont be able to install anything unless Microsoft comes up with a new CU :)
It seems this is what you already have -
http://support.microsoft.com/kb/2977319/en-us
Now opening any KB article for any CU will have this portion Eg the KB
http://support.microsoft.com/kb/2917531 has the below.
Installation and deployment
We recommend that you test hotfixes before you deploy them in a production environment.
            This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. The updates in
this 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 2012 service pack
      (http://support.microsoft.com/kb/2755533/            )
             that contains the hotfixes in this package.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Will Cumulative Update 12 for SQL Server 2008R2 SP2 fix: Warning: Unable to Verify TimeStamp for Path\ProgramName?

Hello,
I had a server crash recently and our outsource hosting tech support suggested applying Cumulative Upade 12 for SQL server 2008R2 SP2 to fix the issue. The exception from our dump file "Warning: Unable to Verify TimeStamp for Path\ProgramName"
is not in the list of hotfixes for this CU. Do you know if this will fix this issue? The CU warns not to apply the CU if your issue id not addressed by the CU. Here is a portion of the dump file with the relevant error:
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(7e8.2ab4): Unknown exception - code 000042ac (first/second chance not available)
ntdll!NtWaitForSingleObject+0xa:
00000000`777412fa c3 ret
0:240> .sympath srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols;
Symbol search path is: srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
0:240> .reload /f
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlservr.exe
..........Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlos.dll
...............Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for opends60.dll
.......Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BatchParser.dll
....Unable to load image C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for instapi10.dll
*** ERROR: Module load completed but symbols could not be loaded for instapi10.dll
..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlevn70.rll
*** ERROR: Module load completed but symbols could not be loaded for sqlevn70.rll
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.................Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ftimport.dll
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\msfte.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for msfte.dll
*** ERROR: Module load completed but symbols could not be loaded for msfte.dll
...........Unable to load image C:\Windows\System32\sqlncli10.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlncli10.dll
...Unable to load image C:\Windows\System32\1033\SQLNCLIR10.RLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SQLNCLIR10.RLL
*** ERROR: Module load completed but symbols could not be loaded for SQLNCLIR10.RLL
..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpsqlbot.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xpsqlbot.dll
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\XPStar.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for XPStar.DLL
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlscm.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlscm.dll
...*** ERROR: Module load completed but symbols could not be loaded for odbcint.dll
...Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\XPStar.RLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for XPStar.RLL
Thank you,
Steve -

The error message appears to be related to a debug session and not come from the actual crash.
So all I know is that you hade a server crash. I don't even know exactly what that means. Did Windows bite the dust? Or was it only SQL Server?
Assuming the latter, I would expect the SQL Server errorlog to have some information (and that would be ERRORLOG.1 or earlier, since the server have been restarted), but if SQL Server died the output may be incomplete.
There may be also dump files, but as I rarely look into these, I am not sure how to interpret them. But I am quite confident that "Unable to verify TimeStamp..." is not the reason SQL Server went down.
I would suggest the following course:
* If the server is not critical, do nothing. As long as it has onlyl happened once, it has only happened once.
* If the server is critical, open a case with Microsoft if you are not able to figure out the reason yourself. The key here is "Unknown exception - code 000042ac".
* If it happens again, you should absolutely open a case. An important thing here is whether the stack dump is identical or something different. If the stack dumps are identical, you may have hit a bug in SQL Server or the OS, and applying CUs or OS
fixes could help if it is a known issue. If the stack dump is something else, you have ghosts in the machine - that is, bad hardware.
Erland Sommarskog, SQL Server MVP, [email protected]

Cumulative update 5 for SQL Server 2012 SP2 is released

Cumulative update 5 for SQL Server 2012 SP2 is released
https://support.microsoft.com/en-us/kb/3037255
MDS related fix is:
FIX: The notification email link is broken when a special character is part of the URL in SQL Server 2012 MDS
http://support.microsoft.com/en-us/kb/3036201

Hello,
The following blog shows the latest builds (updates) available for each version of SQL Server.
http://sqlserverbuilds.blogspot.com/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Silent Install for SQL 2008 admin tools, to be pushed out via SCCM 2012

Hi I would like to know if you have any information on Silent App installs for MS SOL fetchers only? I really need to know what MSI to use in my Application and any switched i can incorporate for deployment though SCCM 2012.
Thanks,
Manny

Hi,
do you want to install SQL 2008 admin tools? and what tools do you want to install? and what is your application? And do you want to deploy the installation script via SSCM? Please be more clear.

Change installation directory for SQL 2008 SP3 or CU

My C drive is full, Server built long time ago. Not enough space available in C Drive but other local drive have storage.
Is there anywhere i can use my other drive for patching or apply CU.
Env: win 2003 ,SQL 2008 SP1

My C drive is full, Server built long time ago. Not enough space available in C Drive but other local drive have storage.
Is there anywhere i can use my other drive for patching or apply CU.
Env: win 2003 ,SQL 2008 SP1
Hi,
Why dont you move SQL server user data file and log file from C drive to other drives this will create space. It would require a SQL Server restart
Refer this link
http://msdn.microsoft.com/en-GB/library/ms189133%28v=sql.100%29.aspx
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

JDBC 1.2 for SQL 2008

Hi Gurus,
I searched in SAP Marketplace and saw that the JDBC adapter 1.2 posted there is for SQL 2005 server only. May I know where I can download a JDBC 1.2 adapter for the 2008 SQL server? I'm working with XI 7.0.
Thanks all.
Regards,
SAPenthusiast

Hello,
Check these notes:
Note 639702 - JDBC Driver for Microsoft SQL Server
Note 1600699 - Microsoft jdbc driver 1.2 support
I think you can just use the JDBC 1.2 that appears for download in SQL Server 2005. Check http://msdn.microsoft.com/en-us/sqlserver/aa937724 for example. The same driver is used to connect different DB versions.
Cheers,
Diego.

How do I install SQL Management Objects for SQL 2008 on a 2 node cluster?

Hi,
One of the software we use needs the SMO to be installed. This is on a SQL 2008 2 node cluster. In the control-panel, I do NOT see this installed, and I see the client tools SDK installed and I even did a repair of it. I still do not see it.
Can some one please help me with SMO install on this 2 node SQL 2008 cluster? I could not find a working link to install this.
Thanks!
Suresh.
Suresh Channamraju

Hi Suresh,
According to your descriptIon, you need to install SMO on two nodes of SQL 2008 cluster, right?
If you want to develop an application that uses SQL Server Management Objects (SMO), you should select the Client Tools SDK when you install SQL Server. To install the Client TooLs SDK without installing SQL Server, install Shared Management Objects from
the SQL Server 2008 Feature Pack.
http://www.microsoft.com/en-us/download/details.aspx?id=6375
By default, the SMO assemblies are installed in the C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\ directory.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Security patch MS11-049 needed for sql 2008 R2 SP2

Similar Messages

Maybe you are looking for