Deleting Columns and Parameters

Deleting Columns and Parameters

A few types of objects appear in Schema View, even though you cannot delete them from Schema View. The examples are columns in a table and parameters of a stored procedure or function. Both these types of objects appear in Schema View so that you can better understand the table, procedure, or function without having to open its definition. However, each column and parameter is defined within the file that defines the entire table, procedure, or function. To delete these items, you must modify the definition for the table, procedure, or function.

To delete a column from a table


  1. If Schema View does not appear, open the View menu, point to Other Windows, and click Schema View.

  2. In Schema View, click the table that contains the column that you want to delete.

    - or -

    In Solution Explorer, click the file containing the table that contains the column that you want to delete.

  3. On the View menu, click Open.

    The file that contains the table definition opens in the Transact-SQL (T-SQL) editor.

  4. Modify the table definition to remove the column that you want to delete.

  5. On the File menu, click Save TableName.Table.sql.

    The changes are saved, and the table definition is updated in Schema View. The column that you deleted no longer appears.

To delete a parameter from a stored procedure or function


  1. If Schema View does not appear, open the View menu, point to Other Windows, and click Schema View.

  2. In Schema View, click the stored procedure or function that contains the parameter that you want to delete.

  3. On the View menu, click Open.

    The file that contains the procedure or function definition opens in the Transact-SQL (T-SQL) editor.

  4. Modify the procedure or function definition to remove the parameter that you want to delete.

  5. On the File menu, click SaveProcedureName.proc.sql or SaveFunctionName.function.sql.

    The changes are saved, and the procedure or function definition is updated in Schema View. The parameter that you deleted no longer appears.

Comments

Post a Comment

Popular posts from this blog

Google to FTS Syntax Cheat Sheet

Image
OPERATOR EXAMPLE DESCRIPTION   nut Searches for inflectional forms of the word nut crank arm crank AND arm Searches for documents containing inflectional forms of the words crank AND arm crank and ann. The keyword AND is optional. tire OR air Searches for documents containing inflectional forms of the words tire or air, “reflector bracket” Performs a phrase search for the phrase "reflector bracket". hardware -bracket Searches for documents containing inflectional forms of the word hardware but not the word bracket. +clamp Searches for the word darn') without generating inflectional forms. ~seat Searches for thesaurus forms of the word seat Assemb* Searches for words that begin with the prefix assemb . <washer nut> Searches for documents that contain the words washer in close proximity to the word nut
Read more

@@rowcount

@@rowcount is a global variable reports the number of affected rows in the most recently executed statement. Just like @@error you need to save it in a local variable if you want to use the value later, since @@rowcount is set after each statement. Since with SET you can only assign variable at a time, you must use SELECT if you need to save both @@error and @@rowcount into local variables: SELECT @err = @@error, @rowc = @@rowcount (For this reason, I prefer to always use SELECT for variable assignment, despite Microsoft's recommendations to use SET.) In T-SQL it is not an error if, for instance, an UPDATE statement did not affect any rows. But it can of course indicate an error in your application, as it could be an error if a SELECT returns more that one row. For these situations, you can check @@rowcount and raise an error and set a return value, if @@rowcount is not the expected value.
Read more

Sql Index

Image
Indexes help us retrieve data from tables quicker. Let's use an example to illustrate this point: Say we are interested in reading about how to grow peppers in a gardening book. Instead of reading the book from the beginning until we find a section on peppers, it is much quicker for us to go to the index section at the end of the book, locate which pages contain information on peppers, and then go to these pages directly. Going to the index first saves us time and is by far a more efficient method for locating the information we need. The same principle applies for retrieving data from a database table. Without an index, the database system reads through the entire table (this process is called a 'table scan') to locate the desired information. With the proper index in place, the database system can then first go through the index to find out where to retrieve the data, and then go to these locations directly to get the needed data. This is much faster.
Read more