Referencing a formatted text source field, using the SQLQUERY function and 'LIKE'

Scribe has the ability to insert SQL queries against a source or target (which does not have to be a database for Scribe). This works great when searching against distinct values.

However, what if you need to format a source field to strip out and prefix text, then match it up to a larger field? In SQL you can declare a variable and perform a LIKE statement.

Plugging that statement into Scribe will cause it to fail. Here is the workaround.

Format the source variable, and save it as a calculated variable to call later.

RIGHT( S1, LEN(S1)-SEARCH(" ",S1 ) ) = cvTrim

Then call your query.

SQLQUERY( cv_Trim, "T", "SELECT [TableField] FROM [Database].[dbo].[Table] WHERE [TableField] LIKE '%' + '%s' + '%' " )

%s references the source field.

Comments

SCSM Data Warehouse Cube / Dimensions do not process - Event 33573 / 35574

Recently I received an alert from our SQL server "OLE DB error: OLE DB or ODBC Error: Operation Cancelled HY008. Around that same time, I found a few errors in our Operations Manager log on our SCSM 2012 R2 DataWarehouse Management Server. Specifically Events 33573 and 33574. Event 33573 Warning Message : An Exception was encountered while trying during cube processing. Message= Processing warning encountered - Location: , Source: Microsoft SQL Server 2012 Analysis Services Code: 1092550657, Description: Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'WorkItemDim', Column: 'WorkItemDimKey', Value: '18553'. The attribute is 'WorkItemDimKey'.. Well, that appears that a overnight job did not run for our SCSM data warehouse. However, when I looked at the Data Warehouse Jobs in the SCSM Console, all of the status were either set to Not Started, or success. Going back to the logs on t...

SQl Upgrade Error - Access to the Path C:\Program Files\Microsoft SQL Server\110\License Terms\SQLServer2012_License_SQLBI_1033.rtf is denied

SQL Upgrade Error - Access to License Denied Ahh a wonderful time to experience an error, when you are upgrading SQL, during a limited window for downtime. Sop much for the weekend plans eh? No worries, this one is easy. In my case I received the following when downgrading an edition for a reporting Server that houses several instances. After the first one processed, I received this error: If I browse to that path, we notice the file is set to read only. Easy enough, lets un-check read only and try again. Success! I had to do this for each instance install. So if you have multiple instances be prepared to set the file to read/write each time.

PowerShell - Add telnet client to Windows Server 2012 R2

I was trying to check port specific communication on a server, so I decided to power up good old telnet. Much to my surprise it was not installed on the Server. PowerShell to fix that issue! Add-WindowsFeature telnet-client All set. No Reboot needed. -AJ

My Dynamic World

Search This Blog