Not real sure I follow - but it shouldn't be too much of an issue to add a script task with the UserID (defined as a variable and populated in...

Okay - no real reason to do this since it works from SQL Server, but to do this you...

A new cardinality estimator was introduced in SQL Server 2014 and could cause some queries to get a less than optimal execution plan.  I suspect that is what is happening...

Thanks Anthony for your help

If i get you well you are saying i must add a file group add 2 files which will be ndf not mdf and the...

That works, but you lose the fail over if that is a concern

Log shipping won't get you near-real time data in a read-only database.  You have to stop applying log files and switch the database to STANDBY for it to be accessible,...

I missed that this database was already included in the other AG.  You are fairly stuck here...

If you already have a secondary that is set to read-only, why do you...

Since the clustered index is the data - any other indexes should be able to be dropped and recreated with no data loss.  The non-clustered indexes will be built from...

Are you on Enterprise Edition - or are you using Standard Edition?

Assuming Enterprise Edition, you can add that third machine into the cluster, install a stand-alone SQL Server instance and...

One of the indexes is the primary key - but that index may not be the clustered index.  If it isn't the clustered index you may be able to rebuild...

Sorry that guy had one of my post removed. He is a freelancer and well known on sql central

I'm getting:

<li style="list-style-type: none;">

• data conversion error(truncation)

<li style="list-style-type: none;">

...

See if this is an improvement

   With excludeRoles
     As (
 Select lr.legalID
   From legalReference     ...

You also have to be aware of transaction log usage - if you import a large file in a single batch you will need at least that much...

@Brian - your solution is not the same as the original query.  The original query is joining to the max date for each column1 - not the max date across...

That function is going to be a performance killer - no matter what.  As it is used - it must be a scalar function and therefore needs to execute for...