Upgrade sql server 2008 to 2008R2 and apply Service pack 3

Hello,
I have a two node cluster (sql server 2008). I would like to upgrade to SQL Server R2 and at the same time would like to patch to Service Pack 3. What would be the best way to accomplish this task with minimal downtime to the users?
This is my plan:
1. Detach any read only databases.
2. Upgrade to 2008 R2 (shared feature only) on passive node (node1).
3. Apply SP3 on passive node in step 2.
4. Swith active node to passive node (node2).
5. Upgrade to 2008 R2 (shared feature only) on node2.
6. Apply SP3 on node2.
7. Upgrade db (instance) on node2 to 2008 R2.
8. Upgrade db (instance) on node1 to 2008 R2.
9. Re-attach read only databases.
Is my procedures correct?
Thank you.

Hello,
Have you seen the following article before?
http://msdn.microsoft.com/en-us/library/ms191295(v=sql.105).aspx
You can slipstream SQL 2008 R2 + SP3.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Upgrade SQL server 2008 r2 to latest available Service Pack in SP 2010 farm.

Hi,
We have 2 server's in the farm ( WFE+App server and SQL server).
We are planning to upgrade SQL server 2008 r2 to latest available Service pack [10.50.6000 (SP3)] version.
So before upgrading SQL server , need to take any necessary actions from SharePoint server side ?
And once patching is done on SQL server, need to run SharePoint Configuration wizard ?
Please provide best way for this upgrade.
Cheers,
RameshNK

You certainly can turn off SharePoint/stop IIS if you wish, but it isn't required. SharePoint will be unavailable during a portion of the SP3 upgrade and will reconnect once SQL is back online.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Uninstall SQL Server 2008 Express R2 and SQL Server 2012 unsuccessfully

HI
I want to uninstall SQL Server 2008 R2 and SQL Server 2012 but it was successful.
When I try to uninstall 2008 R2
It shows the sqlsupport.msi can't find
Warning 26003. Microsoft Server 2008 R2 Setup Support Files cannot be uninstalled because the following products are installed:
SQL Server 2008 R2 SP2 Common Files are installed
SQL Server 2008 R2 Dabtabase Engine Shared
Microsfot SQL Server R2 RsFx Driver
SQL Server 2008 R2 SP2 Database Engine Services
When I uninstall 2012, it shows the SQL Browser has been installed.
Warning 26003. Microsoft SQL sERVER 2012 Setup Support Files cannot be uninstalled because the following products are installed:
SQL Server Browser for SQL Server 2012

I tried to uninsall SQL Server 2008 R2 and SQL Server 2012.
Yes, I did what you said : right click on Microsoft SQL Server 2008 R2 and then uninstall.
System pop up window says :
Warning 26003. Microsoft SQL Server 2008 R2 Setup Support Files cannot be uninstalled because the following products are installed:
SQL Server 2008 R2 SP2 Common Files are installed
SQL Server 2008 R2 Dabtabase Engine Shared
Microsfot SQL Server R2 RsFx Driver
SQL Server 2008 R2 SP2 Database Engine Services
I hope you are uninstalling from Add remove program. Can you first uninstall
SQL Server 2008 R2 SP2 Common Files are installed
SQL Server 2008 R2 Dabtabase Engine Shared
Microsfot SQL Server R2 RsFx Driver
SQL Server 2008 R2 SP2 Database Engine Services
And then uninstall the
Microsoft SQL Server 2008 R2
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 Article
MVP

Applying Service Pack on multiple instance SQL Server 2008 R2 Cluster and Standalone.

Friends,
Its my first time I am applying Service pack to both Standalone and Clustered SQL 2008 R2 servers. I have multiple instances running on both stand alone and Clustered environment. I don't know how to apply pack with multiple instances. Do I need to apply
the service pack each instance one by one or I can just run the pack to each node of cluster and each box of stand alone server? Will I get any multi instance selection option during the installation process so that I can select multiple instances at once??

When installing service pack for multiple instances in a standalone machine, you just run the installer and it lists all the instances eligible for the update. You could do it one by one or do it at the same time. Doing it at the same time saves time and
energy. If you selected multiple instances then you dont have to do anything else.
In case of cluster, if you have multiple instances then you need to be little careful.
Eg: Assume you have a 2 node cluster Node 1 and Node 2. Two instances Instance 1 active on Node 1 and Instance 2 active on Node 2. What I would do in this case is to first failover any one instance to the passive node. Assume I failed over Instance 2 to
Node 1. Now Node 1 is active node for both instance 1 and instance 2 and Node 2 is passive for both instances. At this point I run the service pack on Node 2. Once patching is done, I reboot the node and then failover the instaces one by one to Node
2. At this point both instances 1 and 2 would get upgraded and will be active in Node2. Now Node 1 is passive and so run the update there. Once the service pack is installed, reboot and then fail back Instance 1 back to Node 1. Note: I would also failover
Instance 2 to Node 1 just to confirm that failover works completely after service pack update.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Upgrade SQL Server 2008 R2 enterprise edition to SQL server 2012 slandered edition

Hi everyone,
Need help on below concern.
I have SQL Server 2008 R2 enterprise edition installed. Which contains SSAS cubes, SSIS packages and SSRS Reports.
I need to upgrade it to SQL Server 2012 Standard edition.
How can I achieve this ??
And I don't have much idea in SSIS package migrations.
Please help me to achieve this.
Thanks,
Rohit

Hi,
Please follow side by side approach for upgrade.Get a new windows box and install SQL server 2012 on it
Move databases from SS2008 R2 to SS 2012 by backup restore mechanism.
Move
jobs and logins by Scripting out and running it on SQL SS 2012.See links as well
Please refer to
this link for SSIS package migration
For SSAS please post question in SSAS forum
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

Need clear steps for doing performance tuning on SQL Server 2008 R2 (DB Engine, Reporting Services and Integration Services)

We have to inverstigate about a reporting solution where things are getting slow (may be material, database design, network matters).
I have red a lot in MSDN and some books about performance tuning on SQL Server 2008 R2 (or other) but frankly, I feel a little lost in all that stuff
I'am looking for practical steps in order to do the tuning. Someone had like a recipe for that : a success story...
My (brain storm) Methodology should follow these steps:
Resource bottlenecks: CPU, memory, and I/O bottlenecks
tempdb bottlenecks
A slow-running user query : Missing indexes, statistics,...
Use performance counters : there are many, can one give us the list of the most important
how to do fine tuning about SQL Server configuration
SSRS, SSIS configuration ?
And do the recommandations.
Thanks
"there is no Royal Road to Mathematics, in other words, that I have only a very small head and must live with it..."
Edsger W. Dijkstra

Hello,
There is no clear defined step which can be categorized as step by step to performance tuning.Your first goal is to find out cause or drill down to factor causing slowness of SQL server it can be poorly written query ,missing indexes,outdated stats.RAM crunch
CPU crunch so on and so forth.
I generally refer to below doc for SQL server tuning
http://technet.microsoft.com/en-us/library/dd672789(v=sql.100).aspx
For SSIS tuning i refer below doc.
http://technet.microsoft.com/library/Cc966529#ECAA
http://msdn.microsoft.com/en-us/library/ms137622(v=sql.105).aspx
When I face issue i generally look at wait stats ,wait stats give you idea about on what resource query was waiting.
--By Jonathan KehayiasSELECT TOP 10
wait_type ,
max_wait_time_ms wait_time_ms ,
signal_wait_time_ms ,
wait_time_ms - signal_wait_time_ms AS resource_wait_time_ms ,
100.0 * wait_time_ms / SUM(wait_time_ms) OVER ( )
AS percent_total_waits ,
100.0 * signal_wait_time_ms / SUM(signal_wait_time_ms) OVER ( )
AS percent_total_signal_waits ,
100.0 * ( wait_time_ms - signal_wait_time_ms )
/ SUM(wait_time_ms) OVER ( ) AS percent_total_resource_waits
FROM sys.dm_os_wait_stats
WHERE wait_time_ms > 0 -- remove zero wait_time
AND wait_type NOT IN -- filter out additional irrelevant waits
( 'SLEEP_TASK', 'BROKER_TASK_STOP', 'BROKER_TO_FLUSH',
'SQLTRACE_BUFFER_FLUSH','CLR_AUTO_EVENT', 'CLR_MANUAL_EVENT',
'LAZYWRITER_SLEEP', 'SLEEP_SYSTEMTASK', 'SLEEP_BPOOL_FLUSH',
'BROKER_EVENTHANDLER', 'XE_DISPATCHER_WAIT', 'FT_IFTSHC_MUTEX',
'CHECKPOINT_QUEUE', 'FT_IFTS_SCHEDULER_IDLE_WAIT',
'BROKER_TRANSMITTER', 'FT_IFTSHC_MUTEX', 'KSOURCE_WAKEUP',
'LAZYWRITER_SLEEP', 'LOGMGR_QUEUE', 'ONDEMAND_TASK_QUEUE',
'REQUEST_FOR_DEADLOCK_SEARCH', 'XE_TIMER_EVENT', 'BAD_PAGE_PROCESS',
'DBMIRROR_EVENTS_QUEUE', 'BROKER_RECEIVE_WAITFOR',
'PREEMPTIVE_OS_GETPROCADDRESS', 'PREEMPTIVE_OS_AUTHENTICATIONOPS',
'WAITFOR', 'DISPATCHER_QUEUE_SEMAPHORE', 'XE_DISPATCHER_JOIN',
'RESOURCE_QUEUE' )
ORDER BY wait_time_ms DESC
use below link to analyze wait stats
http://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/
HTH
PS: for reporting services you can post in SSRS forum
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Install sql server 2008 r2 in windows xp service pack3 gives error

After Installing Support Files, a pop up occurs stating that Microsoft SQL Server 2008 R2 installation has encountered an error.
Error Signature: EventType : sql100msi P1 : 10.50.1600.1 P2 : 10.50.1600.1
P3 : sqlncli.msi P4 : 0x2d2816fe P5 : 0x1603 P6 : install_sqlncli can anyone help me

Hello people. I am having much problem trying to get the SQL installed on my computer.
I just added half of error log:
=== Verbose logging started: 5/1/2014 13:27:12 Build type: SHIP UNICODE 4.05.6001.00 Calling process: f:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
===
MSI (c) (94:CC) [13:27:12:770]: Resetting cached policy values
MSI (c) (94:CC) [13:27:12:770]: Machine policy value 'Debug' is 0
MSI (c) (94:CC) [13:27:12:770]: ******* RunEngine:
******* Product: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
******* Action:
******* CommandLine: **********
MSI (c) (94:CC) [13:27:12:770]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (94:CC) [13:27:12:770]: Grabbed execution mutex.
MSI (c) (94:CC) [13:27:12:770]: Cloaking enabled.
MSI (c) (94:CC) [13:27:12:770]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (94:CC) [13:27:12:770]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:A0) [13:27:12:833]: Running installation inside multi-package transaction f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
MSI (s) (2C:A0) [13:27:12:833]: Grabbed execution mutex.
MSI (s) (2C:6C) [13:27:12:848]: Resetting cached policy values
MSI (s) (2C:6C) [13:27:12:848]: Machine policy value 'Debug' is 0
MSI (s) (2C:6C) [13:27:12:848]: ******* RunEngine:
******* Product: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
******* Action:
******* CommandLine: **********
MSI (s) (2C:6C) [13:27:12:848]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (2C:6C) [13:27:13:379]: File will have security applied from OpCode.
MSI (s) (2C:6C) [13:27:13:629]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi' against software restriction policy
MSI (s) (2C:6C) [13:27:13:645]: SOFTWARE RESTRICTION POLICY: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi has a digital signature
MSI (s) (2C:6C) [13:27:13:942]: SOFTWARE RESTRICTION POLICY: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (2C:6C) [13:27:13:942]: End dialog not enabled
MSI (s) (2C:6C) [13:27:13:942]: Original package ==> f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
MSI (s) (2C:6C) [13:27:13:942]: Package we're running from ==> f:\WINDOWS\Installer\250ed1.msi
MSI (s) (2C:6C) [13:27:13:958]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'.
MSI (s) (2C:6C) [13:27:13:958]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:6C) [13:27:13:973]: MSCOREE not loaded loading copy from system32
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'TransformsSecure' is 0
MSI (s) (2C:6C) [13:27:13:989]: User policy value 'TransformsAtSource' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisablePatch' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (2C:6C) [13:27:13:989]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'.
MSI (s) (2C:6C) [13:27:13:989]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:6C) [13:27:14:004]: Transforms are not secure.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'F:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_131426\sqlncli_Cpu32_1.log'.
MSI (s) (2C:6C) [13:27:14:004]: Command Line: ADDLOCAL=SQL_SNAC_CORE,SQL_SNAC_SDK INSTALLSQLSHAREDDIR_32=F:\Program Files\Microsoft SQL Server\ IACCEPTSQLNCLILICENSETERMS=YES REBOOT=ReallySuppress MEDIAPACKAGEPATH=\1033_ENU_LP\x86\setup\x86\ EXTERNALMSICONTROL=1
CURRENTDIRECTORY=f:\41ab42c0be4c457100b4 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=3988
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{79872AB7-3F02-4F99-BDA4-03BBC4644342}'.
MSI (s) (2C:6C) [13:27:14:004]: Product Code passed to Engine.Initialize: ''
MSI (s) (2C:6C) [13:27:14:004]: Product Code from property table before transforms: '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'
MSI (s) (2C:6C) [13:27:14:004]: Product Code from property table after transforms: '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'
MSI (s) (2C:6C) [13:27:14:004]: Product not registered: beginning first-time install
MSI (s) (2C:6C) [13:27:14:004]: Product {4AB6A079-178B-4144-B21F-4D1AE71666A2} is not managed.
MSI (s) (2C:6C) [13:27:14:004]: MSI_LUA: Credential prompt functionality not available on this operating system
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (2C:6C) [13:27:14:004]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (2C:6C) [13:27:14:004]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:6C) [13:27:14:004]: Adding new sources is allowed.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (2C:6C) [13:27:14:004]: Package name extracted from package path: 'sqlncli.msi'
MSI (s) (2C:6C) [13:27:14:004]: Package to be registered: 'sqlncli.msi'
MSI (s) (2C:6C) [13:27:14:004]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'DisableMsi' is 0
MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (2C:6C) [13:27:14:004]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (2C:6C) [13:27:14:004]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (2C:6C) [13:27:14:004]: Running product '{4AB6A079-178B-4144-B21F-4D1AE71666A2}' with elevated privileges: Product is assigned.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'SQL_SNAC_CORE,SQL_SNAC_SDK'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_32 property. Its value is 'F:\Program Files\Microsoft SQL Server\'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding IACCEPTSQLNCLILICENSETERMS property. Its value is 'YES'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MEDIAPACKAGEPATH property. Its value is '\1033_ENU_LP\x86\setup\x86\'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding EXTERNALMSICONTROL property. Its value is '1'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'f:\41ab42c0be4c457100b4'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '3988'.
MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (2C:6C) [13:27:14:004]: DisableAutomaticApplicationShutdown system policy is ignored on this version of Windows.
MSI (s) (2C:6C) [13:27:14:004]: TRANSFORMS property is now:
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (2C:6C) [13:27:14:004]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Application Data
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Favorites
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\NetHood
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\My Documents
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\PrintHood
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Recent
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\SendTo
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Templates
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Application Data
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Local Settings\Application Data
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\My Documents\My Pictures
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Desktop
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs\Administrative Tools
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs\Startup
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Desktop
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Templates
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\WINDOWS\Fonts
MSI (s) (2C:6C) [13:27:14:051]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16

Upgrade sql server 2008 to 2014

Hello,
1- is it possible to install 2014 while 2008 is installed. And then restore the 2008 database into the 2014 version?
2- is 2014 version out and can it be fully used now?
Thanks

SQL Server edition
Definition
Enterprise (64-bit and 32-bit)
The premium offering, SQL Server 2014 Enterprise edition delivers comprehensive high-end datacenter capabilities with blazing-fast performance, unlimited virtualization, and end-to-end business intelligence — enabling
high service levels for mission-critical workloads and end user access to data insights.
https://msdn.microsoft.com/en-us/library/ms144275.aspx
SQL Server Data Tools - Business
Intelligence (SSDT-BI) includes SQL Server Analysis Service Projects, SQL Server Reporting Services
Projects, and SQL Server Integration Services Projects hosted in Visual Studio. SSDT-BI
tools can be downloaded and installed as free tools from the web.
http://blogs.technet.com/b/dataplatforminsider/archive/2013/11/13/microsoft-sql-server-data-tools-update.aspx

Unable to get SQL Server 2008 R2 to start SBSMONITORING service

Hi,
I have been fighting with a Windows 2008 se
rver and trying to get the SQL server ( SBSMONITORING ) Working. I have tried to start the service, always getting the error ' The request failed of the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details
'. Upon doing that, i found a few events in the event viewer. I also attempted a repair install ( as to where I can select a database to repair or the whole thing. ) Does anyone have any idea where i should be looking or what I should be doing? I have logs
of the failed repair install also if anyone wants them.. Help please? Also please excuse my noobness, I don't have much experience with SQL server or anything.
Thanks

This is the event viewer information
Faulting application name: sqlservr.exe, version: 2009.100.2500.0, time stamp: 0x4dfb6221
Faulting module name: sqlservr.exe, version: 2009.100.2500.0, time stamp: 0x4dfb6221
Exception code: 0xc0000005
Fault offset: 0x00000000000687f9
Faulting process id: 0x1ea0
Faulting application start time: 0x01cfc70f5f6a388c
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.SBSMONITORING\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.SBSMONITORING\MSSQL\Binn\sqlservr.exe
Report Id: 9df21a3e-3302-11e4-b861-00155d011601
I am also getting a lot ( i mean, a lot ) of these showing up
The description for Event ID 824 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
incorrect pageid (expected 1:365760; actual 0:0)
read
(1:365760)
5
0x000000b2980000
C:\WSUS\SUSDB\\UpdateServicesDbFiles\SUSDB.mdf
The specified resource type cannot be found in the image file

SQL Server 2008 64-bit - Master Data Services troubleshoot database create Error

I am getting the following error when trying to create a new database in SQL server using MDS
        Microsoft.MasterDataServices.Configuration.ConfigurationException: Data is Null. This method or property cannot be called on Null values. ---> System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or
property cannot be called on Null values.
           at System.Data.SqlClient.SqlBuffer.get_String()
           at Microsoft.MasterDataServices.Configuration.DatabaseUtilities.GetDatabases(DatabaseServerInformation server)
           at Microsoft.MasterDataServices.Configuration.Commands.NewMasterDataServicesDatabase.InternalProcessRecord()
           at Microsoft.MasterDataServices.Configuration.Commands.ConfigurationCmdlet.ProcessRecord()
           at System.Management.Automation.CommandProcessor.ProcessRecord()
           --- End of inner exception stack trace ---
        at Microsoft.MasterDataServices.Configuration.InstanceManager.Execute(Command command)
           at Microsoft.MasterDataServices.Configuration.InstanceManager.CreateMasterDataServicesDatabase(DatabaseServerInformation serverInformation, DatabaseInformation databaseInformation)
           at Microsoft.MasterDataServices.Configuration.UI.MdsDatabase.CreateNewDatabase()
How can this error be resolved?
Thanks

Just double check the code and history.
The bug is fixed in 2011/08/23 and made into SQL 2012 RTM. So I assume you are using 2008 R2, which mainstream support is ended. I am not able to push a fix to that.
https://msdn.microsoft.com/en-us/library/ms178534.aspx
collation_name
sysname
Collation for the database. Acts as the default collation in the database.
NULL = Database is not online or AUTO_CLOSE is set to ON and the database is closed.
The only option would be fix the NULL collation databases.

Sql Server 2008 side effect after Windows 8.1 upgrade

Hi
After installing Windows 8.1 upgrade, I can't see a SQL SERVER instance.
I had Windows 8.0 Enterprise and SQL Server 2008 R2 installed and an instance named SVR12/SIMBD
All Windows 8.1 upgrade worked fine, no crashes no creepy messages
But now I can't to connect to the instance, nevertheless SQL Server Management Studio detects the instance SVR12/SIMBD
Looking at services runnings there are a Service named
SQL Server instead SQL Server (SIMDB)
as before the OS upgrade
Thanks in advance for any help, I'm stuck
Saludos David

What do you mean by "I can't see a SQL SERVER instance"?
Start by using SQL Server Configuration Manager to see what SQL Server instances are installed and if they are running. (If you don't have an icon for Configuration Manager, try C:\Windows\SysWOW64\mmc.exe /32 C:\windows\SysWOW64\SQLServerManager12.msc )
Or start services.msc and check the services that are installed and running.
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

Shouldn't I be able to upgrade to 2008 R2?
Current version:
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

I've the same problem as described above.
My Version is: 10.0.2531.0 SP1
Standard Edition (64-bit), on Windows Server 2003
Additionally, I have SQL Server 2005 Developer installed on the same machine.
I choosed SQL Server 2008 to upgrade to R2.
In the log I found:
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' found no upgrade features.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_engine_core_inst_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package 'sql_engine_core_inst_ctp6_Cpu64' with SkuValue=STANDARD ProductVersion=10.0.1600.22
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition STANDARD for feature package 'sql_engine_core_inst_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=STANDARD sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix found match in sku matrix.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_engine_core_inst_Cpu64' permits upgrade.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_is_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package 'IS2005_Cpu64' with SkuValue=DEVELOPER ProductVersion=9.3.4035.00
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 9.0 and edition DEVELOPER for feature package 'sql_is_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=9.0 sourceEdition=DEVELOPER sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_is_Cpu64' is blocking upgrade.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
2010-10-01 17:54:31 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
2010-10-01 17:54:31 Slp: Rule running on machine: <skipped>
2010-10-01 17:54:31 Slp: Rule evaluation done   : Failed
2010-10-01 17:54:31 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2008 R2 version and edition upgrade matrix in Books Online.
Thanks,
Patrik

Upgrade sql server 2008 to 2008R2 and apply Service pack 3

Similar Messages

Maybe you are looking for