Soumettre la recherche
Mettre en ligne
Sql server guidelines
•
0 j'aime
•
4,601 vues
H
hingubhavik
Suivre
This book is so help full
Lire moins
Lire la suite
Technologie
Signaler
Partager
Signaler
Partager
1 sur 9
Télécharger maintenant
Télécharger pour lire hors ligne
Recommandé
test slideshare
test slideshare
nspp2
qazwsx
qazwsx
nspp2
df sd fsdf
df sd fsdf
nspp2
my test slideshare
my test slideshare
nspp2
mnbv
mnbv
nspp2
sample
sample
nspp2
sss
sss
nspp2
poiuyt
poiuyt
nspp2
Recommandé
test slideshare
test slideshare
nspp2
qazwsx
qazwsx
nspp2
df sd fsdf
df sd fsdf
nspp2
my test slideshare
my test slideshare
nspp2
mnbv
mnbv
nspp2
sample
sample
nspp2
sss
sss
nspp2
poiuyt
poiuyt
nspp2
wsxedcrfv
wsxedcrfv
nspp2
bnvbncvb
bnvbncvb
nspp2
New test slideshare file
New test slideshare file
nspp2
poiuyt
poiuyt
nspp2
poiuyt
poiuyt
nspp2
Test ppt file upload
Test ppt file upload
nspp2
new my test slideshare
new my test slideshare
nspp2
privet
privet
nspp2
test slideshare
test slideshare
nspp2
Worlds3 lect ch13
Worlds3 lect ch13
Jessie Kratzer
Prevenció de riscos laborals. PFI_PTT Vall d'hebron
Prevenció de riscos laborals. PFI_PTT Vall d'hebron
Elisabet Jansà
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
FIDO Alliance
Overview of Hyperledger Foundation
Overview of Hyperledger Foundation
Hyperleger Tokyo Meetup
ADP Passwordless Journey Case Study.pptx
ADP Passwordless Journey Case Study.pptx
FIDO Alliance
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
FIDO Alliance
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FIDO Alliance
Long journey of Ruby Standard library at RubyKaigi 2024
Long journey of Ruby Standard library at RubyKaigi 2024
Hiroshi SHIBATA
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Exakis Nelite
Easier, Faster, and More Powerful – Notes Document Properties Reimagined
Easier, Faster, and More Powerful – Notes Document Properties Reimagined
panagenda
Intro to Passkeys and the State of Passwordless.pptx
Intro to Passkeys and the State of Passwordless.pptx
FIDO Alliance
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
FIDO Alliance
Working together SRE & Platform Engineering
Working together SRE & Platform Engineering
Marcus Vechiato
Contenu connexe
En vedette
wsxedcrfv
wsxedcrfv
nspp2
bnvbncvb
bnvbncvb
nspp2
New test slideshare file
New test slideshare file
nspp2
poiuyt
poiuyt
nspp2
poiuyt
poiuyt
nspp2
Test ppt file upload
Test ppt file upload
nspp2
new my test slideshare
new my test slideshare
nspp2
privet
privet
nspp2
test slideshare
test slideshare
nspp2
Worlds3 lect ch13
Worlds3 lect ch13
Jessie Kratzer
Prevenció de riscos laborals. PFI_PTT Vall d'hebron
Prevenció de riscos laborals. PFI_PTT Vall d'hebron
Elisabet Jansà
En vedette
(11)
wsxedcrfv
wsxedcrfv
bnvbncvb
bnvbncvb
New test slideshare file
New test slideshare file
poiuyt
poiuyt
poiuyt
poiuyt
Test ppt file upload
Test ppt file upload
new my test slideshare
new my test slideshare
privet
privet
test slideshare
test slideshare
Worlds3 lect ch13
Worlds3 lect ch13
Prevenció de riscos laborals. PFI_PTT Vall d'hebron
Prevenció de riscos laborals. PFI_PTT Vall d'hebron
Dernier
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
FIDO Alliance
Overview of Hyperledger Foundation
Overview of Hyperledger Foundation
Hyperleger Tokyo Meetup
ADP Passwordless Journey Case Study.pptx
ADP Passwordless Journey Case Study.pptx
FIDO Alliance
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
FIDO Alliance
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FIDO Alliance
Long journey of Ruby Standard library at RubyKaigi 2024
Long journey of Ruby Standard library at RubyKaigi 2024
Hiroshi SHIBATA
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Exakis Nelite
Easier, Faster, and More Powerful – Notes Document Properties Reimagined
Easier, Faster, and More Powerful – Notes Document Properties Reimagined
panagenda
Intro to Passkeys and the State of Passwordless.pptx
Intro to Passkeys and the State of Passwordless.pptx
FIDO Alliance
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
FIDO Alliance
Working together SRE & Platform Engineering
Working together SRE & Platform Engineering
Marcus Vechiato
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
FIDO Alliance
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
FIDO Alliance
Your enemies use GenAI too - staying ahead of fraud with Neo4j
Your enemies use GenAI too - staying ahead of fraud with Neo4j
Neo4j
Intro in Product Management - Коротко про професію продакт менеджера
Intro in Product Management - Коротко про професію продакт менеджера
Mark Opanasiuk
ASRock Industrial FDO Solutions in Action for Industrial Edge AI _ Kenny at A...
ASRock Industrial FDO Solutions in Action for Industrial Edge AI _ Kenny at A...
FIDO Alliance
TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024
Stephen Perrenod
Introduction to FIDO Authentication and Passkeys.pptx
Introduction to FIDO Authentication and Passkeys.pptx
FIDO Alliance
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
UK Journal
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
marcuskenyatta275
Dernier
(20)
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Overview of Hyperledger Foundation
Overview of Hyperledger Foundation
ADP Passwordless Journey Case Study.pptx
ADP Passwordless Journey Case Study.pptx
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
Long journey of Ruby Standard library at RubyKaigi 2024
Long journey of Ruby Standard library at RubyKaigi 2024
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Easier, Faster, and More Powerful – Notes Document Properties Reimagined
Easier, Faster, and More Powerful – Notes Document Properties Reimagined
Intro to Passkeys and the State of Passwordless.pptx
Intro to Passkeys and the State of Passwordless.pptx
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
Working together SRE & Platform Engineering
Working together SRE & Platform Engineering
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Your enemies use GenAI too - staying ahead of fraud with Neo4j
Your enemies use GenAI too - staying ahead of fraud with Neo4j
Intro in Product Management - Коротко про професію продакт менеджера
Intro in Product Management - Коротко про професію продакт менеджера
ASRock Industrial FDO Solutions in Action for Industrial Edge AI _ Kenny at A...
ASRock Industrial FDO Solutions in Action for Industrial Edge AI _ Kenny at A...
TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024
Introduction to FIDO Authentication and Passkeys.pptx
Introduction to FIDO Authentication and Passkeys.pptx
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
Breaking Down the Flutterwave Scandal What You Need to Know.pdf
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
Sql server guidelines
1.
INDEX Guidelines for SQL SERVER 1 Important Guidelines for SQL Server………………………….. 2 Notice: All rights reserved worldwide. No part of this book may be reproduced or copied or translated in any form by any electronic or mechanical means (including photocopying, recording, or information storage and retrieval) without permission in writing from the publisher, except for reading and browsing via the World Wide Web. Users are not permitted to mount this file on any network servers. For more information send email to: pinal@sqlauthority.com 1 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
2.
Important Guidelines for SQL SERVER • Use "Pascal" notation for SQL server Objects Like Tables, Views, Stored Procedures. Also tables and views should have ending "s". Example: UserDetails Emails • If you have big subset of table group than it makes sense to give prefix for this table group. Prefix should be separated by _. Example: Page_ UserDetails Page_ Emails • Use following naming convention for Stored Procedure. sp<Application Name>_[<group name >_]<action type><table name or logical instance> Where action is: Get, Delete, Update, Write, Archive, Insert... i.e. verb Example: spApplicationName_GetUserDetails spApplicationName_UpdateEmails • Use following Naming pattern for triggers: TR_<TableName>_<action><description> Example: TR_Emails_LogEmailChanges TR_UserDetails_UpdateUserName • Indexes : IX_<tablename>_<columns separated by_> Example: IX_UserDetails_UserID • Primary Key : PK_<tablename> Example: PK_UserDetails PK_ Emails 2 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
3.
• Foreign Key : FK_<tablename_1>_<tablename_2> Example: FK_UserDetails_Emails • Default: DF_<table name>_<column name> Example: DF_ UserDetails _UserName • Normalize Database structure based on 3rd Normalization Form. Normalization is the process of designing a data model to efficiently store data in a database. (Read More Here) • Avoid use of SELECT * in SQL queries. Instead practice writing required column names after SELECT statement. Example: SELECT Username, Password FROM UserDetails • Avoid using temporary tables and derived tables as it uses more disks I/O. Instead use CTE (Common Table Expression); its scope is limited to the next statement in SQL query. (Read More Here) • Use SET NOCOUNT ON at the beginning of SQL Batches, Stored Procedures and Triggers. This improves the performance of Stored Procedure. (Read More Here) • Properly format SQL queries using indents. Example: Wrong Format SELECT Username, Password FROM UserDetails ud INNER JOIN Employee e ON e.EmpID = ud.UserID Example: Correct Format SELECT Username, Password FROM UserDetails ud INNER JOIN Employee e ON e.EmpID = ud.UserID 3 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
4.
• Practice writing Upper Case for all SQL keywords. Example: SELECT, UPDATE, INSERT, WHERE, INNER JOIN, AND, OR, LIKE. • There must be PRIMARY KEY in all the tables of database with column name ID. It is common practice to use Primary Key as IDENTITY column. • If “One Table” references “Another Table” than the column name used in reference should use the following rule : Column of Another Table : <OneTableName> ID Example: If User table references Employee table than the column name used in reference should be UserID where User is table name and ID primary column of User table and UserID is reference column of Employee table. • Columns with Default value constraint should not allow NULLs. • Practice using PRIMARY key in WHERE condition of UPDATE or DELETE statements as this will avoid error possibilities. • Always create stored procedure in same database where its relevant table exists otherwise it will reduce network performance. • Avoid server‐side Cursors as much as possible, instead use SELECT statement. If you need to use cursor then replace it with WHILE loop (or read next suggestion). • Instead of using LOOP to insert data from Table B to Table A, try to use SELECT statement with INSERT statement. (Read More Here) INSERT INTO Table A (column1, column2) SELECT column1, column2 FROM Table B WHERE …. 4 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
5.
• Avoid using spaces within the name of database objects; this may create issues with front‐end data access tools and applications. If you need spaces in your database object name then will accessing it surround the database object name with square brackets. Example: [Order Details] • Do not use reserved words for naming database objects, as that can lead to some unpredictable situations. (Read More Here) • Practice writing comments in stored procedures, triggers and SQL batches, whenever something is not very obvious, as it won’t impact the performance. • Do not use wild card characters at the beginning of word while search using LIKE keyword as it results in Index scan. • Indent code for better readability. (Example) • While using JOINs in your SQL query always prefix column name with the table name. (Example). If additionally require then prefix Table name with ServerName, DatabaseName, DatabaseOwner. (Example) • Default constraint must be defined at the column level. All other constraints must be defined at the table level. (Read More Here) • Avoid using rules of database objects instead use constraints. • Do not use the RECOMPILE option for Stored Procedure as it reduces the performance. • Always put the DECLARE statements at the starting of the code in the stored procedure. This will make the query optimizer to reuse query plans. (Example) • Put the SET statements in beginning (after DECLARE) before executing code in the stored procedure. (Example) • Use BEGIN…END blocks only when multiple statements are present within a conditional code segment. (Read More Here) 5 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
6.
• To express apostrophe within a string, nest single quotes (two single quotes). Example: SET @sExample = 'SQL''s Authority' • When working with branch conditions or complicated expressions, use parenthesis to increase readability. Example: IF ((SELECT 1 FROM TableName WHERE 1=2) ISNULL) • To mark single line as comment use (‐‐) before statement. To mark section of code as comment use (/*...*/). • Avoid the use of cross joins if possible. (Read More Here) • If there is no need of resultset then use syntax that doesn’t return a resultset. IF EXISTS (SELECT 1 FROM UserDetails WHERE UserID = 50) Rather than, IF EXISTS (SELECT COUNT (UserID) FROM UserDetails WHERE UserID = 50) • Use graphical execution plan in Query Analyzer or SHOWPLAN_TEXT or SHOWPLAN_ALL commands to analyze SQL queries. Your queries should do an “Index Seek” instead of an “Index Scan” or a “Table Scan”. (Read More Here) • Do not prefix stored procedure names with “SP_”, as “SP_” is reserved for system stored procedures. Example: SP<App Name>_ [<Group Name >_] <Action><table/logical instance> 6 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
7.
• Incorporate your frequently required, complicated joins and calculations into a view so that you don’t have to repeat those joins/calculations in all your queries. Instead, just select from the view. (Read More Here) • Do not query / manipulate the data directly in your front end application, instead create stored procedures, and let your applications to access stored procedure. • Avoid using ntext, text, and image data types in new development work. Use nvarchar (max), varchar (max), and varbinary (max) instead. • Do not store binary or image files (Binary Large Objects or BLOBs) inside the database. Instead, store the path to the binary or image file in the database and use that as a pointer to the actual file stored on a server. • Use the CHAR datatype for a non‐nullable column, as it will be the fixed length column, NULL value will also block the defined bytes. • Avoid using dynamic SQL statements. Dynamic SQL tends to be slower than static SQL, as SQL Server generate execution plan every time at runtime. • Minimize the use of Nulls. Because they incur more complexity in queries and updates. ISNULL and COALESCE functions are helpful in dealing with NULL values • Use Unicode datatypes, like NCHAR, NVARCHAR or NTEXT if it needed, as they use twice as much space as non‐Unicode datatypes. • Always use column list in INSERT statements of SQL queries. This will avoid problem when table structure changes. • Perform all referential integrity checks and data validations using constraints instead of triggers, as they are faster. Limit the use of triggers only for auditing, custom tasks, and validations that cannot be performed using constraints. • Always access tables in the same order in all stored procedure and triggers consistently. This will avoid deadlocks. (Read More Here) 7 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
8.
• Do not call functions repeatedly in stored procedures, triggers, functions and batches, instead call the function once and store the result in a variable, for later use. • With Begin and End Transaction always use global variable @@ERROR, immediately after data manipulation statements (INSERT/UPDATE/DELETE), so that if there is an Error the transaction can be rollback. • Excessive usage of GOTO can lead to hard‐to‐read and understand code. • Do not use column numbers in the ORDER BY clause; it will reduce the readability of SQL query. Example: Wrong Statement SELECT UserID, UserName, Password FROM UserDetails ORDER BY 2 Example: Correct Statement SELECT UserID, UserName, Password FROM UserDetails ORDER BY UserName • To avoid trips from application to SQL Server, we should retrive multiple resultset from single Stored Procedure instead of using output param. • The RETURN statement is meant for returning the execution status only, but not data. If you need to return data, use OUTPUT parameters. • If stored procedure always returns single row resultset, then consider returning the resultset using OUTPUT parameters instead of SELECT statement, as ADO handles OUTPUT parameters faster than resultsets returned by SELECT statements. • Effective indexes are one of the best ways to improve performance in a database application. • BULK INSERT command helps to import a data file into a database table or view in a user‐specified format. 8 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
9.
• Use Policy Management to make or define and enforce your own policies fro configuring and managing SQL Server across the enterprise, eg. Policy that Prefixes for stored procedures should be sp. • Use sparse columns to reduce the space requirements for null values. (Read More Here) • Use MERGE Statement to implement multiple DML operations instead of writing separate INSERT, UPDATE, DELETE statements. • When some particular records are retrieved frequently, apply Filtered Index to improve query performace, faster retrieval and reduce index maintenance costs. • Using the NOLOCK query optimizer hint is considered good practice in order to improve concurrency on a busy system. • EXCEPT or NOT EXIST clause can be used in place of LEFT JOIN or NOT IN for better peformance. Example: SELECT EmpNo, EmpName FROM EmployeeRecord WHERE Salary > 1000 AND Salary NOT IN (SELECT Salary FROM EmployeeRecord WHERE Salary > 2000); (Recomended) SELECT EmpNo, EmpName FROM EmployeeRecord WHERE Salery > 1000 EXCEPT SELECT EmpNo, EmpName FROM EmployeeRecord WHERE Salery > 2000 ORDER BY EmpName; 9 © Copyright 2000-2008 Pinal Dave. All Rights Reserved. SQLAuthority.com
Télécharger maintenant