Mixing
Installation of SQL Server LocalDB
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I want to install Microsoft SQL Server LocalDB on my system. Earlier I went for MySQL but it
was not suited for my local development needs as I did not require a full instance of the
server. But now I am unable to install it on my own. Let me tell you what all have I done: I
downloaded SQL Server Express Setup (about 5.1 MB). Then I opened it and chose
'Download Media' option and then chose LocalDB. Then it downloaded SqlLocalDB.msi
setup (about 45.9 MB). I ran the setup and installed it on my computer. I don't know what to do next. I have also tried to refer to various websites like sqlshack.com and
mssqltips.com and various questions of super user relating to my problem but I am unable
to understand what they say. They are telling something about configuring it and
creating instance which I am unable to understand as a newbie. Can someone explain me
the complete installation process of SQL Server LocalDB.
sql-server
asked 5 hours ago
Sam
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
1
down vote
favorite
I want to install Microsoft SQL Server LocalDB on my system. Earlier I went for MySQL but it
was not suited for my local development needs as I did not require a full instance of the
server. But now I am unable to install it on my own. Let me tell you what all have I done: I
downloaded SQL Server Express Setup (about 5.1 MB). Then I opened it and chose
'Download Media' option and then chose LocalDB. Then it downloaded SqlLocalDB.msi
setup (about 45.9 MB). I ran the setup and installed it on my computer. I don't know what to do next. I have also tried to refer to various websites like sqlshack.com and
mssqltips.com and various questions of super user relating to my problem but I am unable
to understand what they say. They are telling something about configuring it and
creating instance which I am unable to understand as a newbie. Can someone explain me
the complete installation process of SQL Server LocalDB.
sql-server
asked 5 hours ago
Sam
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Runsqllocaldb infofrom a command-prompt and add the output to your question.
– Dan Guzman
5 hours ago
@Dan you're right. My bad I assumed he went with sql express default installation. AMtwo beat me before I could add another post.
– Sam
3 hours ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I want to install Microsoft SQL Server LocalDB on my system. Earlier I went for MySQL but it
was not suited for my local development needs as I did not require a full instance of the
server. But now I am unable to install it on my own. Let me tell you what all have I done: I
downloaded SQL Server Express Setup (about 5.1 MB). Then I opened it and chose
'Download Media' option and then chose LocalDB. Then it downloaded SqlLocalDB.msi
setup (about 45.9 MB). I ran the setup and installed it on my computer. I don't know what to do next. I have also tried to refer to various websites like sqlshack.com and
mssqltips.com and various questions of super user relating to my problem but I am unable
to understand what they say. They are telling something about configuring it and
creating instance which I am unable to understand as a newbie. Can someone explain me
the complete installation process of SQL Server LocalDB.
sql-server
asked 5 hours ago
Sam
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I want to install Microsoft SQL Server LocalDB on my system. Earlier I went for MySQL but it
was not suited for my local development needs as I did not require a full instance of the
server. But now I am unable to install it on my own. Let me tell you what all have I done: I
downloaded SQL Server Express Setup (about 5.1 MB). Then I opened it and chose
'Download Media' option and then chose LocalDB. Then it downloaded SqlLocalDB.msi
setup (about 45.9 MB). I ran the setup and installed it on my computer. I don't know what to do next. I have also tried to refer to various websites like sqlshack.com and
mssqltips.com and various questions of super user relating to my problem but I am unable
to understand what they say. They are telling something about configuring it and
creating instance which I am unable to understand as a newbie. Can someone explain me
the complete installation process of SQL Server LocalDB.
sql-server
sql-server
asked 5 hours ago
Sam
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
Sam
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
Sam
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
Sam
61
asked 5 hours ago
Sam
61
61
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Runsqllocaldb infofrom a command-prompt and add the output to your question.
– Dan Guzman
5 hours ago
@Dan you're right. My bad I assumed he went with sql express default installation. AMtwo beat me before I could add another post.
– Sam
3 hours ago
add a comment |Â
1
Runsqllocaldb infofrom a command-prompt and add the output to your question.
– Dan Guzman
5 hours ago
@Dan you're right. My bad I assumed he went with sql express default installation. AMtwo beat me before I could add another post.
– Sam
3 hours ago
1
1
Run
sqllocaldb info from a command-prompt and add the output to your question.– Dan Guzman
5 hours ago
Run
sqllocaldb info from a command-prompt and add the output to your question.– Dan Guzman
5 hours ago
@Dan you're right. My bad I assumed he went with sql express default installation. AMtwo beat me before I could add another post.
– Sam
3 hours ago
@Dan you're right. My bad I assumed he went with sql express default installation. AMtwo beat me before I could add another post.
– Sam
3 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
LocalDB is a quirky flavor of SQL Server. In most cases, unless there's specific functionality in LocalDB that you need, I'd suggest running the "regular" Express Edition--as you can avoid quirks like the one you're running into. Additional details of differences are included in this article.
LocalDB has an "automatic" instance that is tied to current user. To connect to that instance, you would use a connection string like "Server=(localdb)MSSQLLocalDB;Integrated Security=true".
You can also create an explicitly named instance using the SQLLocalDB.exe command line utility. Depending on your installed version, the path may vary (in this example, 130 is SQL Server 2016, but you would use 140 for 2017, etc):
C:> cd "C:Program FilesMicrosoft SQL Server130ToolsBinn"
C:> SqlLocalDB.exe create MyLocalDB
C:> SqlLocalDB.exe start MyLocalDB
The SQLLocalDB info command can be used at any time to determine the state of an instance, whether it is running or not:
C:> SqlLocalDB.exe info MyLocalDB
Additional info on creating & connecting to a LocalDB instance can be found on docs.microsoft.com.
answered 4 hours ago
AMtwo
4,312824
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a singlenet start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).
– Aaron Bertrand♦
14 mins ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
LocalDB is a quirky flavor of SQL Server. In most cases, unless there's specific functionality in LocalDB that you need, I'd suggest running the "regular" Express Edition--as you can avoid quirks like the one you're running into. Additional details of differences are included in this article.
LocalDB has an "automatic" instance that is tied to current user. To connect to that instance, you would use a connection string like "Server=(localdb)MSSQLLocalDB;Integrated Security=true".
You can also create an explicitly named instance using the SQLLocalDB.exe command line utility. Depending on your installed version, the path may vary (in this example, 130 is SQL Server 2016, but you would use 140 for 2017, etc):
C:> cd "C:Program FilesMicrosoft SQL Server130ToolsBinn"
C:> SqlLocalDB.exe create MyLocalDB
C:> SqlLocalDB.exe start MyLocalDB
The SQLLocalDB info command can be used at any time to determine the state of an instance, whether it is running or not:
C:> SqlLocalDB.exe info MyLocalDB
Additional info on creating & connecting to a LocalDB instance can be found on docs.microsoft.com.
answered 4 hours ago
AMtwo
4,312824
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a singlenet start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).
– Aaron Bertrand♦
14 mins ago
add a comment |Â
up vote
2
down vote
LocalDB is a quirky flavor of SQL Server. In most cases, unless there's specific functionality in LocalDB that you need, I'd suggest running the "regular" Express Edition--as you can avoid quirks like the one you're running into. Additional details of differences are included in this article.
LocalDB has an "automatic" instance that is tied to current user. To connect to that instance, you would use a connection string like "Server=(localdb)MSSQLLocalDB;Integrated Security=true".
You can also create an explicitly named instance using the SQLLocalDB.exe command line utility. Depending on your installed version, the path may vary (in this example, 130 is SQL Server 2016, but you would use 140 for 2017, etc):
C:> cd "C:Program FilesMicrosoft SQL Server130ToolsBinn"
C:> SqlLocalDB.exe create MyLocalDB
C:> SqlLocalDB.exe start MyLocalDB
The SQLLocalDB info command can be used at any time to determine the state of an instance, whether it is running or not:
C:> SqlLocalDB.exe info MyLocalDB
Additional info on creating & connecting to a LocalDB instance can be found on docs.microsoft.com.
answered 4 hours ago
AMtwo
4,312824
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a singlenet start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).
– Aaron Bertrand♦
14 mins ago
add a comment |Â
up vote
2
down vote
up vote
2
down vote
LocalDB is a quirky flavor of SQL Server. In most cases, unless there's specific functionality in LocalDB that you need, I'd suggest running the "regular" Express Edition--as you can avoid quirks like the one you're running into. Additional details of differences are included in this article.
LocalDB has an "automatic" instance that is tied to current user. To connect to that instance, you would use a connection string like "Server=(localdb)MSSQLLocalDB;Integrated Security=true".
You can also create an explicitly named instance using the SQLLocalDB.exe command line utility. Depending on your installed version, the path may vary (in this example, 130 is SQL Server 2016, but you would use 140 for 2017, etc):
C:> cd "C:Program FilesMicrosoft SQL Server130ToolsBinn"
C:> SqlLocalDB.exe create MyLocalDB
C:> SqlLocalDB.exe start MyLocalDB
The SQLLocalDB info command can be used at any time to determine the state of an instance, whether it is running or not:
C:> SqlLocalDB.exe info MyLocalDB
Additional info on creating & connecting to a LocalDB instance can be found on docs.microsoft.com.
answered 4 hours ago
AMtwo
4,312824
LocalDB is a quirky flavor of SQL Server. In most cases, unless there's specific functionality in LocalDB that you need, I'd suggest running the "regular" Express Edition--as you can avoid quirks like the one you're running into. Additional details of differences are included in this article.
LocalDB has an "automatic" instance that is tied to current user. To connect to that instance, you would use a connection string like "Server=(localdb)MSSQLLocalDB;Integrated Security=true".
You can also create an explicitly named instance using the SQLLocalDB.exe command line utility. Depending on your installed version, the path may vary (in this example, 130 is SQL Server 2016, but you would use 140 for 2017, etc):
C:> cd "C:Program FilesMicrosoft SQL Server130ToolsBinn"
C:> SqlLocalDB.exe create MyLocalDB
C:> SqlLocalDB.exe start MyLocalDB
The SQLLocalDB info command can be used at any time to determine the state of an instance, whether it is running or not:
C:> SqlLocalDB.exe info MyLocalDB
Additional info on creating & connecting to a LocalDB instance can be found on docs.microsoft.com.
answered 4 hours ago
AMtwo
4,312824
edited 3 hours ago
answered 4 hours ago
AMtwo
4,312824
answered 4 hours ago
AMtwo
4,312824
answered 4 hours ago
AMtwo
4,312824
4,312824
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a singlenet start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).
– Aaron Bertrand♦
14 mins ago
add a comment |Â
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a singlenet start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).
– Aaron Bertrand♦
14 mins ago
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
One thing I would like to point out is that I have asked this question for SQL Server 2017. So make sure that your answers correspond to the specified version.
– Sam
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
@Sam You don't mention any version in your question--if you are concerned about a specific version, be sure to mention it in your question. I've updated the answer with additional details for 2017, as well
– AMtwo
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I could have used the regular Express Edition software. But since I want my server ready for small scale local development, I have opted for LocalDB. I just want it to practice my database concepts at the school level. So I do not want to spend excessive resources by runnig my server at full instances.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
I will also attach the output of running the command "SqlLocalDB info" soon.
– Sam
3 hours ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a single
net start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).– Aaron Bertrand♦
14 mins ago
@sam LocalDB might not be the best solution to your problem. If your main concern is about resources, and can’t wrap your head around LocalDB, just install a proper Express instance and don’t set it to auto start. You can start it up when you need it, much simpler command line entries (a single
net start...), stop it when you don’t (net stop), and your databases persist between sessions. I’d also suggest not getting snippy with people because they didn’t read your mind which version you’re using - and first check whether you can’t adapt the advice to your version (true here).– Aaron Bertrand♦
14 mins ago
add a comment |Â
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f221745%2finstallation-of-sql-server-localdb%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Run
sqllocaldb infofrom a command-prompt and add the output to your question.– Dan Guzman
5 hours ago
@Dan you're right. My bad I assumed he went with sql express default installation. AMtwo beat me before I could add another post.
– Sam
3 hours ago