Renaming SQL servers and SPN issues
Posted on 2011-10-22
We have a SQL server, SQLA. We then setup a new server to replace it, but named it SQLB for a few weeks while we set it up. When SQLB was ready for production, we renamed SQLA to SQLX, then renamed SQLB to become the new SQLA. Things didn't come back up very well, and I believe it has to do with SPNs. After the renames, the SQL agent accounts were not associated with the right server name anymore.
Can someone tell me if this sounds correct? I created two SPNs as listed below, and then things started working.
setspn -a MSSQLSvc/SQLA:1433 se\sqlsvcaccount
setspn -a MSSQLSvc/SQL.domain.com:1433 se\sqlsvcaccount
Are there more SPNs I need to add? Like for the host?