![]() Set the Update method to Append and then select Save settings. Select SalesLakehouse and confirm that the default New table is selected before selecting Next to continue. If necessary, set the authentication to Organizational account and then select Next.įrom the navigator, select the workspace used for this tutorial and expand to view all Lakehouse items. Select the FactOnlineSales query under the Data transformation query group and from the Home tab, select Add data destination and then select the Lakehouse option. ![]() In the bottom right corner of the Power Query Online editor, you can find the configured Data destination settings for your query where you can further customize or remove.īefore moving on to the next section of this tutorial, make sure to perform the same steps as you took earlier in this section to configure the Lakehouse as your data destination for each of the following queries. Type in the character(s) to use to mark the end of each statement.ĭisplays the Help on the SQL Query Scratch Pad.ĭisplays a label providing a description of the current SQL, whether there are pending changes (indicated by a leading *), and the name of the loaded SQL Query object or Filename.Setting the update method to Replace deletes all existing data and replaces it with the new data on each subsequent refresh. ![]() sql file.Ī source file browser displays on which you type in the new file name and click on the Save button to save the Query.Īny Query displayed in the Scratch Pad remains there until you either replace it with another Query from file or you close the model.Īpplies the SQL comment characters '-' to the beginning of each selected line or, if the selected lines are already commented, removes the comment characters. Saves the currently-displayed Query to a new. If you created the Query from scratch, a source file browser displays in which you type the new file name and click on the Save button to save the Query. Saves the currently-displayed Query to the file it came from. Saves this SQL statement to the SQL Query object it came from.Ĭreates a new SQL Query object and saves this statement to that object. Click on the file name and on the Open button to display the file contents in the Scratch Pad. Open the Database Builder window, then display the ' SQL Scratch Pad' tab.Įxecutes the SQL Query currently shown in the Scratch Pad.Ĭheck the 'Results' and 'Messages' tabs for the output of executing the Query.Ĭlears the SQL Query editor fields so that you can enter a new query.Ī source file browser displays, defaulted to display SQL files. A tabbed panel consisting of two pages, one to show the results of executing the Query and one to display any messages generated during the execution.An editor panel in which you create or import the SQL Queries - this panel provides SQL-based syntax highlighting for the current data model.A toolbar providing facilities for importing, saving, executing and clearing the SQL Queries.This database connection is shared between the 'SQL Scratch Pad', 'Database Compare' and 'Execute DDL' tabs of the Database Builder. The SQL Scratch Pad requires the Database Builder to have a valid ODBC connection to a live database. While you develop your data model you might want to execute and test ad-hoc SQL Queries for a DDL script, or run enquiries on the live database all of this is possible within the Enterprise Architect Database Builder interface. ![]() The SQL Scratch Pad provides a mechanism to develop and run ad-hoc SQL Queries against a live database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |