SQL Keywords and Descriptions

Code Description ABORT Aborts the current transaction ALTER TABLE Modifies table properties ALTER USER Modifies user account information BEGIN WORK Begins a transaction CLOSE Close a cursor CLUSTER Gives storage clustering advice to the backend COMMIT Commits the current transaction COPY Copies data between files and tables CREATE AGGREGATE Defines a new aggregate function CREATE DATABASE Creates a new database CREATE FUNCTION Defines a new function CREATE INDEX Constructs a secondary index CREATE LANGUAGE Defines a new language for functions CREATE OPERATOR Defines a new user operator CREATE RULE Defines a new rule CREATE SEQUENCE Creates a new sequence number generator CREATE TABLE Creates a new table CREATE TABLE AS Creates a new table CREATE TRIGGER Creates a new trigger CREATE TYPE Defines a new base data type CREATE USER Creates account information for a new user CREATE VIEW Constructs a virtual table DECLARE Defines a cursor for table access DELETE Deletes rows from a table DROP AGGREGATE Removes the definition of an aggregate function DROP DATABASE Destroys an existing database DROP FUNCTION Removes a user-defined C function DROP INDEX Removes an index from a database DROP LANGUAGE Removes a user-defined procedural language DROP OPERATOR Removes an operator from the database DROP RULE Removes an existing rule from the database DROP SEQUENCE Removes an existing sequence DROP TABLE Removes existing tables from a database DROP TRIGGER Removes the definition of a trigger DROP TYPE Removes a user-defined type from the system catalogs DROP USER Removes an user account information DROP VIEW Removes an existing view from a database EXPLAIN Shows statement execution details FETCH Gets rows using a cursor GRANT Grants access privilege to a user, a group or all users INSERT Inserts new rows into a table LISTEN Listen for notification on a notify condition LOAD Dynamically loads an object file LOCK Explicit lock of a table inside a transaction MOVE Moves cursor position NOTIFY Signals all frontends and backends listening on a notify condition RESET Restores run-time parameters for session to default values REVOKE Revokes access privilege from a user, a group or all users. ROLLBACK Aborts the current transaction SELECT Retrieve rows from a table or view SELECT INTO Create a new table from an existing table or view SET Set run-time parameters for session SHOW Shows run-time parameters for session UNLISTEN Stop listening for notification UPDATE Replaces values of columns in a table

Topics in Interview Point of View

1. Framework(CLR,Class Library)
2. Assemblies (Private Assemblies and shared Assemblies,Satellite Assemblies)
3. Reflection
4. Oops(Abstarct Classes,Interfaces,Overloading,Overriding,Encapsulation,Inheritance,..)
5. XML Intro,XML Schema
6. Authentication and Authorisation
7. Delegate
8. Web.Config,Machine Config
9. Managed code and Unmanaged Code and managed data
10. Interoperability
11. Application domain
12. Webservices
13. ADO.net (DataAdapter,DataReader,Dataset,Dataview,DataTable,SqlCommand,SqlConnection)
14. State Management (ViewState,Session,Appication,Querystring,Cookies)
15. Exception, Error handling
16. Caching
17. Tracing (Page Trace)
18. Validation controls(Required,Range,Compare,Custom,Validation Summary)
19. Display Controls (Data Grid,Data List,Reader,Calender,Hidden,Dropdown List,List Box,Radio Button List,Check Box List)
20. Style Sheet(CSS)
21. Global.asax
22. User Controls and Custom controls
23. Frame Set

Session State Modes

Storage location

InProc - session kept as live objects in web server (aspnet_wp.exe)

StateServer - session serialized and stored in memory in a separate process aspnet_state.exe). State Server can run on another machine

SQLServer - session serialized and stored in SQL server


Performance

InProc - Fastest, but the more session data, the more memory is consumed on the web server, and that can affect performance.

StateServer - When storing data of basic types (e.g. string, integer, etc), in one test environment it's 15% slower than InProc. However, the cost of serialization/deserialization can affect performance if you're storing lots of objects. You have to do performance testing for your own scenario.

SQLServer - When storing data of basic types (e.g. string, integer, etc), in one test environment it's 25% slower than InProc. Same warning about serialization as in StateServer.