If you have done any text/data analysis, you might already be familiar with Regular Expressions (RegEx). RegEx evolved as a necessary tool for text editing. If you are still using RegEx to deal with text processing, then you may have some problems to deal with. Why? When it comes to large-sized texts, the low efficiency of RegEx can make data analysis unacceptably slow.
In this article, we will discuss how you can use FlashText, a Python library that is 100 times faster than RegEx to perform data analysis.
Learn more on the GitHub repo. I haven’t used this before but I could see it being handy.
A summary of the paper is:
We present a very simple, informal mathematical argument that neural networks (NNs) are in essence polynomial regression (PR). We refer to this as NNAEPR.
NNAEPR implies that we can use our knowledge of the “old-fashioned” method of PR to gain insight into how NNs — widely viewed somewhat warily as a “black box” — work inside.
One such insight is that the outputs of an NN layer will be prone to multicollinearity, with the problem becoming worse with each successive layer. This in turn may explain why convergence issues often develop in NNs. It also suggests that NN users tend to use overly large networks.
NNAEPR suggests that one may abandon using NNs altogether, and simply use PR instead.
We investigated this on a wide variety of datasets, and found that in every case PR did as well as, and often better than, NNs.
We have developed a feature-rich R package, polyreg, to facilitate using PR in multivariate settings.
The paper and presentation slides are ungated, so check it out. H/T R-bloggers
A common mistake, and one I make frequently myself is to use a string in place of an identifier, or vise-versa. So to start, let’s have some definitions, shall we?
a linear sequence of characters, words, or other data.
a sequence of characters used to identify or refer to a program or an element, such as a variable or a set of data, within it.
And because I always find examples fairly useful.
Click through for the example as well as additional explanation.
I started Power BI Helper with the intention to help to find issues in Power BI reports faster and easier. This tool over time became better and better. I’m excited now to let you know that the version 2.0 of this product is now available for everyone to use and enjoy. This version comes with these features:
Connecting to more than one Power BI model. Selection option for the model.
Showing the connection mode of the Power BI file.
Showing list of tables that are NOT used in any visualization, and can be hidden from the report.
- List of both directional relationships
- List of inactive relationships
Some minor bug fixes
It looks like quite the useful tool.
Ever seen the below error? Until this week I hadn’t. So, I figured I’d take a little time and introduce it to those that had not.
Error Description: Length of LOB data (65754) to be replicated exceeds configured maximum 65536. Use the stored procedure sp_configure to increase the configured maximum value for max text repl size option, which defaults to 65536. A configured value of -1 indicates no limit
We ran into an issue with a customer this week, this error was flooding the error log. After a little digging I found it had to do with transactional replication (also applies to Change Data Capture) they had setup which included LOB data.
Read on to see what you can do to resolve this error. Also, check out the comments and be glad you’re not in that boat…unless you are, in which case…
There are many similarities between
DATEPARTreturns the date or time part as an integer,
DATENAMEreturns the part as a character string.
DATENAMEfunction also takes two parameters: the date or time part we want back, and the input date. Just as we saw with
DATEPART, the documentation indicates the input date parameter must be an “expression that can resolve to one of the following data types: date, smalldatetime, datetime, datetime2, datetimeoffset, or time.”
Similarly, the date and time parts that can be returned look much like those in
DATEPART, which gives us another opportunity for the reminder that we should avoid using the available abbreviations in order to help with writing clearly understandable code.
DATENAME is a useful function for displaying parts of dates & times, but Randolph does lay out the caveats.
So, what are our options?
Create/Edit/Delete ourselves using Powershell/.Net/Python/Go/Java/Some Other SDK
Process something else (YAML?) into JSON
Generate the ARM using c#/Powershell/something else
3rd party tools, (Terraform is the big daddy) / others include Sparkle Formation
To be honest, I’d probably just stick with ARM templates.
The June public preview release is focused on improving our Extensibility experience with the release of new extensions as well as addressing top GitHub issues.
Highlights for this build include the following.
SQL Server Profiler for SQL Operations Studio Preview extension initial release
Azure SQL Data Warehouse extension
Edit Data Filtering and Sorting
SQL Server Agent for SQL Operations Studio Preview extension enhancements for Jobs and Job History views
Build your own SQL Ops Studio extension
Visual Studio Code Refresh
Fix GitHub Issues
I saw “SQL Server Profiler” and started wondering what was going on, until Alan explained that it’s actually the lightweight Extended Events profiler and not the heavyweight beast we know and love and/or hate.