Can I Use My Computer Name Instead of (localdb) in My Database Server?

[Medicol]

My computer name is "Computer" and my domain is MyDomain.com
My account to sign in is MyDomain\MyAccount.
My database instance is "(localdb)\MyInstance" - this is also my database server.
I don't want to use string "(localdb)", can I use my computer name for it such that my database server becomes
"Computer\MyInstance", for example ?

 

[Greg Bernhardt]

What OS and what database server are you using?

 

[Medicol]

Windows and MS SQL Server 2012 Express version

 

[Filip Larsen]

If you are referring to the hostname in connection strings, then you can use "localhost" [1] there instead of your full computer or domain name if you want to connect to a local database server.

[1] http://en.wikipedia.org/wiki/Localhost

 

[LudusRex]

Yes, it is possible to use your computer name instead of (localdb) in your database server. In this case, your database server would be "Computer\MyInstance". However, there are a few considerations to keep in mind before making this change.

Firstly, using your computer name in place of (localdb) may cause issues if you ever need to move your database to a different server. The (localdb) string is a placeholder that allows your database to be easily moved to a different server without having to change the connection string. If you use your computer name, you will need to update the connection string every time you move your database.

Additionally, using your computer name may also cause issues if you have multiple instances of (localdb) on your computer. In this case, it would be difficult to differentiate between the different instances without using the (localdb) string.

It is also important to consider security implications when using your computer name in the connection string. If your computer is accessible to others on the network, using your computer name may make it easier for unauthorized users to access your database.

In summary, while it is possible to use your computer name instead of (localdb) in your database server, it is important to carefully consider the potential implications before making this change.