Skip to main content

Make your SQL Server Express 2012 available from the outside

By default when you install a SQL Server Express, it is configured to be only accessible from the local machine.

Here are the steps required to make your SQL Server Express database available from the outside:

  • Run SQL Server Configuration Manager.
  • Go to SQL Server Network Configuration > Protocols for SQLEXPRESS.
  • Enable TCP/IP.
  • In the SQL Server Configuration Manager also verify that SQL Server Browser is running.

Now before you continue you have to know if you want to use a dynamic port range for SQLExpress or not. If you want to use a dynamic port range, you can immediately jump to the firewall configuration, otherwise you’ll have to do some extra configuration first:

  • Right-click on TCP/IP and select Properties.
  • Scroll down to IPAll.
  • Make the TCP Dynamic Ports empty
  • Set the TCP Port value to 1433.

Last step is to configure the firewall and add an exception that allows SQL Server traffic:

  • If you are using the dynamic ports, choose Add a program on the Exceptions tab of the Windows Firewall item.
  • Browse to the location of the instance of SQL Server that you want to allow through the firewall, for example C:\Program Files\Microsoft SQL Server\MSSQL11.<instance_name>\MSSQL\Binn, select sqlservr.exe, and then click Open.
  • If you are using a specific port, add a new inbound rule for TCP traffic on port 1433.

More information here: http://technet.microsoft.com/en-us/library/cc646023.aspx

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more