I am trying to setup a PWM server but when I get to the Database Remote Connection I get the error below which appears to be the sql database unable to create a table. I have reviewed the logs and they state that the connection to the SQL database was successful. When I go to the SQL database and manually try to add a table it also fails.
unable to initialize database: exception initializing database service: 5051 ERROR_DB_UNAVAILABLE (error creating new table PWM_META: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'value TEXT )' at line 3)
Related
I am trying to create a SSAS tabular project where data source is memSQL DB. I am able to connect to the memSQL database from any SQL client tool using MySQL and/or MariaDb OBDC driver. But when I am using the same ODBC driver for a SSAS tabular project "using OLEDB provider for ODBC" then I am getting error like below:
Failed to retrieve data from DATE_DIM. Reason: ERROR [42000] [MySQL][ODBC 5.3(w) Driver][mysqld-5.5.58]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '*
FROM [DATE_DIM]' at line 1
ERROR [42000] [ma-3.0.9][5.5.58]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '*
FROM [DATE_DIM]' at line 1
I have used the connect string as "Provider=MSDASQL.1;Persist Security Info=False;DSN=memSQLDB". Test connection was successful, but when trying to preview any table's data it throws the above error to me.
Is it a compatibility issue between memSQL (5.5.58) version and MySQL ODBC driver (version-5.3) or MariaDB OBDC driver (version-3.0.9)?
Can anyone suggest if there is any compatible ODBC driver exists, which can work with SSAS ?
With this error message, it appears it's less about authenticating correctly and more about the SSAS tool issuing queries with syntax MemSQL doesn't understand. Can you grab the query(ies) and post them here? That'll help us migrate these to compatible syntax. Depending on how the tool works, you may not have control over changing these queries, and will need the tool vendor to patch the query syntax to be more compatible.
I have table input and insert/update component on my transformation. when i put all parameters for mysql8 and click on test, it was successful and able to connect. But when i browse table I am getting following error
**Unable to retrieve database information because of an error
Error getting views from schema [null]
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'HAVING TABLE_TYPE IN ('VIEW',null,null,null,null) ORDER BY TABLE_TYPE, TABLE_SCH' at line 1
I have latest mysql8.x jar in lib directory
this is not related with pentaho kettle, you have an error in your query
My SQL Server instance has a linked server to an Eloquence database. I need to select data from one of the tables in the Eloquence database, but I need to do it with SQL syntax, since I'm running the code from SQL Server Management Studio (SSMS).
One of the columns has a forward slash in its name (I didn't create it, nor do I have the authority to change it), which throws the following syntax error when I run my query:
OLE DB provider [ProviderName] for linked server [LinkedServerName] returned message "Prepare: Syntax error or access violation {Syntax error in item list (select).}".
OLE DB provider [ProviderName] for linked server [LinkedServerName] returned message "Prepare: Syntax error or access violation {Expression syntax error in aggregate function.}".
Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing the query "SELECT [TableName.ColumnName/WithForwardSlash] FROM [TableName]" for execution against OLE DB provider [ProviderName] for linked server [LinkedServerName].
I have tried:
Select * from.... throws the same error
Aliasing the column...throws the same error
Selecting the tablename.column name...throws the same error
Enclosing column name in brackets...throws the same error
Escaping the forward slash...throws 'Column not found' error
Note: I lack permissions to access the server directly, so I must query it via the linked server from SQL Server.
How can I select this column from SSMS via the linked server if it has a forward slash in it? How can I get around this error?
The SQL/R documentation: SQL/R A.03 Documentation
Hi I delete all publications and subscriptions on sql server 2008 . Then try to disabling publishing and distribution for reconfigure replication but have an error :
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Invalid object name 'dbo.sysmergesubscriptions'.
Changed database context to 'master'. (Microsoft SQL Server, Error: 208) Ho solve it ?
One thing you can do is: create that object by yourself. Most likely there would be more than one table/view missing. Just script those missing objects from another database (for example, develop environment) and create them in your production box.
I tried to move data aka ETL from one sql server to another as mentioned in a previous question - Copy data from one column into another column. Now, I get an error when I try to execute a query.
Query -
INSERT INTO [Target_server].[Target_DB1].[dbo].[Target_Table1](Target_Column1)
SELECT Source_Column222
FROM [Source_server].[Source_DB1].[dbo].[Source_Table1]
WHERE Source_Column1 = 'ID7162'
Error -
OLE DB provider "SQLNCLI" for linked server "MYLINKEDSERVER" returned message "Unspecified error".
OLE DB provider "SQLNCLI" for linked server "MYLINKEDSERVER" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "MYLINKEDSERVER". The provider supports the interface, but returns a failure code when it is used.
If your wrote that simple select is not working, the issue is in security configuration of the linked server and permissions which your user receive there.
Among this, when you execution your query, you don't need to specify the server name and DB name for both parts - source and target. You simply need to execute the query on target server and target database. In this case your query instead of
INSERT INTO [Target_server].[Target_DB1].[dbo].[Target_Table1](Target_Column1)
SELECT Source_Column222
FROM [Source_server].[Source_DB1].[dbo].[Source_Table1]
WHERE Source_Column1 = 'ID7162'
will looks like the following:
INSERT INTO [dbo].[Target_Table1](Target_Column1)
SELECT Source_Column222
FROM [Source_server].[Source_DB1].[dbo].[Source_Table1]
WHERE Source_Column1 = 'ID7162'
and you need your connection to be opened on server [Target_server] and database [Target_DB1]. Also the linked server security properties need to be checked on [Target_server] against the [Source_server].
If you are using loop back linked server (linked server refering to the same database in the same server) then refer the below mentioned link:
Transaction with loopback linked server - locking issues
If that is not the case, this is the solution provided by Microsoft.