did you specify the "ApplicationIntent=ReadOnly" parameter with your connection and is you secondary readable?

I put dev in read-only restricte mode ( with rollback immediate ) to force everybody out, before attempting to restore.

is SQLServer Configuration Manager working OK ?

ref: configuration-manager-is-corrupt

Add RAM & SSD ( especially for tempdb )

FYI Many of the production restores I've had to perform was due to devs learning the delete statement.

BTW I messed up a couple of client machines myself tampering with powershell...

• This reply was modified 4 years, 4 months ago by Johan Bijnens.

Indeed, Jeff

create clustered index ci1 on z1(id) --> creates a non-unique clustered index ( that holds the data at leaf level ! )

alter table Z1 Add constraint PK_Z1 primary key (id)...

• This reply was modified 4 years, 4 months ago by Johan Bijnens.

Check out dbatools.io Export-DbaDbTableData

You should indeed figure out if implementing the suggested missing index makes sense ( chances are ).

Maybe even add an index on your dbo.PLNewData table ( I've just put the...

Test the given catch-all options ! YMMV ( I'm on the "option (recompile) should be a last choice"  side)

after database restore, you need to double check and setup SSB again !

check https://www.mssqltips.com/sqlservertip/5365/steps-to-restore-service-broker-enabled-database-on-new-sql-server-instance/

What I wanted to point to is that a given UniqueClaimID e.g. 10929_6155... is being counted 5 times as there are 5 ProvOrgNm using it, on a total of 134865...

No offense intended at all, nor questioning any level of knowledge.

So you're talking DNS aliasses, wright?

You could connect using "MyInstanceName\MyInstanceName" , no port number needed and SQLBrowser will resolve the...

• This reply was modified 4 years, 5 months ago by Johan Bijnens.

If you're using SQLuser accounts, be sure to copy them up front

Easyiest using DBATOOLS powershell module

$SourceSQL = 'Server\instanceA'
$TargetSQL = 'Server\instanceA'
Copy-DbaLogin -Source $SourceSQL -Destination $TargetSQL -ExcludeSystemLogins

you can even...

Well, some instances may not use port 1433 !

You'll actually need to double check that the instance you are trying to address is actually the one listening at that port...