There are two key differences between columns created in the SQL Report Builder and those created using the Data Warehouse Manager: one is the dependency on update cycles, the other is how columns are saved in your account.
Columns are not dependent on update cycles, so you no longer have to wait for one to complete before you can iterate on your column. If you make a mistake, all it’ll take is a few keystrokes to correct it - no more waiting for two updates to wrap up before you can get back to work.
It’s important to note that the columns you ‘create’ using the SQL editor aren’t saved to your Data Warehouse. You’ll always have access to the query containing the column, but if you want to use the column in more than one report, you’ll have to recreate it in the query for each report. This means that columns created using the SQL editor can’t be used in the traditional Report Builder.
Columns are dependent on update cycles, so a full cycle must complete before they can be edited. These columns are saved to the Data Warehouse Manager and can be used in the traditional Report Builder or SQL Report Builder.