Upgrading to Snowsight from Classic Console¶
After your account is upgraded to Snowsight from Classic Console, follow this guide to learn more about Snowsight and adapt your key workflows.
For all the latest capabilities of Snowsight, see Snowsight: The Snowflake web interface. No major new features have been released for Classic Console since April, 2022.
Top questions after upgrading to Snowsight¶
Where are my old worksheets?¶
Snowsight doesn’t automatically copy the worksheets you had open in Classic Console.
If you don’t see the queries and worksheets that you were running in Classic Console, import your worksheets.
Note
Worksheets are not continually synced from Classic Console and Snowsight. If you create or make updates to a SQL worksheet in Snowsight, the changes are not reflected in Classic Console, and vice versa.
If you already imported your worksheets but you can’t find them, look for a folder named Import YYYY-MM-DD, where the date matches the date that you imported your worksheets.
To recreate the worksheet tabs you had open in Classic Console:
Sign in to Snowsight.
To return to Classic Console, in the navigation menu, select your user menu, and then select Classic Console.
Note the titles of your open worksheets.
Return to Snowsight.
Locate the worksheets that you had open and reopen them as tabs in Snowsight.
How do I load data from a file?¶
In Snowsight, you can load data from a local file or a file on a stage into an existing or new table.
While in a worksheet, you can use the object explorer to load data into an existing table.
You can also navigate to a database schema and create a table from a file.
See Loading data using the web interface for full details.
How do I preview data while writing SQL?¶
If you want to preview the contents of a data table while writing SQL or Snowpark Python in a worksheet, you can use the object explorer:
From a worksheet, select Databases in the object explorer. If you don’t see the object explorer, select Open sidebar.
Locate the database and schema that contain the table you want to preview, and then select the table.
In the table details section that appears, select (Preview table).
A data preview opens overlaying your worksheet, displaying a sample of data in the table.
You can also preview the column names and comments of a database table without previewing the data. See Refer to database object names in worksheets.
How do I see query details from my worksheet?¶
After you run a SQL query, when you view the Results, you can select the Query Details to see information about your query, such as the bytes scanned and the end time.
To review the queries that have been run in the worksheet, as well as the results for those queries, select (Query history).
For more details, see View query history. If you open the query details, you open the query profile for the query. See Review Query Profile.
Where is my account info?¶
To retrieve your account information, such as to copy the account identifier to sign in to SnowSQL, the Snowflake VS Code Extension, or another connection to Snowflake, you can use the account menu in Snowsight:
Open the account selector and review the list of accounts that you previously signed in to.
Locate the account for which you want to copy the account name.
Hover over the account to view additional details, and then select the copy icon to copy the account identifier in the format
orgname.account_name
to your clipboard.
Note
The account identifier is copied in the format orgname.account_name
, which is used for SQL commands and operations.
If you need to use the account identifier with a Snowflake driver (for example, JDBC or ODBC), you need to replace the period (.
) with
a hyphen (-
) so the identifier is formatted as orgname-account_name
.
You can also copy the account URL and review additional details, such as the name of your Snowflake organization, the edition of your account, and your Snowflake region.
Import worksheets from the Classic Console¶
You can import your SQL worksheets from the Classic Console to Snowsight from within Snowsight.
Import your SQL worksheets to make it easier to refer to queries and SQL statements that you’ve written in the past, without needing to switch to a different web interface and session.
Note
You can import your worksheets to Snowsight even if you can no longer access the Classic Console.
To import your SQL worksheets to Snowsight, do the following:
Sign in to Snowsight.
Select Projects » Worksheets.
Select the … more menu » Import Worksheets.
In the confirmation dialog, select Import.
Snowflake creates a folder named Import YYYY-MM-DD and places all worksheets from the Classic Console in that folder.
Important
Snowsight has a maximum worksheet size of 1MB. Worksheets larger than 1MB fail to import. See Troubleshoot issues with upgrading to Snowsight.
After importing worksheets¶
Worksheets are not synced between Snowsight and the Classic Console. If you make updates to a SQL worksheet in Snowsight, the changes are not reflected in the Classic Console, and vice versa.
Differences between Snowsight and Classic Console¶
There are a few differences between Snowsight and Classic Console. For the latest information about new functionality in Snowsight, see Snowflake weekly, Snowsight, and feature release notes.
Running SQL code in worksheets¶
Functionality |
Classic Console |
Snowsight |
More details |
---|---|---|---|
Build, test, and deploy Snowpark Python Worksheets. |
✔ |
||
Autocomplete for database objects and SQL functions in worksheets. |
✔ |
||
Organize worksheets with folders |
✔ |
||
Worksheets in a folder can have any role |
✔ |
||
Share worksheets and dashboards |
✔ |
||
Automatic contextual statistics for worksheet results |
✔ |
||
Visualize worksheet results with charts |
✔ |
||
Open worksheets in tabs |
✔ |
✔ |
|
Preview database objects while writing SQL. |
✔ |
✔ |
|
Download results in TSV or CSV file format. |
✔ |
✔ |
|
View Query History in worksheets |
✔ |
✔ |
|
Highlight statements in worksheets. |
✔ |
✔ |
|
See results where values are up to 5 million characters. |
✔ |
✔ |
|
Query results display raw data format. |
✔ |
✔ |
|
Run all queries in a worksheet. |
✔ |
✔ |
|
No limit on rows returned in worksheet results. |
✔ |
✔ |
|
Populate new worksheets with your default warehouse. |
✔ |
Soon |
Working with Snowflake¶
Functionality |
Classic Console |
Snowsight |
More details |
---|---|---|---|
Load a file into an existing table |
✔ |
✔ |
|
Load a file into a new table while inferring the schema for the file. |
✔ |
||
Upload files from a stage into a table. |
✔ |
✔ |
|
View files in a stage. |
✔ |
||
Add & edit named stages. |
✔ |
✔ |
|
See task graphs and run history. |
✔ |
||
Debug and rerun task graphs. |
✔ |
||
Monitor dynamic table graphs and refreshes. |
✔ |
||
Create a file format |
✔ |
✔ |
|
View role hierarchy. |
✔ |
||
Perform data governance tasks like masking data or adding policies and reviewing the governance of your data. |
✔ |
||
Access your billing usage statements. |
✔ |
||
Review usage and cost management for your account. |
✔ |
✔ |
Classic Console usage might be missing information. See Managing cost in Snowflake |
Monitor usage by tags and create budgets |
✔ |
||
Set up and manage replication. |
✔ |
Replicating databases and account objects across multiple accounts |
|
Monitor replication status. |
✔ |
✔ |
|
Access with an account name URL. |
✔ |
✔ |
|
Support for Private Connectivity. |
✔ |
✔ |
|
View Admin pages if secondary roles are active. |
✔ |
✔ |
|
Filter by end time and statement type in Query History. |
✔ |
✔ |
|
Resize the object explorer to view more details. |
✔ |
✔ |
|
Monitor warehouse usage to 10 minutes of granularity for the last day. |
✔ |
✔ |
|
Set up notifications for Resource Monitors. |
✔ |
✔ |
Troubleshoot issues with upgrading to Snowsight¶
The following scenarios can help you troubleshoot common issues that can occur when upgrading your workflow to Snowsight.
I can’t access Snowsight¶
You might need to update network policies and firewall rules to allow Snowflake URLs access to Snowsight.
See Preparing Private Connectivity for Snowsight in Snowflake Community and Signing in to Snowsight.
Some of my worksheets failed to import¶
Possible causes and resolutions:
- Cause:
The worksheet is too large. Snowsight has a maximum worksheet size of 1MB and worksheets larger than 1MB fail to import.
- Solution:
If you still have access to the Classic Console, consider whether you can split large worksheets into smaller worksheets that you can organize semantically in one folder, or do something similar.
- Cause:
The worksheet uses an unsupported file version.
- Solution:
If you still have access to the Classic Console, manually copy the contents of each worksheet that failed to import to a new worksheet in Snowsight.
- Cause:
The worksheet failed to import and can’t be opened or run.
- Solution:
If you still have access to the Classic Console, try to open the worksheet in Classic Console and copy the contents into a worksheet in Snowsight. If you cannot open the worksheet, contact Snowflake Support.
I don’t want my imported worksheets to be in a folder¶
To remove a worksheet from a folder, do the following:
In Snowsight, open the worksheet.
Select the worksheet name, and in the drop-down menu that appears, select Move to and choose the relevant option:
Select the name of an existing folder. The current parent folder for the worksheet is not an option to select.
Select + New Folder to create a folder and move the worksheet to that folder.
Select Remove from Folder to remove the worksheet from the folder.
The menu closes and the worksheet moves to the new location.
Note
You can’t move multiple worksheets at the same time. A worksheet can only be in one folder.
Usage information looks different in Snowsight¶
Usage information might be different in Snowsight compared with the Classic Console because the Classic Console has a 2 million row limitation in the query used to calculate usage.
Use Snowsight for accurate usage information. See Exploring overall cost.
Pages load slowly and sometimes I see a white screen¶
Your default warehouse is used to load some pages in Snowsight. If your warehouse is overloaded, pages like the database object explorer might load slowly or not at all.
You can see which warehouse is used for client-generated tasks in Query History. See Monitor query activity with Query History.