Home Dashboard Directory Help
Search

Include SQL Server Native Client in LocalDB standalone setup by GLuebben


Status: 

Closed
 as By Design Help for as By Design


2
0
Sign in
to vote
Type: Suggestion
ID: 709095
Opened: 11/28/2011 1:52:29 AM
Access Restriction: Public
0
Workaround(s)
view

Description

SQL Server 2012 LocalDB is a really cool alternative to SQL Server compact when you need a small little database that just runs fine on a workstation.
Please make the standalone setup of LocalDB as complete as possible. To my mind it should include at least:
- SQl Server LocalDB runtime (of course)
- SQL Server Native Client
- A simple command line client like OSQL
Details
Sign in to post a comment.
Posted by David Mullin on 7/26/2012 at 11:24 AM
I'm confused by this answer. I have installed the LocalDb MSI on a clean machine, and have a simple .Net Application that attempts to use a SqlConnection with the Connection String Data Source=(localdb)\\v11.0;Integrated Security=true, and I fail to connect. It appears that I need to install the SNAC in order to make this work.

If that's true, then of what value is the LocalDb installer, in and of itself? If I just install LocalDb, what can I possibly accomplish with that?

Or, am I missing something?
Posted by Microsoft on 4/20/2012 at 9:10 AM
Hi,
Thanks for sharing your feedback on this. As Kryzysztof explained earlier, we have decided to keep the LocalDB footprint/dependencies small to simplify the installation/configuration experience. We will continue to watch this closely as new requirements arise.

Srini Acharya
SQL Server
Posted by Microsoft on 4/13/2012 at 10:58 AM
Hi,
Thanks for sharing your feedback on this. As Kryzysztof explained earlier, we have decided to keep the LocalDB footprint/dependencies small to simplify the installation/configuration experience. We will continue to watch this closely as new requirements arise.

Srini Acharya
SQL Server
Posted by GLuebben on 12/6/2011 at 1:38 AM
Hello Krzysztof,

thank you very much for your feedback and your explanation!

Kind regards

Gerold Luebben
Posted by Microsoft on 12/5/2011 at 3:36 PM
Hello,

Thank you for sharing your feedback with us.

We did consider including SQLCMD and SNAC in LocalDB installer, but after long debate decided to ship LocalDB without it. The major factor was our desire to keep LocalDB installer small and simple. Installing shared components always comes at the risk of adding a reboot as well, which we are trying to avoid at all cost. Both SNAC and Command Line Utilities are not needed by managed applications and can be installed separately with their own simple MSIs (we slimmed both down significantly in SQL Server 2012 RC0). As a result we felt that the right thing is to keep SNAC and Command Line Utilities separate from LocalDB.

That being said we are always listening to your feedback. I am moving this bug to future releases for reconsideration.

Thanks,
Krzysztof Kozielczyk, Program Manager for SQL Server Express


Sign in to post a workaround.