A Fine Slice Of SQL Server
Steven Sanderson goes for a walk on the stock exchange:
In the world of time series analysis, Random Walks, Brownian Motion, and Geometric Brownian Motion are fundamental concepts used in various fields, including finance, physics, and biology. Today, we’ll explore these concepts using functions from the
healthyR.tspackage.
Click through to learn about each of these concepts and some examples of how you can generate time series datasets following each of them.
Comments closedChris LaGreca spits out some dates:
I often work with time series data and find it useful to have a variety of ways to randomly generate dates. This particular example is great for evenly distributed date partitions. Running the script below with
the default argumentswill output a list of random dates, one for each month of the year.
It looks like this is generating based off of a uniform distribution, which probably makes the most sense for “give me a day of the month” data generation.
Comments closedJared Westover needs to delete some rows:
In this article, we’ll examine the importance of indexes in improving DELETE statements. Also, many developers assume that adding a foreign key creates an index, which means they’re typically missing. How can you identify which foreign keys are missing indexes? Don’t worry. A handy DMV helps find them. Starting today, you’ll have the skills to make your DELETE statements faster.
Click through for the full post.
Comments closedChad Callihan gets rid of dupes:
In a recent comment on a my post about combining CSV files using PowerShell, a reader named Oliver asked how duplicate values should be handled when combining multiple CSV records. I added a suggestion to that post but figured, “Why not elaborate more on a post of its own?”
Why not, indeed? Click through for the solution.
Comments closedJeff Iannucci gives us the details:
SQL Server database ownership may seem like an insignificant concern, but choosing the wrong owner for your database can be a main contributor to security disasters like ransomware. Let’s talk a bit about how to choose an owner that doesn’t create a huge security vulnerability for you and your SQL Server instance.
(Note: this isn’t the same as being in the db_owner role, although we will look at that later in this post.)
Click through for more information. This is one of the big reasons to avoid cross-database ownership chaining or setting TRUSTWORTHY on any database. Jeff has another way of resolving this particular problem that works, but the best solution is not to use either of those features.
Comments closedSagheer Ahmed sets up TLS encryption:
This technical guide provides detailed instructions on how to configure SSL/TLS encryption for SQL Server using a self-signed or CA-issued certificate. Secure your data transmissions and enhance your security posture with these essential steps.
Read on for the instructions.
Comments closedSteven Sanderson toes a bit of tag replacement:
Hello, R enthusiasts! Today, we’re jumping into a common text processing task: extracting strings between specific characters. This is a great skill for data cleaning and manipulation, especially when working with raw text data. I’m going to show you how to achieve this using base R, the
stringrpackage, and thestringipackage. Let’s go!
Read on for examples.
Comments closedMika Sutinen thinks about how things could go wrong:
Failure Mode and Effect Analysis(FMEA) is a process of building more resilient systems, by identifying failure points in them. While it’s highly recommended to perform FMEA during the architecture design phase, it can be done at any time. More importantly, it should be reviewed periodically, and especially when the system architecture changes.
While you can do Failure Mode and Effect Analysis for whole systems, in this post, I will share an example on how to get started with FMEA for a database environment.
Read on for a description of the concept and some tips on how to perform one.
Comments closedMike Lynn talks Transparent Data Encryption:
Transparent Data Encryption uses certificates in its architecture for protecting your data while at rest. One attribute of a certificate is they have an expiration date. Certificates expire for a couple reasons, but the main reason is to enforce security. When a website certificate expires it forces the website owners to get a new certificate by proving they are who they say they are with a trusted third party.
SQL Server certificates that are used for TDE also have an expiration date, but these dates are only checked when you are creating a self-signed certificate using the “CREATE CERTIFICATE” T-SQL command. If you don’t supply an expiration date when creating your certificate SQL Server will assign one that is 1 year into the future.
Read on to learn more about how it works with TDE. I will say that with encrypting backups, SQL Server does care about the expiration date when it comes to creating a new encrypted backup, but not when it comes to restoring a backup.
Comments closedKoen Verbeeck copies some data:
We have a couple of Snowflake databases and would like to have that data available in Microsoft Fabric as well. Is there an easy solution to get the data quickly in Fabric? We don’t have many technical people on staff, so writing complex ETL is not an option.
Read on for more information on how it works. Mind you, you’re probably still writing the T and some of the L after using mirroring.
Comments closed