You are on page 1of 11

A view is a virtual table that consists of columns from one or more tables.

Though it is similar to a table, it is stored in the database. It is a query stored as an object. Hence, a view is an object that derives its data from one or more tables. These tables are referred to as base or underlying tables. Once you have defined a view, you can reference it like any other table in a database. A view serves as a security mechanism. This ensures that users are able to retrieve and modify only the data seen by them. Users cannot see or access the remaining data in the underlying tables. A view also serves as a mechanism to simplify query execution. Complex queries can be stored in the form as a view, and data from the view can be extracted using simple queries. A view consists of a SELECT statement that stored with a database. Because views are stored as part of the database, they can be managed independently of the applications that use them. A view behaves like a virtual table. Since you can code a view name anywhere you can code a table name. a view is sometimes called a viewed table. Views can be used to restrict the data that a user is allowed to access or to present data in a form that is easy for the user to understand. In some database users may be allowed to access data only through views

Stored Procedure A stored procedure is a set of one or more SQL statements that are stored together in database. To create a stored procedure use CREATE PROCEDURE statement. To use the stored procedure you send a request for it to be executed. When server recieves the request, it executes the stored procedure. Stored procedures assist in achieving a consistent implementation of logic across applications. The SQL statements and logic needed to perform a commonly performed task can be designed, coded, and tested once in a stored procedure. Each application needing to perform that task can then simply execute the stored procedure. Coding business logic into a single stored procedure also offers a single point of control for ensuring that business rules are correctly enforced. Stored procedures can also improve performance. Many tasks are implemented as a series of SQL statements. Conditional logic applied to the results of the first SQL statements determines which subsequent SQL statements are executed. If these SQL statements and conditional logic are written into a stored procedure, they become part of a single execution plan on the server. The results do not have to be returned to the client to have the conditional logic applied; all of the work is done on the server. There are some concepts of stored procedures

SIGN UP MEMBER LOGIN:


Password can't be empty.

Enter User ID or E

User Id can't be empty.

Ask your questio


Submit

Submit
Submit Submit Submit POST
TECHNOLOGIES

.NET 4.5 .NET Remoting Active Directory C# ADO.NET & Database AJAX Algorithms & AI Android Programming Articles ASP, JavaScript, CSS ASP.NET & Web Forms ASP.NET Controls ASP.NET MVC BizTalk Server C# Assemblies C# Language C# Tutorials C, C++, MFC Career Advice Chapters Cloud Computing COBOL.NET Coding Best Practices COM Interop Compact Framework Cryptography C# Crystal Reports C#

Current Affairs Custom Controls C# Databases & DBA Deployment Design & Architecture DirectX C# Enterprise Development Error Zone Exception Handling C# Expression Studio F# Files & IO Financial Applications Games Programming C# GDI+ & Graphics Hardware How do I HTML 5 Internet & Web iPhone/iPad Java Java and .NET JQuery JSP Leadership Learn .NET LINQ Message Queue Metro Style Apps Mobile & Embedded MonoDevelop Networking Office Development OOP/OOD Operating Systems PHP Printing in C# Products Project Management Reporting Services Robotics & Hardware Security in .NET SharePoint Silverlight Smart Devices Speech in C# SQL

SQL Server 2012 String, StringBuilder Team Foundation & VSS Testing Threading in C# Visual Basic .NET Visual C# Visual Studio .NET Visual Studio 11 Visual Studio 2010 VS LightSwitch 2011 WCF Web Forms Web Services WebForms Controls Windows 8 Windows Controls C# Windows Forms C# Windows Phone Windows PowerShell Windows Services Workflow Foundation WPF XAML XML in C# XNA

FORUMSBLOGS VIDEOSINTERVIEWSCERTIFICATIONSDOWNLOADSBOOKSLINKSNEWS

jQuery .animate() Method Part 1 Learn .NET in 60 days - Day 1 Crystal Report in Visual Studio 2010

C# Corner Search

ARTICLE

Views & Stored Procedure in SQL Server 2005


Posted by Raj Kumar in Articles | SQL Server 2012 on October 10, 2008 Tags: Attach, Attach Database, Configuraton Manager, Database, database engine, how to attach database, How to attach Database in SQLServer 2005, services, sql 2005, SQL Server 2005, SQL services, Stored Procedure, Views This article shows how to use Views and Stored Procedures in SQL Server 2005

inShare0

284428 21


Reader Level:

In this article I am going to describe how to use views in SQL Server 2005 database. A view is a virtual table that consists of columns from one or more tables. Though it is similar to a table, it is stored in the database. It is a query stored as an object. Hence, a view is an object that derives its data from one or more tables. These tables are referred to as base or underlying tables. Once you have defined a view, you can reference it like any other table in a database.

A view serves as a security mechanism. This ensures that users are able to retrieve and modify only the data seen by them. Users cannot see or access the remaining data in the underlying tables. A view also serves as a mechanism to simplify query execution. Complex queries can be stored in the form as a view, and data from the view can be extracted using simple queries. A view consists of a SELECT statement that stored with a database. Because views are stored as part of the database, they can be managed independently of the applications that use them. A view behaves like a virtual table. Since you can code a view name anywhere you can code a table name. a view is sometimes called a viewed table. Views can be used to restrict the data that a user is allowed to access or to present data in a form that is easy for the user to understand. In some database users may be allowed to access data only through views.

In this example I am using my Vendor database which has these fields. Here is my database:

Figure 1. Create View : USE [Vendor] GO /****** Object: View [dbo].[VendorData] Script Date: 08/07/2008 23:27:34 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO ALTER VIEW [dbo].[VendorData] AS SELECT VendorId,VendorFName,VendorLName,VendorCity,VendorState,VendorCountry,PostedDate, VendorDescription FROM Vendor You can execute your view like this, in this example VendorData is my View name. Use Vendor GO SELECT * FROM VendorData WHERE VendorState = 'PA' ORDER BY PostedDate GO

Output:

Figure 2. This is it. Stored Procedure A stored procedure is a set of one or more SQL statements that are stored together in database. To create a stored procedure use CREATE PROCEDURE statement. To use the stored procedure you send a request for it to be executed. When server recieves the request, it executes the stored procedure. Stored procedures assist in achieving a consistent implementation of logic across applications. The SQL statements and logic needed to perform a commonly performed task can be designed, coded, and tested once in a stored procedure. Each application needing to perform that task can then simply execute the stored procedure. Coding business logic into a single stored procedure also offers a single point of control for ensuring that business rules are correctly enforced. Stored procedures can also improve performance. Many tasks are implemented as a series of SQL statements. Conditional logic applied to the results of the first SQL statements determines which subsequent SQL statements are executed. If these SQL statements and conditional logic are written into a stored procedure, they become part of a single execution plan on the server. The results do not have to be returned to the client to have the conditional logic applied; all of the work is done on the server. There are some concepts of stored procedures. A stored procedure is one or more SQL statements that have been compiled and stored with database. A stored procedure can be started by application code on the client. Stored procedure can improve database performance because the SQL statements in each procedure are only compiled and optimized the first time they are executed. In sontrast SQL statements that are sent from a client to the server have to be compiled and optimized everytime ther are executed. In addition to SELECT statement, a stored procedure can contain other SQL statements such as INSERT, UPDATE, DELETE. It also contain control-of-flow language.

A trigger is a special type of procedure that executes when rows are inserted, updated or deleted from table. A user defined function(UDF) is a special type of procedure that can return a value or a table

ALTER TABLE dbo.Presidents ADD CONSTRAINT President_unique CHECK (YearsInOffice >= 0 AND YearsInOffice < 13) ALTER TABLE dbo.Person ADD CONSTRAINT PK_Person PRIMARY KEY NONCLUSTERED (PersonID);

To create a composite primary key on an existing table:


ALTER TABLE dbo.Person ADD CONSTRAINT PK_Person PRIMARY KEY CLUSTERED (PersonID, DOB);

For an existing table, there are two places that can be used to specify the primary key. The first is inline to the column. Using this method, you cannot create a composite primary key:
CREATE TABLE [dbo].[Person]( PersonID [int] IDENTITY(1,1) CONSTRAINT PK_Person PRIMARY KEY NONCLUSTERED NOT NULL, FirstName VARCHAR(50) NULL )

The second way is to specify the primary key after the creation of the table, this will enable you to create a composite primary key. Keep in mind that in order to use a column in the primary key, the field must not be nullable.
CREATE TABLE [dbo].[Person]( PersonID [int] IDENTITY(1,1) NOT NULL, FirstName VARCHAR(50) NOT NULL CONSTRAINT PK_Person PRIMARY KEY NONCLUSTERED (PersonID, FirstName) )

Note: The CONSTRAINT PK_Name portion of the code above is optional, however if not specified a constraint name will be auto generated.

Prerequisites The primary key column(s) must be unique for each row. If you are altering an existing table and trying to add a primary key to a column that is not unique, you will receive the error:

The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name dbo.Person and the index name PK_Person. The duplicate key value is (1). The The script script for for renaming renaming any object any (table, column sp etc) : :
execute sp_RENAME 'TableName.[OldColumnName]' , '[NewColumnName]', 'COLUMN'

sp_RENAME '[OldTableName]' , '[NewTableName]'

This article demonstrates two examples of renaming database object. 1. Renaming database table column to new name. 2. Renaming database table to new name.
3. EXEC sp_rename 'Stu_Table', 'Stu_Table_10'

External Entities may be a (a) source of input data only (b) source of input data or destination of results (c) destination of results only (d) repository of data 5.1.5 By an external entity we mean a (a) unit outside the system being designed which can be controlled by an analyst (b) unit outside the system whose behavior is independent of the system being designed (c) a unit external to the system being designed (d) a unit which is not part of a DFD Data cannot flow from an external entity to an external entity because (a) it will get corrupted (b) it is not allowed in DFD

(c) an external entity has no mechanism to read or write (d) both are outside the context of the system A context diagram (a) describes the context of a system (b) is a DFD which gives an overview of the system (c) is a detailed description of a system (d) is not used in drawing a detailed DFD 5.2.2 A context diagram is used (a) as the first step in developing a detailed DFD of a system (b) in systems analysis of very complex systems (c) as an aid to system design (d) as an aid to programmers 5.2.3 By levelling a DFD we mean (a) splitting it into different levels (b) make its structure uniform (c) expanding a process into one with more sub-processes giving more detail (d) summarizing a DFD to specify only the essentials *When Are Fact-Finding Techniques Used? Fact-finding used throughout database application lifecycle. Crucial to early stages including database planning, system definition, and requirements collection and analysis stages. Enables developer to learn about the terminology, problems, opportunities, constraints, requirements, and priorities of the organisation and the users of the system. Fact-Finding Techniques Database developer normally uses several fact-finding techniques during a single database project including: _ examining documentation, _ interviewing, _ observing organisation in operation, _ research, _ questionnaires. Examining Documentation Can be useful: _ to gain some insight as to how the need for a database arose; _ to identify the part of the organization associated with the problem;

_ to understand the current system. Interviewing Most commonly used, and normally most useful, fact-finding technique. Enables collection of information from individuals face-to-face. Objectives include finding out facts, verifying facts, clarifying facts, generating enthusiasm, getting end-user involved, identifying requirements, and gathering ideas and opinions. Interviewing Two types of interviews: unstructured and structured. Open-ended questions allow interviewee to respond in any way that seems appropriate. Closed-ended questions restrict answers to either specific choices or short, direct responses. Questionnaires Conduct surveys through questionnaires special-purpose documents that allow facts to be gathered from a large number of people while maintaining some control over their responses. Two types of questions, namely free format and fixed-format.

*A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform. An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost. A good SRS defines how an application will interact with system hardware, other programs and human users in a wide variety of real-world situations. Parameters such as operating speed, response time, availability, portability, maintainability, footprint, security and speed of recovery from adverse events are evaluated
*Diff b/w commit and rollback.

You might also like