Post reply

avoid install localdb through SSDT installer

  • August 16, 2016 at 5:11 pm

    #312506

    I am trying to download and install SQL 2016 Data tools on a development server which we have already installed SQL server 2016 database engine.

    The SSDT download page is here.

    https://msdn.microsoft.com/en-us/mt186501

    I am not sure how to do the option of Set up an Administrative Install Point (optional)

    I downloaded on a network share, by remote log in to the server, open the UNC path, and double click the setup file, it gives an error.

    Then I tried the Download SSDT as an ISO image file.

    After mount the ISO, it started to install, and it installs a localdb first, which I don't want to, since We already have a full version of database engine .

    Is there a way to choose to not install localDB?

    Thanks,

  • August 16, 2016 at 5:23 pm

    #1895816

    sqlfriends (8/16/2016)

    I am trying to download and install SQL 2016 Data tools on a development server which we have already installed SQL server 2016 database engine.

    The SSDT download page is here.

    https://msdn.microsoft.com/en-us/mt186501

    I am not sure how to do the option of Set up an Administrative Install Point (optional)

    I downloaded on a network share, by remote log in to the server, open the UNC path, and double click the setup file, it gives an error.

    Then I tried the Download SSDT as an ISO image file.

    After mount the ISO, it started to install, and it installs a localdb first, which I don't want to, since We already have a full version of database engine .

    Is there a way to choose to not install localDB?

    Thanks,

    As far as I know, there's no way to avoid the localDB installation.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • September 8, 2016 at 11:46 am

    #1899897

    Thank you.

    Since we have already a standard edition instance installed, could we somehow do not let the localdb shown at SSDT tool.

  • September 8, 2016 at 12:13 pm

    #1899905

    Isn't localDB pretty integral to how SSDT works?

  • September 8, 2016 at 12:31 pm

    #1899907

    There is no localdb in BI tools in previous SQL version, so I don't think it is necessary if we have a full version of SQL installed.

  • September 8, 2016 at 12:57 pm

    #1899910

    SSDT used to be just the SQL connection & deployment tooling - source control, dacpacs and the like.

    Now they've integrated the BI tooling for AS/IS/RS (used to be called SSDT-BI) with SSDT in 2016.

    So yeah for BI tooling you're right, localDB probably isn't required. But you don't get the choice now 🙂

    I will say that LocalDB is blooming fantastic when you're working with source control/local development of SQL objects.

    Whether or there's a full instance of SQL installed locally too is irrelevant, it's not what LocalDB is there for.

  • September 8, 2016 at 1:11 pm

    #1899913

    sqlfriends (9/8/2016)

    There is no localdb in BI tools in previous SQL version, so I don't think it is necessary if we have a full version of SQL installed.

    This is an SSDT thing – it's as much related to Visual Studio as it is to 'SQL versions'. And I am pretty sure that SSDT for VS2013 and VS2012 have their own little SQL instances too.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • September 8, 2016 at 2:50 pm

    #1899925

    Thank you guys.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply