Using Web Deploy 3.5 from Visual Studio 2012 including SQL scripts? Make sure you have these installed on the server:
Use Web Platform Installer to install:
If not you’ll get dac provider errors when deploying:
In SQL Management Studio on the server, right click the server instance [machinename]\SQLEXPRESS and click Properties. In the left pane, click Connections, and check Allow Remote Connections to this server.Create Firewall Rules
Now we’ll need to repeat the procedure to add an entry for port 1634 as well.
Now we need to remove the dynamic ports and tell SQL Server that you want to use port 1633 to connect to the server.
You need to restart the SQL Server Service for the changes to take effect.Restart SQL Server Service
To restart the SQL server…
Also, while you are here, make sure that the SQL Server Browser service is started.
Verify Firewall Settings
Open a Command Prompt. Run the command:
Ports 1633 and 1634 should both be open and listening.
You should now be able to connect to your SQL Server remotely.
Notes: SQL Server Browser was introduced in SQL Server 2005 to replace SSRP which was introduced in SQL Server 2000, which was introduced to point SQL clients to the correct instance of SQL Server (SS) on a computer. Before that, you could only have one instance of SS on a server. Since you can setup it up so that SS gets a dynamic port every time it starts up when TCP/IP is enabled for remote connections, SQL Browser is used to help the connecting clients get the port number for the named instance the client is making the request for. The way it works is the client would send a UDP message to SS Browser, which listens on port 1434 by default, and it would look at the server’s registry and instances of SS and respond to the client with the correct port for the connection, then the client can create the connection using that port.
Since we only have one instance of SS in our machine and we issued a static port for our machine, we don’t need the ‘routing’ mechanism that SS Browser was created for, so we can just stop that service in the server’s Services and disable the firewall rule for SS Browser, which is one less port that’s open on your server. When you connect to the server from SQL Management Studio, make sure you use the port number when you log in, so the Server name on the log in would be “xx.xx.xx.xx,1633”. With SS Browser Service stopped and the Firewall Inbound Rule disabled, you should still be able to connect.
You should also rename or disable the ‘sa’ account:
ALTER LOGIN sa DISABLE; ALTER LOGIN sa WITH NAME = [myLoginName];
Create something simple with it
Learn the breadth of the technology to understand what there is to know about it.
Determine the most important high level topics to learn and only go into details when necessary, you can always fill in the details later