Topic: [SOLVED] problems with SQL Server dbo schema
[SOLVED] problems with SQL Server dbo schema
Hi. I am really excited about DataCleaner. I could use it as a generic replacement for a tool that I wrote just to profile/validate one column in a database.
I just downloaded 1.2, but I can't get it working on my database. I'm trying SQL Server 2005, using both Microsoft's driver and the JTDS driver. With either, when I go to preview the table or profile the data, I get an error like this:
INFO JdbcDataContextStrategy - SELECT "action_status"."ai_key", "action_status"."action_status", "action_status"."created", "action_status"."obsolete" FROM dbo."action_status"
WARN JdbcDataContextStrategy - Exception occurred when executing query: Invalid object name 'dbo.action_status'.
Exception in thread "AWT-EventQueue-0" dk.eobjects.metamodel.MetaModelException: Could not execute query
at dk.eobjects.metamodel.JdbcDataContextStrategy.executeQuery(JdbcDataContextStrategy.java:385)
at dk.eobjects.metamodel.DataContext.executeQuery(DataContext.java:280)
at dk.eobjects.datacleaner.gui.windows.PreviewDataWindow.<init>(PreviewDataWindow.java:45)
If I copy-and-paste the query into Oracle SQL Developer (connecting to SQL Server using the JTDS driver) it works fine.
Should I just file this as a bug?
I just downloaded 1.2, but I can't get it working on my database. I'm trying SQL Server 2005, using both Microsoft's driver and the JTDS driver. With either, when I go to preview the table or profile the data, I get an error like this:
INFO JdbcDataContextStrategy - SELECT "action_status"."ai_key", "action_status"."action_status", "action_status"."created", "action_status"."obsolete" FROM dbo."action_status"
WARN JdbcDataContextStrategy - Exception occurred when executing query: Invalid object name 'dbo.action_status'.
Exception in thread "AWT-EventQueue-0" dk.eobjects.metamodel.MetaModelException: Could not execute query
at dk.eobjects.metamodel.JdbcDataContextStrategy.executeQuery(JdbcDataContextStrategy.java:385)
at dk.eobjects.metamodel.DataContext.executeQuery(DataContext.java:280)
at dk.eobjects.datacleaner.gui.windows.PreviewDataWindow.<init>(PreviewDataWindow.java:45)
If I copy-and-paste the query into Oracle SQL Developer (connecting to SQL Server using the JTDS driver) it works fine.
Should I just file this as a bug?
Hi,
Thanks for the report and I'm sorry to hear about your troubles. For 1.2 we've changed the underlying query-mechanism to use MetaModel and it's [MetaModelCompliancy compliancy with MS SQL] is still a gray area I'm afraid. We're planning to incorporate integrationtests of MS SQL which will guarantee compatibility, but we're not quite there yet (primarily we are in need of a MS SQL server for executing the tests).
In previous versions of DataCleaner MS SQL was reported to work fine, did you take a look at DataCleanerMicrosoftSql ?
Please post a defect ticket (component = MetaModel) and we will look into it shortly!
Thanks for the report and I'm sorry to hear about your troubles. For 1.2 we've changed the underlying query-mechanism to use MetaModel and it's [MetaModelCompliancy compliancy with MS SQL] is still a gray area I'm afraid. We're planning to incorporate integrationtests of MS SQL which will guarantee compatibility, but we're not quite there yet (primarily we are in need of a MS SQL server for executing the tests).
In previous versions of DataCleaner MS SQL was reported to work fine, did you take a look at DataCleanerMicrosoftSql ?
Please post a defect ticket (component = MetaModel) and we will look into it shortly!
Wait a sec.
Can you preview other tables in your database?
Because this discussion which have some similarities to your description of the bug, this might be a security access restriction playing with us. Are you connecting as the same user from withing datacleaner as you are in your oracle client? Please take one more look and if you can't find the cause - please post the bug ;-) And if you find it we would appreciate to hear about it so we can post it for future requests!
Can you preview other tables in your database?
Because this discussion which have some similarities to your description of the bug, this might be a security access restriction playing with us. Are you connecting as the same user from withing datacleaner as you are in your oracle client? Please take one more look and if you can't find the cause - please post the bug ;-) And if you find it we would appreciate to hear about it so we can post it for future requests!
Thanks. Your response was enough to prod me into trying other things. I changed from
URL: jdbc:sqlserver://host:port
Catalog: my_database
to
URL: jdbc:sqlserver://host:port;database=my_database
Catalog: <blank>
and it works now.
URL: jdbc:sqlserver://host:port
Catalog: my_database
to
URL: jdbc:sqlserver://host:port;database=my_database
Catalog: <blank>
and it works now.
Great, I'm very glad to hear so! That whole catalog thing is beginning to be somewhat a mystery to me. Seems almost no databases use that property, but we kept it in the dialog to ensure that if some databases use it we would have the option available.
Log in by clicking the login link at the top of the screen
Go back to forum.
