The following are instructions for setting up a connection to an Active Directory (AD) Domain secured SQL Server using either SQL Server Management Studio or Visual Studio. This is especially applicable when not using a domain attached PC.
If you have started to create a good collection of you own SQL Templates and snippets, then you may want to copy or share them from PC to PC or from user account to user account.
You will find your personal templates here Continue reading “Location of your SQL Templates and how to take them with you”
If you have been using Azure SQL Servers and databases, you will already be aware that you need to configure the server level firewall. You may not know that you can also set firewall rules at database level too.
However this cannot be done through the Azure Portal. However both server and database level firewall rules can be easily managed using SQL.
-- ========== SERVER LEVEL FIREWALL (master database connection) -- List firewall rules SELECT * FROM sys.firewall_rules ORDER BY name; -- ADD Server firewall rule EXECUTE sp_set_firewall_rule @name = N'MyFirewallRule', @start_ip_address = '192.168.1.1', @end_ip_address = '192.168.1.10' -- DELETE Server firewall rule EXECUTE sp_delete_firewall_rule @name = N'MyFirewallRule'
-- ========== DATABASE LEVEL FIREWALL (specific database connection) -- List firewall rules SELECT * FROM sys.database_firewall_rules ORDER BY name; -- ADD Database firewall rule EXEC sp_set_database_firewall_rule @name = N'MyDBFirewallRule', @start_ip_address = '192.168.1.11', @end_ip_address = '192.168.1.11' -- DELETE Server firewall rule EXEC sp_delete_database_firewall_rule @name = N'MyDBFirewallRule'
Got a new high resolution latop with scaling and struggling to use SSMS. Here’s the fix
If you are looking for a quick way to improve your SQL Azure performance then you can check to see if SQL Azure has determined if any useful indexes are missing.
In SQL Server Management Studio (SSMS) run the following against your database
select * from sys.dm_db_missing_index_details
This will output something like (I have obscured some sensitive names)
For example, the above suggested I made the following indexes on AccessNoXRefs table.
For more information see http://msdn.microsoft.com/library/ms345434.aspx and http://msdn.microsoft.com/en-US/library/dn133166.aspx
After installing SQL Server 2008 R2 on a Windows 2008 server you will need to configure the firewall (if it’s turned on!) to allow access to the SQL server. Here is the simple method using the interface and assumes the following:
- The SQL Instance is the default (first installed)
- The ports have not been manually configured
- Nothing too exotic like database mirroring is required.
- Open the Firewall either from the Control panel
or by running WF.msc
- There are 3 default firewall profiles. One or more can be active depending on what and how you have configured your NICs. You will need to ensure you are editing the correct profile. Here you can see that mine is on a domain, so my Domain Profile is Active.
- Select ‘Inbound Rules’ in the left hand pane.
- Click on ‘New Rule…’ in the right actions pane.
- select Port Rule Type and click Next>
- Set TCP and Specific local Ports to 1433 and click Next>
- Leave the default of ‘Allow the connection’ and click Next>
- If you don’t ever want SQL to be directly accessible on a Public network (assuming you are going to ever connect your SQL server directly to the internet for some reason!!) then un-check the ‘Public’. Otherwise just click Next>
- Name it SQLPort and give it a description and click Finish.
That will enable inbound connections to your SQL Server. If you are also enabling SQL Browser Service then you will need to add UDP Port 1434 too another inbound rule.
If you have more than one instance of SQL then you will need to set the port and create rules for them.
For full details on ports and setting it up go to http://msdn.microsoft.com/en-us/library/cc646023(v=SQL.105).aspx