Author: Martyn

Posted on

OpenHab HABPanel – Custom Widget – Change Color

The below example will look at itemName_thing and if the value is “off” then the text will be green else it will be red

<div class="col-xs-4 text-left" ng-style="{ color: itemValue('itemName_thing')=='off'?'green':'red' }">

This follows the standard Angular JS Ternary structure for an if statement

{ConditionVar ? 'varIsTrue' : 'varIsFalse'}

Posted on

OpenHabian – Cloning myself … failed

On my Pi 3b OpenHabian would not self install.

  • Log in with the default credentials openhabian/openhabian
  • Check you have internet access {ping google.com} – if not fix that
  • Check if the directory exists and it can’t overwrite /opt/openhab
  • Check your Date and Time of the system using the command date (will cause SSL Failures if really wrong)

For me the date was wrong so issued 

# sudo date mmddhhMMYYYY
  • mm = Two number Month
  • dd = two number day
  • hh = two number hour
  • MM = two number minute
  • YYYY = 4 digit year.

Posted on

SQL Server Version Numbers

SQL Server has version number like 13.0.5026.0. See below for version numbers.

  • SQL Server 2017 – 13.x.xxxx.x
  • SQL Server 2016 – 12.x.xxxx.x
  • SQL Server 2012 – 11.x.xxxx.x
  • SQL Server 2008 R2 – 10.50.xxxx.x (Final Build 10.50.6000.34)
  • SQL Server 2008 – 10.0.xxxx.xx (Final build 10.0.6000.29
  • SQL Server 2005 – 9.xx.xxxx.xx (Final build 9.00.5000.00)

Determine SQL Server Version

To determine the version of SQL Server, you can use any of the following methods.

Method 1: Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

Method 2: Look at the first few lines of the Errorlog file for that instance. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG and ERRORLOG.n files. The entries may resemble the following:

2011-03-27 22:31:33.50 Server      Microsoft SQL Server 2008 (SP1) - 
10.0.2531.0 (X64)

                March 29 2009 10:11:52

                Copyright (c) 1988-2008 Microsoft Corporation

Express Edition (64-bit)
on Windows NT 6.1 <X64> (Build 7600: )

This entry provides all the necessary information about the product, such as version, product level, 64-bit versus 32-bit, the edition of SQL Server, and the OS version on which SQL Server is running.

Note The output of this query has been enhanced to show additional information, as documented in the blog post article, What build of SQL Server are you using?, for the following versions:

  • SQL Server 2014 RTM CU10 and later versions
  • SQL Server 2014 Service Pack 1 CU3 and later versions
  • SQL Server 2012 Service Pack 2 CU7 and later versions

Method 3: Connect to the instance of SQL Server, and then run the following query:

Select @@version

An example of the output of this query is the following:

Microsoft SQL Server 2008 (SP1) - 
10.0.2531.0 (X64)
  March 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit)
  on Windows NT 6.1 <X64> (Build 7600: )

Note The output of this query has been enhanced to show additional information. This is documented in the blog post article, What build of SQL Server are you using?, for the following versions:

  • SQL Server 2014 RTM CU10 and later versions
  • SQL Server 2014 Service Pack 1 CU3 and later versions
  • SQL Server 2012 Service Pack 2 CU7 and later versions

Method 4: Connect to the instance of SQL Server, and then run the following query in SQL Server Management Studio (SSMS):

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),

SERVERPROPERTY ('edition')

Note This query works for any instance of SQL Server 2000 or a later version.

The following results are returned:

  • The product version (for example, 10.0.1600.22)
  • The product level (for example, RTM)
  • The edition (for example, Enterprise)

References

https://support.microsoft.com/en-gb/help/321185/how-to-determine-the-version-edition-and-update-level-of-sql-server-an

Posted on

Rules to follow while naming a SQL Server Instance

Reserved Keywords in Microsoft SQL Server are not accepted. You cannot name a SQL Instance as DATABASE or ALTER or CREATE or SCHEMA (of course Capitals Letters does not matter).

First character should not be a numerical value (0-9), it can be an alphabet (a-z), underscore ‘_’, number sign ‘#’, or ampersand ‘&’.

Space and special characters (such as @, ^, *, \ ) are not allowed. 

Instance name should be 16 chars or less in length.