Keyboard not found, Press F1 to Continue Random musings from a techhead.

13Dec/110

Changes in SQL Server 2012 Licensing

The coming launch of SQL Server 2012 is bringing many new features and improvements to the product, but along with those improvements comes some interesting changes to the way SQL Server is licensed.

The most notable change is a move away from the traditional per socket licensing to a per core license model. For example: Standard Edition has moved from supporting a maximum of 4 CPUs to a maximum of 16 cores. With newer server processors available with 10+ cores, this move could seriously impact your licensing costs as you scale upward.

Next up is the introduction of the Business Intelligence Edition. This edition will feature many of the newer BI solutions Microsoft has been working on including PowerView, PowerPivot, Master Data Services, and the Semantic Model. While the traditional Integration Services and Reporting Services are still included in the Standard Edition, all of the newer "Self Service" BI tools will require an upsell to the BI Edition.

Lastly, Data Center Edition has be discontinued, and all of its features will be rolled into the Enterprise Edition. Along with this change, Microsoft has discontinued the Server+CAL licensing for Enterprise edition and licensing by cores will now be the only option.

For more details on the matrix of the new Edition's features, check out Microsoft's Edition page.

Filed under: IT, SQL No Comments
13Dec/110

Step by Step: How to configure SmartUPS w/ Management Card and APCUPSD

APCUPSD is an Open Source and free alternative to the server shutdown software sold by APC. This step by step guide will help you configure the APCUPSD software for use with an APC SmartUPS (Ethernet based models) on a Microsoft Hyper-V server (or Windows Server Core).

  1. First you will need to configure your APC UPS Management Card if you have not done so already. This can be done through the Web admin interface with Ethernet enabled Management Cards. Refer to the instructions that came with the card to find the default IP address settings in order to connect to the Web Interface for the first time.
  2. Once you have the Management Card configured correctly and connected to an appropriate network that your server will have access to, make sure to add the IP address of your server you are configuring to the Clients list in the Management Card's Web Interface.
  3. Next will be to configure the PowerChute timers in the Web Interface. Depending on the current load factor and the capacity of your UPS the settings you chose may vary greatly. You can vary the Shutdown Delay and Return Delay to account for short power losses if they are common in your environment.
  4. Next, download the software at apcupsd.org and install. The installer will automatically create and start the APCUPSD service and install the tray utility (useful for non-Server core installs only) by default.
  5. Once APCUPSD is installed, open the config file located (by default) at C:\apcupsd\etc\apcupsd\apcupsd.conf. The config file is well commented and should help you with configuration if you have a setup that deviates from the ethernet based management card used in this guide. To configure APCUPSD for an Ethernet Management Card, you will change the following settings in apcupsd.conf:
    UPSCABLE ether #Sets the connection type to ethernet
    
    UPSTYPE pcnet #Sets the connection protocol to PowerChute
    
    DEVICE upsipaddress:upsusername:upspassphrase #Tells APCUPSD how to connect to the UPS. Replace the values with what is correct for your environment
    
    LOCKFILE /var/lock #Sets the location of the lockfile
    
    UPSCLASS standalone #Sets the UPSCLASS to the appropriate type for a SmartUPS
    
    UPSMODE disable #Turns off sharing (only for ShareUPS models)
    
  6. Once you have saved the config file you can now configure Windows Firewall to allow APCUPSD to connect to the Management card. Execute the following commands on the server to configure the Firewall rules:
    netsh firewall set portopening protocol=TCP port=3052 name=APCUPSD3052
    
    netsh firewall set portopening protocol=UDP port=3052 name=APCUPSD3052
    
    netsh advfirewall firewall add rule name="APCUPSD" protocol=TCP dir=in localport=3551 remoteport=3551 action=allow
    
  7. Now that APCUPSD and the Windows Firewall is configured, you can restart the APCUPSD service and test connectivity. To restart the service, use the following commands:
    net stop APCUPSD
    
    net start APCUPSD
    
  8. To test connectivity (you may have to give the service 30seconds or so after starting before it connects), use the follow command:
    apcaccess status localhost:3551
    
  9. If you see results similar to below, including the line "STATUS : ONLINE" you're up and running. Make sure you do a real power loss (pull the cord) test as soon as your environment allows!
Filed under: IT, Work No Comments