SET LANGUAGE failed because '' is not an official language name or a language alias on this SQL Server
-
I'm trying to migrate a DB from SQL 2005 to SQL 2014 Standard. Vendor provided an application that migrates the DB between servers. I'm able to connect to the source but getting this error when connecting to the target
SET LANGUAGE failed because '' is not an official language name or a language alias on this SQL Server
Instance runs on Server 2012 R2.
I made sure the English language is set properly in SQL server properties and made sure my Local Settings are set to English
For testing I installed the same SQL version on Win 10 box and able to connect with no problems
I googled for solution for a long time and did not find anything that applies to my situation
would appreciate any help
Thanks
Peter
- peter 98284 - Tuesday, February 14, 2017 12:02 PM
What are you connecting from?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
from the target server which is the Server 2012 R2 running SQL 2014 Standard.
- peter 98284 - Tuesday, February 14, 2017 12:13 PM
Sorry, I meant from what application. From SSMS?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
sorry, it's special Java based tool for Primavera P6 application, that connects to the source and target SQL servers and migrates DBs. I tried to just do regular MS SQL backup/restore but the application on the new server would not run, so this tool runs other scripts to make it work
this is what it looks like
- peter 98284 - Tuesday, February 14, 2017 12:24 PMsorry, it's special Java based tool for Primavera P6 application, that connects to the source and target SQL servers and migrates DBs. I tried to just do regular MS SQL backup/restore but the application on the new server would not run, so this tool runs other scripts to make it work
this is what it looks like
Try running sp_helplanguage on the problematic server and comparing the results with those from a server with no issues.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
Maybe this row is missing on the problematic server?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
getting same results
0 mdy 7 0 us_english English January,February,March,April,May,June,July,August,September,October,November,December Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov,Dec Monday,Tuesday,Wednesday,Thursday,Friday,Saturday,Sunday 1033 1033
-
In case it is of help to anyone.
My problem was the case sensitive, ENGLISH or ITALIAN is not valid but English or Italian work OK.
- txustopo wrote:
In case it is of help to anyone.
My problem was the case sensitive, ENGLISH or ITALIAN is not valid but English or Italian work OK.
Hi and welcome aboard. That's actually a really pertinent post for this 5 year post and that's why I like this site so much. No "Comments are Closed" here! Well done and glad to "meet" you.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply