I am trying to publish cube which is created on pentaho schema workbench and trying to analyses the result into bi server, in this procedure i am successfully published the cube but facing exception of Table not found in statement exception in saiku server even if the table is exist in the mysql database so what can i do to resolve this exception?
Check your data sources file - Saiku is probably not using the right schema for the database so is looking in a different place.
Related
I have some list of Tables to be created in SQL Server with the same structure as they are currently present in MySQL DB.
Tools which i can use are SSIS , SQL Server (T-SQL) But haven't found a solution still
I am using SSIS package Transfer SQL Server Objects task in order to transfer some tables from local SQL Server database to Azure SQL.
My task fails with the following error "USE statement is not supported to switch between databases. Use a new connection to connect to a different database."
I have read that this error occurs because master database is used and can be fixed by prefixing table names (for the tables to be transferred) with a database name. Unfortunately I cannot do that because when selecting table names there is no option to add database name as prefix - only schema name. So I am stuck here. Any suggestions?
Transfer SQL Server Objects task is using SMO in the background, which then uses the "USE" statement. This makes Transfer SQL Objects incompatible for connecting to Azure SQL Database.
My recommendation is to use Azure SQL Data Sync if you are only synchronizing tables: https://msdn.microsoft.com/library/azure/hh456371.aspx
Let me know how you go with it.
Julie
I have MySQL running on my local machine. I have created several tables in MySQL workbench and connected WebMatrix to the MySQL DB. All the tables are present, however one of them does not contain any data (but it contains data in MySQL database). I have refreshed in Web Matrix, redone the connection string etc but the data does not display. When I try to run the SQL that populated the database in MySQL, inside of WebMatrix I receive this error from the Database Manager:
Object reference not set to an instance of an object.
My SQL is too long to post here. Any suggestions?
Restarted MySQL service and refreshed in WebMatrix. Data is now present. Not sure what was causing the issues but is resolved.
I have been working on this all day and now I'm stuck, so hopefully someone out there can help me :)
The challenge.
Migrate data from MS SQL to MySQL.
The MS SQL I received as a bak file, which I restored using SQL server management studio on a PC with Windows 7 Home edition.
I have created a source MySQL database on a webserver, running LAMP.
The solution (maybe)
I'm currently trying to convert the database, initially just one table for testing, using MySQL Workbench with the database->migrate wizard, but now I'm stuck at the Bulk Data Transfer. I would expect this step to create the table in my MySQL database and transfer the data, but that never happens.
For the source I choose Connection Method = ODBC (native)
No problems connecting to the source and destination databases
I choose to keep schema info as table prefix, so imported tables look like: database.dbo_table_name
Migration step succeeds (migrate selected objects & Generate SQL Create Statements)
The Create statements look like this if I don't edit them
CREATE TABLE IF NOT EXISTS 'restored_database_name'.'dbo_table_name' … I think the 'restored_database_name' part causes a permission error. It does if I type this in the SQL tab directly in phpMyAdmin. Therefore I change it to:
CREATE TABLE IF NOT EXISTS 'dbo_table_name' …
Also per default this is part of the SQL:
DROP SCHEMA IF EXISTS 'restored_database_name';
CREATE SCHEMA IF NOT EXISTS 'restored_database_name …
I think this also causes some permission issues, so I commented these out.
In the next step I uncheck the 'Create schema in target RDBMS' since I don't think I want this.
The problem:
Nothing interesting for the next steps, but then at the "Bulk data Transfer" I get this error:
ERROR: 'restored_database_name'. 'dbo_database_name': mysql_stmt_prepare: SELECT command denied to user 'mysql_user_name'#host' for table 'dbo_database_table_name.
Finished copying 0 rows.
I think the error is somehow related to permissions on the destination database. I wonder if it is possible to make sql file, not just with the create table commands, but also with INSERT commands so I could just take the sql and import it using command line or phpmyadmin.
I'm using Workbench 5.2 CE
Any help is appreciated
I've seen that you have made your way into the Workbench's Migration Wizard. Maybe you're just missing something so I suggest you to review this blog so you can verify your steps: How-To: Guide to Database Migration from Microsoft SQL Server using MySQL Workbench.
Unfortunately you can't use the Migration Wizard data copy command line utility to generate the SQL file with all the inserts, but I'm pretty sure you can get this from MS SQL Server Management Studio and it should pretty much work for MySQL without modifications (or with minor modifications).
I've added and designed an ADO.NET Entity Data Model (.edmx) and have generated the corresponding DDL Script (.edmx.sql). When I was using SQL Server 2008, all I had to do was connect to it via the Transact-SQL Editor toolbar and execute the SQL. When I try this method, however, it doesn't let me connect to the MySQL server, as it seems to be looking only for Microsoft SQL Servers. I have the latest version of Connector/Net, and can add the MySQL database as a Data Connection, but cannot execute the script I need. What steps are needed to use an Entity Framework model with my MySQL server?
I stumbled across this little property while editing my Data Model:
(This option was installed along side Connector/Net.)
After changing to SSDLToMySQL.tt, right-click and select Generate Database from Model... as you would normally. This will generate the .edmx.sql file, and should give you several errors (as .NET uses SQL Server to parse .sql files.) After generating the DDL script, I opened up MySQL Workbench and pasted the script in. You need to make sure that an appropriately-named schema already exists on the server, then run the script, and voila.