SQL Service Principal Names

[@richard90153]

Thank you! Helpful in tracking down a domain issue I was having. You sparked the thought that fixed the issue.

[@michaelgoedeker9697]

Your amazing!! Thank you for this!

[@BJP719]

Very helpful, thanks! Will use this to troubleshoot "Target Principal Name is Incorrect" when trying to connect to SQL Server from one domain to another via SSMS.

[@mahmoodalsaadi2331]

You are really doing well, thank you very much MAN!

[@gaoussoubagate5903]

Good explanation, and clear for SPN.

[@GuyInACube]

Thanks! I'm thinking of revisiting this topic and put it in the context of SQL Server 2016, and also look at how SharePoint 16 affects this.

[@binaryblog]

Hello, If I use 3 different domain user accounts for SQL services like Server Agent, SQL Server Agent Database Engine etc, do I have to configure SPN for all of them?

[@GuyInACube]

The SPN is service dependent. So, if you have a Database Engine, Agent and Reporting Services, and they each use a different Domain Account, you would handle them by service. So, the SQL Service would get the SQL SPN on it's service account. Agent doesn't get an SPN. Reporting Services may or may not require an HTTP SPN depending on what you are doing, but it would go on it's service account. If you have multiple SQL Engine instances, they each get their own unique SPN depending on the protocol. Those SPN's would go it their specific service accounts. The big thing to remember is that SPN's are unique and you can only have one.

[@binaryblog]

Guy in a Cube Thank you for your clear and helpful explanation.

[@I2amI3o]

Thank you, Very Helpful!

[@GuyInACube]

Glad it helped! Thanks for watching!

[@natarajvd]

Excellent