I am assuming the eligibility_ud columns is structured as: {SubscriberNumber}-{number}

So that would mean we could have something like: 123456789-01, 123456789-02, 123456789-03, ...

If that is the case, and the intended results...

If InfoSec already has an issue with replication because you are going from Prod to Non-Prod, then using backup/restore is also going to be an issue.  Anything that allows production...

If you cannot get the master key from the original source - then *hopefully* you have copies of all projects in VS so you can redeploy to a newly created...

CharIndex only uses a single character. For a group...

You can use something like this:

SELECT ...
     , col_1 = substring(v.Tag, 1, p1.pos - 2)
     , col_2 = substring(v.Tag,...

No - you don't need to change the max size as that only limits how large the file can get when it auto grows.  The auto growth setting is a...

I will jump in here - if you are backing up the database after you load new data and you are not modifying that data directly, then simple recovery will...

When you add a file to a filegroup - SQL Server uses a proportional fill algorithm.  Here is some information you can review:

https://learn.microsoft.com/en-us/sql/relational-databases/pages-and-extents-architecture-guide?view=sql-server-ver16

https://www.sqlskills.com/blogs/paul/investigating-the-proportional-fill-algorithm/

Basically, since you added a new...

If all of the files are in the same filegroup - then it was almost certainly spread across multiple volumes (drives) originally.  There are multiple factors to consider here:

1. Are...

The problem is that you are trying to format the results of a CAST to BIGINT.  Instead of using FORMAT (bad idea - really slow) and trying to cast those...

SSL uses the FQDN - if someone is connecting to SQL Server using listener.domain.com then the certificate must have that same name.  If it doesn't have the same name then...

There really isn't any benefit to splitting out the database into multiple data files - unless those data files are on different volumes.  The volumes can either be a drive...

The fast query is not the same as the slow query - I would focus on the differences.  For example - looks like the 'slow' query includes additional tables:

            
January 14, 2024 at 5:08 pm
            
#4361709

            
            
                                                
        

This configuration doesn't really make sense - it is either a DR scenario without an HA solution or it is just to allow for offloading read only workloads.

There are many...

As Phil pointed out - you can eliminate that message.  If you...