Tim
Data Integration
Joined 5 years ago
User Profile
User Widgets
Contributions
Feature request: Let me connect a livemodel to a source with different table names
Let me connect a livemodel to a source with different table names The problem: I want to change my livemodel's connection to a different database. The new database has the same tables, but they belong to a different schema or have different names. As a result, I get a message "select a different database which includes all tables under one schema". So, I cannot change to the new database. Feature request: When I change the source database in an elasticube, I get an interface where I can map my datamodel's tables to the new names. I'd like the same interface for livemodels. Better yet, let me switch to the invalid connection, and then show the error only when I try to publish the model. Workarounds: A) In the old database, I could create the new table names. Then I can point my livemodel to the new names before switching connection. B) I could edit the .smodel file. C) Tech support suggested this: Use the REST API 2.0 PATCH /datamodels/{datamodelId}/schema/datasets/{datasetId}. I used it with the fillowing request body, then I could change the database. == { "database": "c00845810new", "schemaName": "dbo", "type": "live", "connection": { "oid": "99380074-a2bb-4cd7-8bc3-7a5d20152b82" }, "liveQuerySettings": { "timeout": 60000, "autoRefresh": false, "refreshRate": 30000, "resultLimit": 5000 } } Related discussion in support case 500Pk00000s1fVCIAY.27Views0likes1CommentGrafana preserve over reboot
I'm using Grafana to monitor my Sisense server. If I reboot the server, Grafana shows no data from before the reboot. Is there a way to preserve the data? (The reason I need this is that I want to monitor RAM use over a week, even if my server gets rebooted.)54Views0likes3CommentsLet designers see data models
My designer and data-designer users want to see data models shared with them. Currently, Sisense only shows you data models that you have edit permission on. The reason is that they want to see the relationships, tables, and fields. They want to do that to understand how they should use the data, fix issues in their dashboards, and confirm bugs in the data models. The visual data model page does that better than reading through a list of dimensions. Similar to this post: https://community.sisense.com/discussions/build_analytics/how-to-grant-view-only-access-on-the-elasticubes-to-designers/290928Views0likes1CommentUnload old cubes when under RAM pressure
Scenario: I have a server with many cubes. Half the cubes are used only once or twice a month. Sisense tech support said an elasticube will "keep its data in memory for fast query access". That means I have to provision the server with enough RAM to hold all cubes, even the rarely-used ones. Goals: I want to provision RAM for the expected level of use. E.g. I expect 60% of the cubes to be used each day. Also, if I have under-provisioned my server, I don't want it to crash (memory safe mode). Instead, I want rarely-used cubes to slow down until I provide more RAM. Solution: There is an existing feature that can help: I can set cubes to unload from RAM if unused for more than one day. I'd like a better way: When Sisense detects high RAM use, I want it to list cubes by last-queried date and unload the oldest ones. My way, the unload happens only when necessary, not daily. It "softens" the impact of insufficient RAM by making it slow down the least important cubes instead of crashing.19Views0likes0CommentsRe: Bug: Refresh schema all tables
Maybe it's just slow and lacking a progress indicator: On another attempt, I got the popup about changed fields after a few minutes. In my case, my query is slow, so maybe if it's doing "select top 1" that's taking a while. It'd be great to at least get an indicator show that it's still processing.48Views0likes0Comments