go to post Andreas Schneider · Sep 16 I've been running my tests on an IRIS docker image. I have now switched to a Windows VM, just to see if this works better (IRIS for Windows (x86-64) 2024.2 (Build 247U) Tue Jul 16 2024 09:57:03 EDT).I have also extended my attempts. Like the first time, I used a gateway connection to an IRIS 2024.2 instance (on a docker image), the second GATEWAY connection goes to an MS SQL Server 2022. Unfortunately, the THROUGH command still does not work for me. However, the 'old' CREATE FOREIGN TABLE works through the previously created FOREIGN SERVER. This indicates that the configuration of the FOREIGN SERVER and its connection is correct. THROUGH to a IRIS 2024.2 Server works not CREATE FOREIGN TABLE to a IRIS 2024.2Server works THROUGH to a MS SQL Server 2022 Server works not CREATE FOREIGN TABLE to a MS SQL Server 2022 Server works But now the error is a different one ;-) I have no idea how the THROUGH command works...
go to post Andreas Schneider · Aug 17 SQL DATA LENS is now available from the Microsoft Store for easy installation: check it out here
go to post Andreas Schneider · Jun 1 I've tried it on Windows 11. With your information I've searched again and found (my) problem now! First: Thanks for that! What was the problem? I've installed IRIS using the custom option and selected to install ALL items on the hard disk. Then I cannot find the odbc driver dll in the following folder:All the other drivers are there: dotnet, java and so on.Now I've tried a client installation on a fresh Windows... the folders are still empty. BUT the ODBC Data Source Administrator shows the 2024.1 IRIS ODBC driver! Again: The CLIENT install works!The files are located here:The puzzle is solved. Thanks to all of you!Andreas
go to post Andreas Schneider · Jun 1 Thanks for the link! I know this link, but unfortunately it seems that only real?! customers can access it! I've got this message: Personally, I have never bought a Caché\IRIS licence, but have worked for companies that have such access. At home ;-) I only use the Community Edition. So the message could be plausible.Andreas
go to post Andreas Schneider · Apr 28 The last element is the namespace not the schema, please see here: Using the JDBC Driver | Using Java with InterSystems Software | InterSystems IRIS Data Platform 2024.1 jdbc:Cache://<host>:<port>/<namespace> Andreas
go to post Andreas Schneider · Apr 28 You can change the default schema (= what is used if no schema is specified in the query) here:However, if you use the schema extensively in your data model to structure the model, you should always use the schema in the query. Working with fully qualified object names is simply best practice and avoids misunderstandings. It seems better not to rely on such things like a default schema because it can changed (or diff from server to server). This becomes even more important when the same object names exist in different schemas.jm2cAndreas
go to post Andreas Schneider · Sep 18, 2023 SQL DATA LENS release 3.15 is out! Download here for free The new AI features available in the world are great for a small development company. It allows me to focus on integrating new features into SQL DATA LENS and let an AI bot generate some promotional videos. What do you think about this: or what do you think about that?
go to post Andreas Schneider · Mar 12, 2023 I'm not sure what the reason is but with 2023.1 there are some errors in %SQL_Diag.Result when loading data from my datasets. The errors are different from 2022.3.After changing some columns in my data model from NOT NULLABLE to NULLABLE the errors are gone and the performance with IRIS 2023.1 is the same as with 2022.3
go to post Andreas Schneider · Mar 12, 2023 I've upgraded my small test project https://github.com/andreas5588/openflights_dataset from 2022.2.0.368.0 to IRIS 2023.1.0.207.0 and I've discovered that the SQL execution time was much slower than expected.Within this project I load the data using "LOAD DATA FROM FILE" sql statement and it looks like that this is taking up the time.A "docker-compose build" with IRIS 2022.2.0.368.0 took about about 17 seconds on my machine, the same with IRIS 2023.1.0.207.0 took 300 seconds!The image with IRIS 2022.2.0.368.0 is 2.87Gb and the image file with IRIS 2023.1.0.207.0 image is 3.21Gb.This is the only change I've made https://github.com/andreas5588/openflights_datasetAny idea whats going on?Andreas
go to post Andreas Schneider · Dec 26, 2022 That looks strange. If you execute the query via JDBC the error ist the same. A CAST to the same datatype as provided from Config.ConfigFile works: SELECT CAST(ID AS VARCHAR(512)), CAST(CPFName AS VARCHAR(255)), CAST(Comments AS VARCHAR(4096)), CAST(Name AS VARCHAR(64)), CAST(Product AS VARCHAR(64)), CAST(SectionHeader AS VARCHAR(255)), CAST(Version AS VARCHAR(7)) FROM Config.ConfigFile
go to post Andreas Schneider · Dec 25, 2022 As a test i created an iris instance in a docker container. Nicely the problem doesn't exist there. Maybe I'll just try a reinstallation of IRIS under win10 the next days...
go to post Andreas Schneider · Aug 14, 2022 Hi! Unfortunately there is no way to UPDATE the %DESCRIPTION information on a table or column with SQL.But you can add these information while CREATEing a table like this: or this way for a column:Please see CREATE TABLE | InterSystems SQL Reference | InterSystems IRIS Data Platform 2022.1 for more details. By default the %DESCRIPTION information is projected to the Remarks column via JDBC: As you can see the text comes from the %DESCRIPTION property: This works also for the columns.This is from JDBC:This is from INFORMATION_SCHEMA.COLUMNS:Andreas
go to post Andreas Schneider · Aug 14, 2022 By the way, why is SQL not available for selection in the codesnippets?isn't SQL a first class citizen on the iris dataplatform?? ;-)
go to post Andreas Schneider · Aug 14, 2022 I tried it with a small example: I could not find any problem. Generally this variant works from my point of view.Exceute a "PURGE CACHED QUERIES" and retry, maybe this will help.Andreas
go to post Andreas Schneider · Apr 9, 2022 @Vitaliy.Serdtsev thanks for this great idea! In the past i have also missed this feature myself from time to time. So far the pain has not been great enough ;-) But now I know that other users also miss this feature...
go to post Andreas Schneider · Feb 11, 2022 Freut mich wenn ich helfen konnte. Gerne mit DU ;-) Andreas
go to post Andreas Schneider · Feb 9, 2022 The column parameter has MAXLEN 229: parameter As %Library.String(MAXLEN = 229) [ SqlColumnNumber = 6 ]; that is why the insert fails
go to post Andreas Schneider · Feb 9, 2022 The rejected insert has 239 chars in the fifth column. The working insert has 186 chars. So check your table defintion. How are the columns defined?
go to post Andreas Schneider · Feb 9, 2022 Are you shure that you match the column list? An INSERT without a column list is not very stable about changes.
go to post Andreas Schneider · Jan 9, 2022 I think it is always a good idea to avoid reserved words in the data model. Even if the quick import of a CSV tempts to take it not so exactly. Especially because messages from IRIS don't always point exactly to the cause of the problem ... or it leads to problems later. This saves unnecessary troubleshooting. https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...happy loading! ;-) Andreas