I created SPSS modeler flow in Watson studio. I need to schedule it runs daily, but modeler flows can not be scheduled as job in Watson studio.
What do you suggest to do ?
Maybe thru a notebook which runs the modeler and that can be scheduled afterwards?
If so, pls advise the Phyton code to run a SPSS modeler built in Watson studio
Thanks in advance
#massi Scheduling is currently not available in SPSS modeler flow in Watson Studio.
Related
I am using Power BI Desktop and try to create a live connection (no standard import) to an Analysis Services tabular model in Visual Studio 2017.
In Power BI Desktop, I press Get Data -> Analysis Services.
I use Power BI Desktop with the same credentials as in the Analysis Services model in Visual Studio.
I use Microsoft SQL Server 2017 (RTM).
What am I missing?
Try this check list:
Try to access your cube with SQL Server Management Studio
if not ok -> there is a problem with credential or server. If your computer and the server are not in the same domain it could be an issue
from power bi desktop try import data rather than live connection
can you connect to your model with data tools for visual studio?
The point here is to exclude some configuration to focus on the real problem.
let me know.
I faced this problem today in my work and I make the following and it's working for me
process the whole analysis service project from visual studio, not just the cube or one dimensional
type the name of the database in the Database(optional) and click ok.
tell me if this not working with you
good luck
I am currently using Visual Studio 2015 (Community Version) and I am trying to automate a data flow task that moves an SQL input into a Flat File output.
I have tested that the task works manually however I cannot find anywhere how to automate the process, any help would be greatly appreciated as I am very new to this, Thanks
You need to schedule a process that triggers your code/DTS. You can use SQL Server Agent, Windows Scheduler or other scheduler software.
If you are working with SSIS and your process is a DTS (I'm guessin it is because you mentioned "Data Flow Task"), then you can execute it using the command line with the dtexec program.
If you are using C#, Visual Basic or another programming language in Visual Studio, make sure to compile it as a Console Application so it generates an .exe file.
Finally schedule your program execution (either dtexec or the call to the .exe) in your scheduler software, with a custom timing (for example everyday at 7am, just weekends, etc.). Make sure to monitor the results afterwards!
I've been exploring UIPath community edition and have come across that the Main window and most of its activities are just like a Visual Studio Workflow. Is it right to say that UIPath is built upon Workflow Foundation of .NET Framework? I'm just trying to reconcile them both in my head now.
Yes that is correct. You can use many functions and methods within UiPath that come from .net. If you press crt+space when you are typing code you will get a list of all functions and methods available. You can even invoke code and execute previously saved Microsoft code.
Not only it's build using Microsoft Workflow Foundation but you could also extend UiPath using Activities build in very similar fashion to WFF. So if you know how to create NativeActivity for example, you already know how to extend UiPath.
Note that the development in UiPath is not really code-extensive, knowledge of .NET is a plus but not mandatory.
Anybody has any idea how to do custom reporting in Team Services without help of Power BI. I can get the test cases and defect data from Excel Add-In but this is not useful as we have to write the Team Services Query all the time.
There are also some lightweight charts and dashboards you can use for the report, refer to this link for details: Dashboards and reports overview.
And beside the Power BI, Analytics service is added to VSTS but it is in preview for now. If you are interested in it, you can contact the Analytics service team: vsts-analytics-supp#microsoft.com.
What is the difference between Query Studio and Report Studio in Cognos?
Could anyone explain me in detail?
Thanks in advance.
Query studio is lightweight add hoc web report writer that allows semi-power users to build ad-hoc reports via the Cognos web portal using prepared data content published to the web portal. Users can sort/filter change font size, do some grouping and aggregation... and save their reports. How ever this report writer is lightweight in that you don't have strong capabilities over presentation format and layout.... in comes report studio which is the enterprise report development tool which can develop pixel perfect reports that have a high degree of interactivity complex condition/conditional layout processing etc... Report studio can edit query studio reports as well. So sometimes users save their Query studio reports but ask for developers to tweak them to get desired appearance/functionality. Both application generate XML files that are stored in the Cognos Repository.