Categories: SQL Server

SQL Server Error : 117, Severity: 15. The %S_MSG name ‘%.*ls’ contains more th

SQL Server Error : 117 Details


SQL Server Error: 117
Severity: 15
Event Logged or not: No
Description:
The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d.
Severity 15 Description:
Indicates syntax errors in the Transact-SQL command.

 

This error can be encountered in the process of moving a database from one hosting provider to another. The current provider incorporates the domain name into the user name. The domain extension is .co.uk. As a result, some database objects have the fully qualified name user@company.co.uk.table for example.

But, attempting to change the schema of these objects in order to insert them into a dbo schema by using:

ALTER SCHEMA dbo TRANSFER user@company.co.uk.table

you get Error Message 117:

The object name ‘user@company.co.uk.table’ contains more than the maximum number of prefixes. The maximum is 1.

Solution for Resolving the Error

In above example the query processor is interpreting the dots as different prefixes, while in fact, they’re just part of your database name in most situations. Now, Solution is not actually increasing the amount of prefixes allowed  as error gives hint but is below with square brackets:
ALTER SCHEMA dbo TRANSFER [user@company.co.uk].table

SQL Server Error Code and solution summary


SQL Server Error: 117
Severity: 15
Event Logged or not: No
Description:
The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d.

Solution is below with square brackets:

ALTER SCHEMA dbo TRANSFER [user@company.co.uk].table

Vamshi B

Recent Posts

sql server detected logical consistency based error

Learn about SQL Server detecting logical consistency based issues and how to resolve them.

5 months ago

sql server error 1222

Learn about SQL Server error 1222 and how to resolve the lock request time out…

5 months ago

Microsoft SQL Server 2022 New Features

Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…

5 months ago

SQL Server Error 1222 lock request time out period exceeded

SQL Server Error 1222 lock request time out period exceeded   Lock request time out…

6 months ago

SQL Server Error : 427, Severity: 20. Could not load the definition for constr

SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…

10 months ago

SQL Server Error : 204, Severity: 20. Normalization error in node %ls.

SQL Server Error : 204, Severity: 20. Normalization error in node %ls.

10 months ago

This website uses cookies.