you can use a sequence for that instead of an identity.

loopback? have a look at https://blog.sqlauthority.com/2017/04/18/sql-server-login-failed-login-untrusted-domain-cannot-used-windows-authentication/

and https://arslan-bobir.medium.com/sql-server-troubleshooting-resolving-the-login-is-from-an-untrusted-domain-and-cannot-be-used-7a1a6c715817

and... probably not but worth looking at.

https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-configure-encryption-types-allowed-for-kerberos - if a new server it is likely that RC4_HMAC_MD5 is disabled - if so try enabling...

is this still using the same formula you had on your original thread (https://www.sqlservercentral.com/forums/topic/round-or-convert-the-output-of-the-power-function) - or are you now trying to use the correct IRR

when using the NT Service account the SPN's are created under the COMPUTER account.

setspn -L "computername$" will give the specific SPN's that were set.

but... if you already changed the account...

the question is WHY - I fail to see any reason why using temp tables would be an issue. that is what TEMPDB is for, and there are no special...

did you follow the steps here https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/replication-two-instances-and-sql-server-configure-tutorial?view=azuresql

SQL MI to onprem does not follow standard way of doing it between 2 onprem servers.

as far as I remember the latest version of SQL BPA is for 2012 - https://www.microsoft.com/en-in/download/details.aspx?id=29302

nothing seems to have been done (or will be done ) on that tool so...

not much you can do about that query (which is the version I gave you) - the nature of the query does not really allow for pre-filtering or use of...

did you do the steps highlighted at https://cloudblogs.microsoft.com/sqlserver/2022/07/28/azure-active-directory-authentication-for-sql-server-2022/

times on a I7 6 core laptop

according to explan plan query cost (relative to batch= are 0, 0, 100% respectively  - so DEFINITELY NOT something to use.

- with while loop...

option 1 is incorrect - just discard it.

can you give the plan for the second? was expecting it to be a bit faster than that.

regarding your last query (from the second plan). two options below

option 1 is just a adjustment of your original query - does same thing but with 1 less join. may...

can you try this slight variation of my second example and give runtime and plan as well.

drop table if exists #weeklastday;
drop table if exists #temp1;

select distinct t1.EXPIRATION
into...

that plan is from you version of the change e.g. where you still keep the dateadd and your temp table does not filter or change the expiration date.

can you give...

how much faster? can can you also put new explain plan.