Databases
StackOverflow2013
Postsdbo
PORe-runnable SQL Server Scripts
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORe-runnable SQL Server Scripts
    primarykey
    data
    text
    <p>What are the best practices for ensuring that your SQL can be run repeatedly without receiving errors on subsequent runs?</p> <p>e.g.</p> <ul> <li>checking that tables don't already exist before creating them </li> <li>checking that columns don't already exist before creating or renaming </li> <li>transactions with rollback on error</li> <li>If you drop tables that exist before creating them anew, drop their dependencies first too, and don't forget to recreate them after</li> <li>Using CREATE OR ALTER PROCEDURE instead of CREATE PROCEDURE or ALTER PROCEDURE if your flavor of SQL supports it</li> <li>Maintain an internal versioning scheme, so the same SQL just doesn't get run twice in the first place. This way you always know where you're at by looking at the version number.</li> <li><p>Export the existing data to INSERT statements and completely recreate the entire DB from scratch.</p></li> <li><p>dropping tables before creating them (not the safest thing ever, but will work in a pinch if you know what you're doing)</p></li> </ul> <p>edit: I was looking for something like this:</p> <pre><code>IF EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[foo]') AND OBJECTPROPERTY(object_id, N'IsUserTable') = 1 ) DROP TABLE foo </code></pre> <p>Do others use statements like this or something better?</p> <p>edit: I like Jhonny's suggestion:</p> <pre><code>IF OBJECT_ID('table_name') IS NOT NULL DROP TABLE table_name </code></pre> <p>I do this for adding columns:</p> <pre><code>IF NOT EXISTS ( SELECT * FROM SYSCOLUMNS sc WHERE EXISTS ( SELECT id FROM [dbo].[sysobjects] WHERE NAME LIKE 'TableName' AND sc.id = id ) AND sc.name = 'ColumnName' ) ALTER TABLE [dbo].[TableName] ADD [ColumnName] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJason Marcell
    1. USJason Marcell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORe-runnable SQL Server Scripts
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORe-runnable SQL Server Scripts
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORe-runnable SQL Server Scripts
      1. USNathan Koop
      1. VTFavorite
    1. COI'd remove dropping tables before creating them. You wouldn't want to drop tables with data in!
      singulars
      1. PORe-runnable SQL Server Scripts
      1. USMitch Wheat
    2. COAgreed, it's probably not the safest thing to do. I was just trying to get the ball rolling on the kinds of responses I was looking for.
      singulars
      1. PORe-runnable SQL Server Scripts
      1. USJason Marcell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload