Virtual Conference – 2 More Days to Save
There are only 2 days left at the current early bird rate – if you want to save, NOW is the time to check out the information about the conference. We’re pulling together information about SQL Server administration, how-to information, tips, tricks, Business Intelligence, SharePoint and more. More than 75 sessions, more than 20 speakers… all direct to your computer. Here’s a VIP code to save an additional $20: VIP0302NL – The links below will automagically apply it for you.
[Get More Information Here] or [Register Now to Save]
SharePoint Recovery Options
Did you know that you can effectively remove backup execution failures while at the same time cutting backup times? It’s true. AvePoint’s DocAve solution does just that and you can learn more about how they helped the U.S. Social Security Administration do exactly this. If you are working with SharePoint, you’ll definitely want to take a look. Get more information here in the case study (direct link).
Server Name Considerations – DNS and More
I hadn’t planned on more naming items – but this is great feedback from a more "holistic" sense and I wanted to pass along this note from Johan.
"I know this is a pure Database Admins forum but when you start discussing server names, you are also referencing one of my other networking tasks. As I am working for a globally operating company with limited ICT staff, I am responsible for Databases, Active Directory, Server installations and Business Continuity Management. The server name standard I introduced uses ISO country code (Char 2), City Code (Char 3), Virtualization (‘V’ or not present), primary function (Char 3) and a number (Char 2). This results in NLEHVSQL03 for the third physical SQL server based in The Netherlands and the city of Eindhoven. This way the location of a server and its primary function is always known by its name.
The thing you are missing in your fine newsletter is the fact that your example server "GGSH389FKSJJS" can have a DNS Alias (technically called CNAME) that also describes another function. So your file server can have the Windows Active Directory and DNS name "GGSH389FKSJJS" and another DNS alias (CNAME) "FSBookKeeping" for the users.
This has multiple advantages:
– When the server fails, you can bring a new one online called "JXZ596JVSUT", point the DNS alias "FSBookKeeping" to this server and no scripts, unc paths and documents have to be changed as the users use \FSBookKeepingfileshare
– When your location has a Business Continuity crisis. Only DNS aliases have to be pointed to the servers in the backup server room. This also limits the scripting and configuration tasks during a crisis
– Your server can have multiple functions to the user under different Aliases.
– DNS entries can be updated with a script so they can be prepared for the case of an emergency. (see http://www.vansoest.it/v1/uk/default.asp?file=Hotlist.whc and click “Domain Name Server (DNS) Tips” for more information about the DNSCMD command line command)
There is a fileserver security option “DisableStrictNameChecking” that must be set before a fileserver (SMB) can be accessed by a DNS alias (CNAME). You can also find more information here: http://www.vansoest.it/v1/uk/default.asp?file=Hotlist.whc and click “Domain Name Server (DNS) Tips” I hope this gives your readers a lot more possibilities for efficiently naming their servers."
SelectViews Show is Live
Eric Harlan on the show today – SharePoint tips and experiences, SQL Server in the cloud, utilities and more. Also, relational databass a thing of the past? (Nope), upcoming events and the SQL Server tip of the day.
[Watch the Show]
Featured Script
admin db – Heavy Duty LiteSpeed Log Shipping
Please see my sswug.org articles, "Heavy Duty LiteSpeed Log Shipping" (parts 1, 2 and 3) for a full descripition of the confi… (read more)