[EN] New instalation versus existing feature: SQL Connect in VS2012

sql_connect_270x220My environment is not very complicated: just windows platform, some sql server instances, recording stuff, bloggers kit, visual studio installation and some third party (vendors) tools. One of them, installed ‘by default’ in my Visual Studio 2012 instance is SQL Connect by RedGate {LINK}.  Ingeniously simple database development in Visual Studio.  Connected, source-controlled database development in Visual Studio:

  • Develop databases in Visual Studio alongside application code
  • Query databases and execute stored procedures directly from Visual Studio
  • Track and share changes using your source control system

Very useful tool, especially when You think abou controlling your code, and data. I had installed, and fully updated Visual Studio 2012 environment, and tried install my RedGate’s SQL Developer Bundle (more about this ingeniously awesome pack in next posts). And I got an error:


Pict. 1 | in the process of installing full package, received error from SQL Connect 1.1 (MSI Error 1603)

On Microsoft Support page we can find information about cause of this error – KB834484:

You may receive this error message if any one of the following conditions is true:

  • The folder that you are trying to install the Windows Installer package to is encrypted.
  • The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
  • The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.

Because nothing of that is my cause I decided to skip this software in installation process, and installing all others software.


Pict.2 | result is green for me.

Next I back to problematic package, using both paths with installation: default by vendor (c:\… I never use partition C for any of files if I really needn’t it), and default by me (somewhere else).


Pict.3 | installation folder by default for this installation…


Pict.4 | cannot help me. Still got an error.

I checked my Visual Studio 2012 installation and I discovered that SQL Connect 1.1. has been installed. Hmmm.. maybe conflict? I de-istalled this feature from my Visual Studio {Menu/Tools/Extentions and Updates}. And run RedGate setup again.


Pict.5 | Got You. Finally green light.


It is a little strange for me. just installer crashed – better solution should be show me my mistake, like: “You have installed version. please delete other versions before you install this software”. Well, maybe Redgater’s could repair this installer, because this dependiences are important.

[EN] How to DO IT? Installation SQL Server Service Pack on more than one instance

In previous post I wrote about new stuff: Service Pack 2 Customer Technology Preview for Microsoft SQL Server 2008 R2. In this one I’ll show what’s happen when we install this (and any other) service pack update on more than one instance. In this case I’ve two SQL Server 2008 R2 instances: one in Enterprise Edition and one in Express Edition with Advanced Services (both with SP1 installed). Generally We can use different Service Packs (one for Enterprise and one for Express) but it is not necessary. OK before we start we should download right file – in this case SQLServer2008R2SP2-KB2630455-x64-ENU.exe (349.8 MB) from THIS place. After, we can start:


Pic.01 | First step as always is for checking compability and possibility for success installation. Eight rules passed, one skipped (because it is not a cluster environment).


Pic.02 | Licence Agreemend SHOULD be read and MUST be accepted.


Pic.03 | First instance – JOTARO on SQL Server Enterprise Edition (with SP1)


Pic.04 | Second instance – MIFUNE on SQL Server Express with AdvServ. As we see installator found third KEYKO and fourth SQLEXPRESS instances. Both are under SQL Server 2008 Express and this service pack is not appropriate for updating process.


Pic.05 | We should check Files in Use for our security, we should know which services are collerated with those instances BEFORE we start update.


Pic.06 | And we have collerated service.


Pic.07 | When we are ready to update we can look last time for summary before we going further – for SQL Server Express Edition (I apologize my readers, I missed screen for Enterprise Edition)…


Pic.08 | and for Shared Features of course.


Pic.09 | Installator start update for first instance – SQL Server Enterprise Edition…


Pic.10 | and finishing them. next we must waif few minutes (on my laptop about five) before next phase will start.


Pic.11 | And the second phase is starting. If we have more instances we will have more phases.


Pic.12 | At the end we have GREEN LIGHT and link for summary log.


Pic.13 | The last – unfortunatelly we must restart computer. Another one reason for announce maintenance tasks for company.

*** **** ***

After that is really good practice to review summary log. Is not very big, and is not hard to understand, but give us a lot of necessary information: what happened with my server. Let see it.

By default all reports are stored in this folder (and we shouldn’t change it): C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120518_235654\SystemConfigurationCheck_Report.htm

Inside this file we will find informations below:

Overall summary:
  Final result:        Passed but reboot required, see logs for details
  Exit code (Decimal): 3010
  Exit message:        Passed but reboot required, see logs for details
  Start time:          2012-05-18 23:57:06
  End time:            2012-05-19 00:29:57
  Requested action:    Patch

Instance JOTARO overall summary: {FIRST INSTANCE}
  Final result:        Passed but reboot required, see logs for details
  Exit code (Decimal): 3010
  Exit message:        Passed but reboot required, see logs for details
  Start time:          2012-05-19 00:11:19
  End time:            2012-05-19 00:24:42
  Requested action:    Patch

Instance MIFUNE overall summary: {SECOND INSTANCE}
  Final result:        Passed
  Exit code (Decimal): 0
  Exit message:        Passed
  Start time:          2012-05-19 00:24:58
  End time:            2012-05-19 00:29:52
  Requested action:    Patch

Machine Properties:
  Machine name:        WRON023
  Machine processor count:       2
  OS version:          Future Windows Version {WINDOWS 8 CONSUMER PREVIEW}
  OS service pack:             
  OS region:           Ísland
  OS language:         English (United States)
  OS architecture:     x64
  Process architecture:64 Bit
  OS clustered:        No

Product features discovered:
{details in text normally but the graphical looks better, see below}
Product, Instance, Instance ID, Feature, Language, Edition, Version, Clustered

Package properties:
  Description:         SQL Server Database Services 2008 R2
  ProductName:         SQL2008
  Type:                RTM
  Version:             10
  SPLevel:             2
  KBArticle:           KB2630455
  PatchType:           SP
  AssociatedHotfixBuild:         0
  Platform:            x64
  PatchLevel:          10.52.3720.0
  ProductVersion:      10.50.1600.1
  GDRReservedRange:    10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
  PackageName:         SQLServer2008R2-KB2630455-x64.exe
  Installation location:         e:\86645666867d6b8cf018fff81c2985\x64\setup\

Updated product edition:
  Instance             Edition            
  JOTARO               ENTERPRISE         
  MIFUNE               EXPRESS_ADVANCED   

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

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:    C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120518_235654\SystemConfigurationCheck_Report.htm


Information from file under part: ‘Product features discovered ‘ looks better when we turn SQL Server Setup Discovery Report. Result is much better in table view: