DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to.
DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued

Recent change in Datanucleus uses fully qualified name to access database objects, which is in the form of <catalog>.<schema>.<object>. However, the schema name for SQL Server has been historically set to empty string "". Therefore the fully qualified name for a SQL Server object is something like "mycatlog..mytable". With this however it cannot find an existing table in the database.

Recent change in Datanucleus uses fully qualified name to access database objects, which is in the form of <catalog>.<schema>.<object>. However, the schema name for SQL Server has been historically set to empty string "". Therefore the fully qualified name for a SQL Server object is something like "mycatlog..mytable". With this however it cannot find an existing table in the database.
This problem demonstrates in Apache Hive bug HIVE-5218:
https://issues.apache.org/jira/browse/HIVE-5218

Your patch is invalid since it will fail when someone is using earlier than SQLServer 2005. So you need to add a check on max/min version (or similar) and if 2005+ then use your code, otherwise use old code.

Andy Jefferson added a comment - 08/Oct/13 08:54 PM Your patch is invalid since it will fail when someone is using earlier than SQLServer 2005. So you need to add a check on max/min version (or similar) and if 2005+ then use your code, otherwise use old code.

Andy Jefferson added a comment - 10/Oct/13 10:34 AM SVN trunk has a form of this "patch", with check on version of SQLServer based on web search. Totally untested, and nobody else with SQLServer has reported a problem so likely minority interest