To me that sounds like when the disk had bad sectors which resulted in data getting corrupted in the system databases and possibly user databases.

First, I would put it into...

I would start by reaching out to Microsoft for support.

They may suggest that you rebuild master, but you will lose all of your logins and roles and other objects stored...

I am thinking you mean DLL not DDL.  Wireshark would probably help determine if it is network related, and I am still leaning towards something on the network stack between...

With the view, if the indexes on the table are "good enough" for it, then you could still use the view without the index on it.  This would allow you...

Pretty sure in SQL Server, that would be a view or a table.

You cannot name a query.  So whatever the contents of the query "QRY_DATES" are, you would need to...

If I am understanding your post correctly, switching to Windows Server 2019 is causing the slowness getting data from the SQL instance, correct?

If so, I would guess the problem is...

My first thought would be firewall or permissions.

Permissions could be a problem if the SQL Server Service account (or Agent service account or the Polybase service account... not 100% certain...

type = 'U' means you are grabbing all "user" type of login.  To SQL, a "human" and a "non-human" are identical.  It is just a login.

How would SQL know the...

I would go with that approach UNLESS the full CHECKDB fails on the restored DB.  If it fails, I would then run a full on prod as well to ensure...

Pretty sure that my advice above would apply to views as well.  Profiler or plan cache will capture the TSQL being run and then you can review and audit it.

The...

If there is any data you would be upset or in trouble for if it got leaked, I would encrypt it.

My opinion - there isn't anything worth stealing in the...

One approach that MAY work for you would be to break it up into multiple steps.

Since pulling the inner queries into a temp table improves performance, why not just use...

Looking at the execution plan, I am thinking that adding an index on SubscriberID may help as you are using those in the WHERE clause.

Your estimated number of rows is...

There is a good article on checkdb here:

https://www.mssqltips.com/sqlservertip/2399/minimize-performance-impact-of-sql-server-dbcc-checkdb/

I do recommend you read that as it addresses your concerns with PHYSICAL_ONLY as well as using the backup-restore-checkdb approach.

The best way to work with performance issues is to look at the execution plan.  Could you post the execution plan for your query?

When I run the above, it is...

• This reply was modified 3 years, 10 months ago by Mr. Brian Gale.