Sql-server – Connect to LocalDB with new ODBC Driver for SQL Server

localdbodbcsql server

UPDATE: Thanks to Dan Guzman, the problem has been solved.
I'd made a mistake and used the old legacy Driver={SQL Server}; assuming it is the new driver. Instead, I should have used Driver={ODBC Driver 11 for SQL Server} which is the actual new ODBC driver.
I can connect to (Localdb)\v11.0 with the new driver.

TL;TR: Why I can not connect to (Localdb)\v11.0 using the new Driver={SQL Server}; in connection string, but I can connet if I switch the driver to the old Driver={SQL Server Native Client 11.0}; ?

The remaining connection string parameters I use are (if used in C++ code, backslash escaped):

Server=(localdb)\v11.0;Integrated Security=True;

I'm trying to access SQL Server via ODBC and calling SQLDriverConnect with DSN-less connection string. If I switch the driver to SQL Server Native Client 11.0, then I suddenly can connect.

I have also tested generating FILEDSN using %systemdrive%\Windows\System32\odbcad32.exe and I observed exactly the same issue.

The only local database I can connect with the new Driver={SQL Server} is Server=DEVBOX\SQLEXPRESS (if used in C++ code, backslash escaped, of course).

I couldn't find any confirmation that the new ODBC Driver for SQL Server does not support LocalDB.

It is only indicated in the FAQ of ODBC Driver for SQL Server for Linux

Which features of SQL Server 2012 does this version of the driver
support?
The ODBC driver on Linux supports all server features in SQL Server 2012 except LocalDB.

How can I connect to LocalDB with the new ODBC driver on Windows?

UPDATE:
I'm using Windows 10 Pro + VS2015.
I can connect to both, (localdb)\v11.0 and DEVBOX\SQLEXPRESS with SQL Server Management Studio 2016 (CTP).
(The same question has been asked on MSDN Forums, here.)

Best Answer

The ODBC driver SQL Server is the legacy SQL Server ODBC driver that ships with Windows for backwards compatibility. The latest SQL Server ODBC driver is ODBC Driver 11 for SQL Server. I believe this ODBC driver is installed with SQL Server 2016 CTP. The released version is available as a separate download.

Syntax:

ALTER TABLE {TABLENAME} 
ADD {COLUMNNAME} {TYPE} {NULL|NOT NULL} 
CONSTRAINT {CONSTRAINT_NAME} DEFAULT {DEFAULT_VALUE}
WITH VALUES

Example:

ALTER TABLE SomeTable
        ADD SomeCol Bit NULL --Or NOT NULL.
 CONSTRAINT D_SomeTable_SomeCol --When Omitted a Default-Constraint Name is autogenerated.
    DEFAULT (0)--Optional Default-Constraint.
WITH VALUES --Add if Column is Nullable and you want the Default Value for Existing Records.

Notes:

Optional Constraint Name:
If you leave out CONSTRAINT D_SomeTable_SomeCol then SQL Server will autogenerate
a Default-Contraint with a funny Name like: DF__SomeTa__SomeC__4FB7FEF6

Optional With-Values Statement:
The WITH VALUES is only needed when your Column is Nullable
and you want the Default Value used for Existing Records.
If your Column is NOT NULL, then it will automatically use the Default Value
for all Existing Records, whether you specify WITH VALUES or not.

How Inserts work with a Default-Constraint:
If you insert a Record into SomeTable and do not Specify SomeCol's value, then it will Default to 0.
If you insert a Record and Specify SomeCol's value as NULL (and your column allows nulls),
then the Default-Constraint will not be used and NULL will be inserted as the Value.

Notes were based on everyone's great feedback below.
Special Thanks to:
@Yatrix, @WalterStabosz, @YahooSerious, and @StackMan for their Comments.

Sql – How to return only the Date from a SQL Server DateTime datatype

SELECT DATEADD(dd, 0, DATEDIFF(dd, 0, @your_date))

for example

SELECT DATEADD(dd, 0, DATEDIFF(dd, 0, GETDATE()))

gives me

2008-09-22 00:00:00.000

Pros:

No varchar<->datetime conversions required
No need to think about locale

Best Answer

Related Solutions

Sql – Add a column with a default value to an existing table in SQL Server

Syntax:

Example:

Notes:

Sql – How to return only the Date from a SQL Server DateTime datatype

Related Topic