16Salesforce is a CRM, delivered as SaaS | subscription based and centrally ,backup and recovery | data administn func (data
unc (data policies, procedures n become primary key of this relation. If identifier is assigned then the identifier
hosted| accessed by thin client web browser| force.com is a creates employee standards; planning, data conflict resolutn, managing the info repository,
facing applications and tools delivered using Paas |Provides computing internal marketing of DA concepts)| traditional dba func (analyzing n
platform and solution stack as service| consumer controls s/w dev, config designing db, selecting db n soft tools, installing/ upgrading dbms, data
settings| provider provides n/w, servers, storage| cloud computing means backup n recovery, data security, privacy n integrity, improving query
SaaS, utility computing, web services, Paas, MSP, service commerce processing perform, tuning db perform)| data warehouse admin (emphasis
platform, internet integration| SaaS- UI upgrades, no req latest version, use of integratn n coordinatn of metadata; support decision support apps, manage
any whr, time| Paas-add,customize field names.Additional app for integration| dw growth, establish service level agreements), client/server app security (
Iaas- more space, secure| products Sales-salescloud ,data.com, Service – keep static html files in protected directories on server & std db access
Service cloud,desk.com, Marketing-could,pardot, Community-cloud,chatter, controls, dynamic files- user authenticatn| Open Source db mgmt.:
analytics, platformApps- SalesForce1, Force.com, Heroku, AppExchange| alternative to oracle, ss, less expensive.|Threats to Data
force.com-integration google app,micro office| google integration- send email Security(human,s/w,h/w failures), theft, loss of privacy and confidentiality,
msg, service calls, share documents, calendar| Microsoft integration- outlook, loss of data integrity and availability. | Dynamic Page: session security, sssl
excel, vlookup formulas pivot table charts| Data aggregation- for encryption, restrict no of users and open ports, remove unwanted pgm) |
campaigns,leads, accounts, cases , dashboards, reports, vertical respose- track W3C Platform for privacy protect|(views/ db soft security features
the response back| Salesforce app dev UI, busi logic, data model| Declarative subschemas, integrity controls-domains( set allowable values),
approach- Page layout, record types, formula fields, validation rules, assertions(enforce db connec), triggers(prevent inappropriate action , write
workflows&approvals, custom objects&fields, relationships| programmatic log files) , autho rules, user defined procdedures, encryptn, authenticatn
approach- visualforce pages & components, Apex controllers & triggers, schemes, backup n checkpointin)|Authorization Matrix : Subjects, Objects,
Meta bulk rest API| objects = tables | global unique id | text or auto number| Actions, Contsraints|User defined procedures : Customize authorization
create an object you get CRUD UI, mobile app, rest api, rich metadata, index proc| Passwords: 8 char, alphanumeric, no complete words or person info,
search|17Column- field, table-object|objects std&custom, design of data frequent change. | SOX (requires compny to audit the access to sensitive data,
model is key for success app| structure for storing data, interact with data- designed to ensure integrity-it change mgmt., logical access to dta, it operatns|
force.com|text,picklist,dependent picklist, Date, Checkbox, IT Chg Mgmt- proc which authorizes changes to opertnal sys,db.|Logical
currency,longtextfield| relation between two objects|Data access concepts– Access to Data: - personnel & physical access control.|DB recovery -
object-level,field-level,record-level—orgwide defaults,role heri, sharing Backup Faci( Periodic Backup, Cold backup – db shut down , hot backup
rules, manual sharing|Report Formats—tabular reports – simple – some part of db shutdown and backed up at a given time), Journalizing
report,summary—grouped report eg sales,date, matrix—diff dimensions, Facil: Audit Trail of transc and db updates(Transc log, Db Change Log
joined reports—multiple report types and views| Dashboard—20 – Images taken – before image, after image(before modify after modify),
components,3 components on home tab, summarized views| Checkpoint facilities: no new transactions till sync b/w db and transc , allows
tables,charts,gauges,metrics.18Programmatic approach—SOAP UI- processing from shrter period.| Recovery and restart Procedures: Disk
CRUD records,maintain password, perform searches, Rest API ease of mirroring ( move b/w identical copies), Restore/Rerun, (commit or abort all
integration and dev. Bulk-API based on rest principle, optimized for loading transaction changes), Bckwd(Rollback) & Fwd Recovery| ACID –
and deleting large data sets| Programmatic approach Metadata API- Atomic(cannot be subdivide) , Consistent( constraint always c wrt to transc),
Retrieve,deploy, create,update or delete customizations. Migrate changes Isolated(Db changes nt revealed during trans), Durable( DB changes are
testing to prod. Metadata model not data itself| Apex—create web and email perm)| Concurrency Control(maintain data integrity for simultaneous user
services. Validations in multiple objects. Create complex business processes access)| CC techniques: Serializability( one after other), Locking
not supported by workflow. Create custom transactional logic. Attach custom Mechanisms(Shared – Read but no update, Exclusive lock –No access
logic to another operation| Objects – API data types are field types,in the UI, permitted, when preparing update(esp))|Two phase locking protocol:
API fieldproperties: autonumber, create, delete, filter, group, idloopup, query, growing phase and shrinking phase)| Versioning- Alternate to locking,
search, sort, update|primitivedatatypes–base64, Boolean,byte,date, dateTime, system rejects update in case of conflict, use of rollback and commit| Data
double, int, string, time|difference between relationtype include data deletion, Dictionary – document data elem of db., System Catalog – sys created db
record ownership, security and page layouts – master detail (1 to m), m to m, ,describes all db objects| Information Repository – metadata| Information
lookup (1 to m)| master detail 1-m – parent child relationship, master deleted Repository Dictionary System(IRDS) : s/w manage access to Information
child deleted. Detail record inherits sharing and security settings. Relationship repo. | repository system architecture (informant model, repository engine-
field is required in page layout. Custom object is detail side| lookup – no effect objects, relatnships, extensible types, version n config mgmt., repository db)
on deletion and security, not automatically required. When you define a db | performance tuning (dbms installatn, memory n storage space usage, i/o
lookup relationship, data from one object can appear as custom related list on contentn, cpu usage, app tuning) |Ensure data availability (h/w failures, data
page layouts for the other object| Custom objects – Custom flags is true. loss, human error, n/w probs, maintain downtime)2Good data name – related
Create using UI, metadata WSDL, force.com IDE. Suffix _c. Appear on UI to business, meaningful, unique, readable, composed, repeatable, written
name field must be populated| Relationship - _r| salesforce obj query standard| Term – phrase, fact – association between two terms| guildlines –
language- powerful query strings in following environment – queryString concise desc,sysreq, acc of diagrams, achieved by concensus| Entities type –
parameter in query() call, apex statements, visualforce controllers, eclipse| row in table, entity type – collection of entities| relationship instance – link
Salesforce object search language—search() same as before| Apex- salesforce between entities, relationship type – category of relationship| attributes –
platform language, cloud based, =java, webservices,batch,triggers| IDE – properties|business rules–declarative, precise, atomic, consistent, expressible,
force.com, mavens mate, force CLI. Apex is tightly integrated with distinct,business-oriented| entity - a person or noun, entity type- collection of
db,persistence layer. Database objects are called sobjects. DML-manipulate, entities that share common properties, entity instance – single occurrence of
SOQL – query, SOSL – search| sobject is generic abstract type.1Database--‐ a entity type| Strong entity – independently exist, weak entity – exist with
organized collection of logically related data|Data- stored rep of meaningful strong| Classification of attributes – req vs optional, simple vs composite,
objects, Structured-numbers,unstructured-images| Information- increase single-valued vs multivalued, stored vs derived, identifier| Composite – An
knowledge | metadata – data about data| disadv of fileprocessing – data attribute that has meaningful components parts | Candidate keys – minimal
dependence, duplication of data, limited data sharing, lengthy development combinations of attributes satisfies the requirement for being an identifier|
times, excessive program maintenance| Data redundancy issues Naming attributes – unique,singular| defining attri – included & not included,
inconsistencies, data integrity| DBMS – s/w system that is used to create, why imp, aliasas, source of value, req vs optional, min & max, relation with
maintain and provide controlled access to user db| adv db – data other attri | Relation type – modeled as line between entity types. Relationship
independence, no data redundancy, consistency, sharing, productivity, instance – between specific entity instances. Associativity entity –
quality, accessibility, responsiveness, maintanence, decision, support| costs combination of relationship and entity| Degree of relationship – unary, binary,
and risk—new personnel,complex,costs,backup,conflict| Data models- ternary| Cardinality Constraints – the number of instances of one entity that
enterprise data model—high level entities and relationship for the org, proj can or must be associated with each instance of other entity| Max Cardinality
data model – matching data structure in db detailed view| Entities- noun form, – max instances of one entity that is asso with other entity| When should a
relationship – between them. Relational db – tables and keys| components of relationship with attributes instead be an asso entity? All relationship should
db—CASE,repo,DBMS,db,app prog, UI,db admin,sys dev,users| Enterprise be many. Asso entity should have meaning independently. Asso has primary
data model—first step in db dev process. Scope and content. High level key and other attributes. It should participate in other relationships. Ternary
view.ERD.desc entity types. Busi rules.relation between entities| Approaches relationship should be converted to associated entities| the date completed
to DB SDLC system development life cycle,prototyping. SDLC – attribute pertains specifically to the emp completion of a course, it is an
detailed,timeoriented, long dev cycle. Proto – RAD, conceptual data attribute of a relationship| Associative entity also considered to be an entity
modelling,initial proto,repeat implementation. SDLC – planning purpose – in its own right| Modeling time dependent data has become more important
understanding, deliverable – request for study, db activity – enterprise due to regulation such as HIPPA and Sarbanes-Oxley.4Data integrity –
modelling and early concentual modelling. Analysis – req analysis,functional Mechanisms for implementing business rules that maintain integrity of
specification, integrated data model. Logical design – info req elicitation & manipulated data| data manipulation – SQL operations for retrieving and
structure, detailed design spec, logical db design. Physical design – dev tech, modifying data. A relation is named 2 dimension table of data | Tables to
tech purchase, physical db design. Implementation— qualify as relations – unique name, atomic, row unique, attri uniqe name,
programming,documentation,db implementation. Maintenance – order irrelevant| All relations should be in first normal form| relation = entity
monitor,periodic audit,db maintenance| Db Schema – External : views, subset types, rows = entity instances, columns = attributes| foreign key – enable
of conceptual schema, conceptual – er models, internal: logical, physical dependent relation to refer to its parent relation| Domain constraints –
structures| Project – a planned undertaking of related activities| evolution of allowable format size and value for an attribute, Entity constraint – valid data,
db—reduced maintenance,desire to manage more complex data types, ease of not null, primary key, Referential Integrity – consistency, foreign key
data access, need for more powerful decision platforms. Flat included| restrict – donot allow to delete of “primary” side if related row exists
files,hierarchical,network,relational,OO,objectrelational,datawarehousing| in foreign side, cascade – delete foreign side if primary side is
Range of db app – personal db, 2 tier n tier, ERP&DW| ERP – integrate all deleted.Transforming ER diagram – Composite attributes – use only simple
enterprise functions | DW – Integrated decision support system derived from components, multivalued attribute – new relation, weak entities - becomes a
various operational db.11Data nd DB administration: ineffective data separate relation with a foreign key from the superior entity. Primary key is
adminis (multiple data definitn, misssin data elements, inapropr data sources of weak + superior entity | Mapping binary relationships 1-1 – primary key of
n timing, poor respose time, damaged data, unauthorized access)| Data the mandatory side becomes a foreign key on the optional side. 1-m primary
Administration : responsible for overall management of data resources , key on one side becomes foreign key on many side. M-m – create a new
including maintaining coporate wide standards. Database Administration : relation with primary key of both relation as composite primary key.| mapping
resp for physical db design and tech issue like security , db performance associative entities – identifier not assigned – the primary key of both tables
is primary key and other keys are foreign keys| Mapping unary – 1-m
recursive foreign key in the same relation. M-m one for an associative relation
in which the primary key has two attributes, both taken from the primary key
of the entity| mapping ternary – one relation for each entity and one for
associative entity. Associative entity has foreign key to each entity in the
relationship| Data Normalization – tool to validate and improve the logical
design so that it satisfies certain constraints. The process of decomposing
relations with anomalies to produce smaller relations| Insertion anomaly –
adding new rows forces user to create duplicate data, deletion anomaly –
deleting rows may cause loss of data that was required, modification –
changing of data in row forces to change rows. A table should not pertain to
more than one entity type| Functional dependency – The value of one attribute
determines the value of another attribute. Candidate key – a minimal unique
identifier. No partial functional dependency – 2nf, no transitive dependency
– 3NF| view integration – combining entities from multiple er diagram into
common relations. Synonms – diff name same meaning, homo – same name
diff meanings, transitive dependency – not be there after merging| Enterprise
keys – primary keys that are unique to whole db, object ID’s.14Object
Persistence: objects capacity to maintain its state b/w application execution
sessions| Object Relational Mapping (ORM): structural relationships b/w
object oriented and relational represe of data , to permit use of Relational
DBfor persistence.| Object Relational Impedence Mismatch: diff in
approach of OO to application design and relational model for db design.(
Elements – nature & granularity od data types, structural relationships,
Defining the identity of objects./instances, architectural styles)|Object
Identity : property of object diff from others based on existence.| Accesor
Method : A method providing objects access to state of another object.|
Object Persistence using relational DB Call Level API – SQL query
handcoded passed as parameter to driver. (JDBC, ODBC) Adv( Low
overhead , highest level of control over details of DB connect), Disadv(
detailed code, reuse not possible , SQL code not automatically generated, no
transparent persistence)|SQL Query Mapping Frameworks – developers
operate at high level of abstraction My batis.,Adv( Direct access of DBMS
capability through SQL, Code less than Call level API, Database access code
easier to manage.) , Disadv( More overhead than call level API , need
understanding of DBMS and DB schema, SQL code nt automatic generated,
no transparent persistence.)| ORM Frameworks: transparent persistence ,
declarative mapping schema between OO and database relations/tables.
(JDO), Adv(highest transparent persistence, no need to detailed
understanding of DBMS, enable true object oriented design), Disadv(most
overhead, complex cases , legacy db leads to difficulty. |Proprietary
Frameworks: integrates data access queries into prog languages (LINQ)|
ORM Responsibilties: Providing layer of abstraction between OO
apllications and database schema, Generating SQL Code for Db access,
Centralizing code related to DB access, Query language, concurrency control.
| ORM DB Performance Management: Fetching Strategy – model
specifying when and how an ORM framework retrives persistent objects to
the run time memory during navigation. , N+1 select problem : performance
problem due to too many select statements generated by ORM framework|
HQL: Different approaches in handling join , implicit associate join ,ordinary
join in from clause , fetch join in from clause, theta style join in where clause
9DATA Warehousing: Data warehouse(subjected oriented, integrated, time
variant, non updatable, Data Mart : DW limited in scope. need (integrated
company wide view of high qual data, separatn operational and info sys),
issues wid cmpny wide view (inconsistent data & key struct, missin data
elements, free vs structured form) | Data warehousing arch. Independent
data mart – separate etl for each dm complex due to multiple dms.
Dependent dm and operatnal data store – ODS Provide curr data , only
single etl , dependent DM loaded from EDW. Logical dm and real time data
warehousing- ODS and DW same, real time ETL data , dms logical view of
dw | Event = database action that results from a transaction.| Transient Oper
data – dataoverwritten |periodic warehouse data – data inserted| Derived
Data - ease of use 4 decision support, fast response, customized data, data
mining, adhoc query support nd its characteristics (detailed, periodic,
aggregate, distributed)| Dimensional model (contains descriptn bout subjects
of business. Denormalized, Good 4 adhoc queries bad 4 transactions) | Fact
table (quantitative n factual data and creates n-ary relatn b/w dimentiona)|
Dimension table shud hav surrogate keys (non-intelligent and non-
business, keep track of non key attributes for a given prod key, simpler
shorter, same length format for all key)| Granularity (transactional-finer,
aggregated, finer grains _ better market analysis, finer grain more dimension
tables)| Size of fact table (multiply no of possible values 4 each dimension
table)| Mutliple Fact table (performance, facts for diff combo for dimesions),
Factless Fact ( only foreignkey data from dimension)|Conformed
Dimesions( associated with multiple fact)| Normalizing dimension tables
(multivalued dimensions-facts qualified by set f values 4 same business
object, involves creatn f separate assosiative entity), dimension hierarchy
(natural fixed depth hierarchy-provide levels f aggregatn 4 users wanting
summary info)|Slowly changing dimensions (replace old data, or new
column-multivalued, or new row wid characteristics at time f change). | 10
rules 4 dimensional model(use atomic tables, single process fact tables,
consistent grain, disallow null keys, decode dimen table, use surrogate keys,
conform dimensions, balance req wid actual data)| Columnar databases :
Issue of big data , optimizestorage for sum data of few columns, data
compression eg. Sysbase , vertica.| NoSQL : not only sql, deals with unstru
data . Apache Cassandra. Couch DB.| UI Metadata: identify – subj of dm, fact
and dimesions, then indicate how data derived from edw including derivation
rules, how data is derived from ods inclu derive rules, then identify avail
reports, predefined queries, data analy techniques and responsible people.|
OLAP – graphical tools, mutlidimesional view of data and allows to analyze
data. Types Relational OLAP(ROLAP) – traditional relational representation
, Multidimesional OLAP – Cube structure| Data mining goals (explanatory-
explain obs events, exploratory-explore 4 new relatn, cnfmatory- cnfm hypo)|
business performance mgmt. (allows manager to monitor key activities to
achieve organization goals)10Data quality and Integration: Data
Governance – high level organizational groups and processes overseeing data
stewardship.| Data steward : responsible for ensuring org applictns properly
support org data quality goals.|Requiment for Data Governance- senior
mgmt. and business units sponsorship , data steward mger to support train
coordinate data stewards, data stewards for diff busi units, subjects,
governance committee for data mgmt. guidelines & standards| Sarbanes-
oxley (compliance by law sets data and meta data quality standards)| Purpose
of data quality (minimize it risk, timely business decisions, regulatory
compliance, expand cust base)| Characteristics of data qual. (unique,
accurate, consistent, cmplt, timeliness, conformance, currency refrential
intgrity)| Causes of poor qual data (external data resources, redundant data
storage, data entry, lack of organizational commitment)| Steps in Data qual
improve - business buyin (executive sponsorship, build business case, return
on investment, avoidance of cost, avoid opportunity loss), data qual audit
(statiscaly profile data files, document set of values for all fields, analyze data
patterns, specialized data profiling tools, verify whether control n business
rules r enforced), data stewardship pgm (oversight of same, manage data
sub area, oversee (data definitn, product of data, use of data)), improve data
capture process(automate data entry, manual entry from preset options,
trained operators, goo ui design principles, immediate data validation for
entered data) apply modern data mgmt. principles nd tech(pattern
matching, fuzzy, expert sys),sound data modeling & db design. total quality
mgmt principles (defect prevent, cont improvement, use of enterprise data
std, strong foundatn of measurement), balanced focus ( customer, product
service), | Master data mgmt: disciplines, tech, methods to ensure meaning
and quality of reference data within , across subject areas. Characteristics –
Identity Registry ( master data in source system , registry provides appl with
locn), Integration Hub- (data changes broadcast to central service).
Persistent ( central golden record maintained , all apps have access, data
duplication , requires app to push data). | Data Integration – create unified
view of busi data. Requires CDC Change data Capture: which data have
changed since the previous data integration| Techniques for data integration
: Consolidation - ETL, Data Federation : - Enterprise Information
Integration EII ( virtual view of data w/o creating a centralized database, Data
Propogation – Enterprise Application Integration (EAI) and Enterprise Data
Replication(EDR)- duplicate data with near real time data. | Reconciled Data
Layer: ( Typical operational Data – transient not normalized , restricted in
scope , sometimes poor quality, after ETL - detailed , historical, normalized,
comprehensive, timely, quality controlled)| data reconciliation (extract
(select, join, normalize, integrate), scrub/cleanse, transform, load)| Static
Extract – Capturing snapshot of the source data at a point in time,
Incremental Extract : capturing changes that have occurred since last static
extract| Steps in Data reconciliation : Capture/extract, Scrub/ Cleanse,
Trasnform , Load). | Refresh Mode :bulk overwriting of target data at
intervals, Update Mode : only changes in source data written| Record Level
Transformation Functions: Selection , Joining, Normalization ,
Aggregation.12DD: 1 logical db spread physically across all loctns. |
Decentralized DB : Coll of Independent DB on unconnected comps.|
Reasons of distributed db (business unit autonomy n distribution, data
sharing, data communication reliability n costs, multiple app vendors, db
recovery, transactn n analytic processing), easy to manage, difficult to
enforce.| Homogenous DDB – same DBMS/node – Autonomous : indepen
DBMS, Non autonomous – central DBMS| Heter DDB - diff DBMS/Node
– systems, gateways, prfrd by indepen org|System- FULL DBMS
Functionality( all distributed DB functions), partial DBMS -
federated(supports local db for unique requests) – loose(db has own schema)
and tight integration ( local db use common schema). Unfederated( requires
central access. objectives (location transparency – user doesn’t know
location of data, local autonomy – local site can operate , and have own
security , logging), significant trade-offs (synchronous –all copies in
database always in sync, good data integrity, high cost, slow response time,
asynchronous – opp to synchro), |Advantages: (increase reliability/availi of
data, local control, modular growth, low commu cost, fast response 4 certain
query), |Disadv( s/w cost n complexity, processing overhead, data integrity
exposure, slower resp 4 cert que)| Options 4 distributing db (data replicatn,
horizontal, vertical partitioning, combinatn of above)| Data Replication
Adv(Reliable, Fast respo, avoid complicated distributed trans integrity,
reduce network traffic), Disadv(More storage, additional time for update,
omplexity)| Types of Data Replication – Push( updated site send change to
others), Pull(receiving site control when updates will be done- Snapshot
replication , near real time replication)| issues of data repli (data timeliness,
dbms capabilities, performance implicatns, n/w heterogeneity, n/w commu
capabi)| Horizon/ vertical partition (adv- data stored close to where it is
used, local access optimiz, only relevant data avail, union across parttions)
(disadv- accessing data across partitn i.e. inconsistent spped, no data
replicatn(backup vulnrability)). | distribution db strategies (centralized db
distributed access, repliatn wid periodic snapshot update, replicatn wid near
real time sync of updates, partitioned 1 logical db, partitioned independent
nonintegrated). factors of distributed strategy (organizational forces,
frequency n locality of refer, tech capabi, growth n expansion needs, cost of
mnging complex tech, need of reliability)Reliability increases, expandibility
increase, comm overhead increases, managibility & data consistency
decreases| Func of d DBMS : Single logical db provide, replicate Data,
Scalable, allow for different DBMS application codes at diff nodes, locate
data in distribu data dictionary , translate between nodes with diff local dbms,
security concurrency, deadlock , data consistency.| Ddbms transparency obj
(location, replicatn, failure- all or no transact process, transaction manager-
logs data before and after image, concurrency control). |concurrency control
(concurrency transparency- appearance of serial transact although
simultaneous, timestamping- globally unique to each transaction, alternate
to locks)| Query optimi (for multi site join, must decide where 2 access data
n how 2 proceed; 3 steps: query decompositn, data localizatn, global optimiz)
unit of work (remote, distributed, distributed request), Semi Join : only joining
attribute of query sent from one site to another.| Evolution of Dist DBMS:
Unit of work( all trans steps), Remote Unit of Work ( SQL statements origin
in one loc , executed as single unit of work on 1 remote DBMS., Distributed
UOW( Different ststements different remote sites), Distributed Request(
Single SQL – reference to tables in >1 remote sites)Object Oriented13 center
around objects n classes, involves inheritance, Encapsulates data n behavior,
benefits (tackle challen probs, improved comm bw user analy n developer, ^
consistency in analysis n design, robustness, reusability f analy, design n prog
results, explicitly represents commonality amng sys)| OO vs ER , Class(entity
type), Object( Entity Instance) ,Association( Relationship), behavior vs no
behavior)| Represented using UML & crows foot notation.| UML : graphical
notations for busi model. Specifying., designin, implementing s/w sys
artifacts.| Class Diagram : most relevant UML Diag for DB modeling| Class
:weldefined role in app domain wid state – attribute type & value, behavior
– object act & react n identity- object has unique identity. .( Entity can be
Tangible, Concept or Event,Artifact of Design proc.| Object: Particular
Instance of Class (has both behavior + attributes)| Operation: Function
provided by all instance of class. Types ( Constructor – creates new instance
of class, Query – access state of object, Update –Alters the state of an object,
Scope – class operation) Operations implement the object behaviour|
Encapsulation : Hiding internal implement details. | Associations: relation
among object classes. Association Role : role of object in assoc. Multiplicity
: no of objects in an assoc. Represented as: 0..1,0..*,1..1,1..*. |Association
class has attributed f own, participates in relatnshps wid oder clas). Abstract
Class : no direct instance possible, subclass may have, Concrete Class :
direct instance possible.| Class-scope attri (specifies value common to entire
class =is default value)| Abstract Operation :Defines form or protocol of oper
, but nt implementation| Method : Implementation of oper..| Polymorphism:
Same operation may apply diff class in diff ways.| Overriding : Replace
method in superclass by more specific implementation in subclass.| Multiple
Classification : An object is an instance of more than one class.| Multiple
Inheritance ; A class inherits features from one more than one superclass.
Aggregation(a part-of relatnshp bw component obj n aggregate obj),
composition(stonger frm f aggregatn- obj belongs 2 only 1 whole obj n exist
only as a part f one whole obj), Recursive aggre(composition where
component obj is instance f same cls as aggregate obj)5Physical db design
purpose – translate the logical description of data into tech specs for storing
and retrieving data. Goal – provide performance and ensure database
integrity, security and reliability. Decisions – attribute data types, phy record
descriptions, file org, indexes and db arch, query optimizations. Field –
smallest unit of application data recognized by system software. Field design
– choosing datatype, coding, compression, encryption, controlling data
integrity. Varchar2, char, clob, number, date, blob. Field data integrity –
default value, range control, null value control, referential integrity. Missing
data – estimate of missing values, list, ignore missing values, triggers can be
used to perform this. Denormalization can increase the chances of errors
inconsistences and anomalies, force re programming, proper query design and
optimizations.| Partitioning – horizontal – rows are partitioned 3 types key
range partitioning, hash partitioning, composite partitioning. Vertical –
columns, primary key must be repeated. Advantages – efficiency, local
optimization , security, recovery, uptime, load balancing. Inconsistent,
complexity, space| rules of indexing – use larger tables, index primary keys,
index search, order by and group by, value >100 <30.3Enhanced ER model
– extended er model| subtype – a subgrouping of entities in an entity type
that has attribute distinct from others| generalization – the process of defining
more general entity type from a set of more specialized entity. Bottom up.
Specialization – top down| total specialization – two lines, disjointness –
whether it has to be of 2 types simultaneously| subtype discriminator – An
attribute of the supertype whose values determine the target subtype. Disjoint
– A simple attribute with alternative values to indicate the possible subtypes.
Overlapping – a composite attribute whose subparts pertain to different
subtypes. Entity cluster- grouped in a single abstract entity type|.8Client –
workstation, server – computer, database server| Presentation logic – input,
output, UI, processing logic – business rules, data management – procedures,
functions, programs, storage logic – data storage – dbms activiry| Application
partitioning – placing portions of the application code in the diff locations
after its written. Adv – improved performance, interportability, balance
workload. Fat client – client has processing and presentation logic, thin client
– client has only presentation logic, distributed – client and server has
processing logic shared| 3 tier n tier processing logic will be on application
server| 2 tier client workstation is responsible for presentation, data
processing, business logic| server performs all data storage, access and
processing. Typically called as db server| API routine an application uses to
perform procedure on the computer OS– ODBC,JDBC, ADO.net|
Steps(Database via Middleware)- identify and register db driver, open
connection to db, execute query, process results, repeat 3-4 times, close the
db connection | Web application Components : DB Server(hosts DBMS eg.
SQL server ), WEB server( receives , responds to browser requests using http
eg apache, information IS), Application Server(s/w buiding blocks for
creating dynamic websites eg asp.net, apache), web browser (client program
send/receives web pages eg IE)|HTML – markup language for webpages,
Standard Generalized Markup Language(SGML) – markup lang standard,
Extensible Markup L(XML) – allows customized tages, XHTML – XML
complaint HTML, Javascript and VBScript – enable interactivity in HTML,
Cascading style sheets(CSS) – control appearance of web elem in HTML,
XST & XSLT – XMS style sheet and transformation to HTML|3Tier
Considerations : Stored Procedures : Code logic embedded in dbms,
improve performance, but proprietary, Transactions : involve many db
updates ,all succeed or none should occur, DB Connections : open connection
is resource intensive,use of connection pooling|3 Tier Advantage:
Scalability,Tech flexibility, long term cost redu, better match to business sys,
improved customer service, competitive advantage, reduced risk| Cloud
Computing Char: on demand, broad n/w access, resource pooling,rapid
elasticity, measured service| XML – text based markup lang, use elements,
tags,attributes. Include Document type declarations , XML Schemas,
comments , entity ref. Revolutionize internet data exchange. Document
Structure Declarations(DSD),XML Schema(XSD) replace DTD for
validating XML Docs structure| XSD – lang for determining XML Databases|
Storing XML Data : relational database by shredding XMl Document, XML
Doc in large field(BLOB, CLOB), XML Docs in special XML Columns, in
native XML Database(non relational)|Retrieving XML data: Xpath – set of
XML tech supporting Xquery Dev & locating data in XML docs. XQuery –
XM transformational Lnaguage allows query on relational db and XML
data.Extensible Stylesheet Language Transformation (XSLT): transform
complex XML Docs & create HTML pages from XML. Single XML doc can
be translated to HTML and WAP/WML| Web services – XML standards,
define protocols for automatic communication between s/w prog over web.|
UDDI Universal Description , Discovery & Integration : standard for
create and distribute webpages. | Web services description
language(WSDL): XML based for desc Web Services and Speciying its
public interface.| Simple Object Access Protocol ( SOAP): XML based
protocol for sending messages b/w applications over web. Loosely coupled,
highly interoperable components. Flexibility and shorter development time.
6SQL: Structured Query Language |RDBMS- DBMS dat manages data as
colection of tables in wich al rlshnps r reprsntd by common values in reltd tables.
|Purpose f SQL Std-Specify syntax/semantics 4 data definition n manipulation; defin
data strctrs n basic operations;enable portablty f DB definition n appn modules;
specify minimal(level1) n complete(level 2) stds; alow 4 later growth/enhancmnt 2
std; |benefits-reduced trainin costs; productivity; appn portablty n longevity; reduced
dependence on single vendor; cross-system communication. Catalog-set f schemas
dat constitute description of DB. Schema-structure dat contains descr f objects
created by user(base tables,views, constrnts).Data Defition Language(DDL)-
comands dat define DB incldn creatin,alterin n dropin tables n establshn
constraints.DML(manipulation)-comands 2 maintain n query DB.DCL(Control)-
comands 2 control DB, incldn administerin privileges n comitin data. |Steps Table
Creation-identify data types; identify columns dat can n cant b null; identify columns
dat must b unique; identify prim-foreign key mates; determine default values;
identify constraints on columns; create table n associated indexes.Schema
Definition: ControlProcessing/Storage Efficiency – choices of index , file
organization for base tables and indexes , data clustering , statistics maintenance.
Boolean – Not, then and then OR. VIEWS-Dynamic View-virtual table created upon
request; no data actually stored. data 4m base table;Based on SQL SELECT
Statement.Materialized View-data actualy stord,copy or replication f data,must b
refreshd periodicaly 2 match corspondin base tables. CHECK-prevents updates dat
wud create rows nt included in view. Adv Views-Simplify query commands;assist
wid data security; enhance programin productivity; contain most current base table
data;use lil storage space;provide customizd view 4 user; establish physical data
independence. Disadv-Use procesin time each view is referenced; may or may
not b directly updateable.Create statements : CREATE TABLE AssignedTo
(empNo VARCHAR (10) NOT NULL/DEFAULT ‘xyz’, projNo VARCHAR(10)
CHECK (ProjNo IN(1,3,4)),custID INTEGER GENERATED ALWAYS AS
IDENTITY(START WITH 1 INCREMENT BY 1 MIN VALUE 1 MAX VALUE
10 NO CYCLE),CONSTRAINT pk_AssignedTo_empNo
PRIMARYKEY(empNo,projNo),CONSTRAINT fk_AssignedTo_projNo
FOREIGN KEY (projNo) REFERENCES Project (projNo) ON DELETE NO
ACTION ON UPDATE NO ACTION); ALTER table table_name
alter_table_action Alter table actions:ADD [COLUMN] column_definition,
ALTER [COLUMN] column_name SET DEFAULT def_value, ALTER
[COLUMN] column_name DROP DEFAULT,DROP [COLUMN] column_name
[RESTRICT][CASCADE], ADD table constraint MERGE INTO tablename
USING table_reference ON (condition) WHEN MATCHED THEN UPDATE SET
column1 = value1 [, column2 = value2 ...] WHEN NOT MATCHED THEN
INSERT (column1 [, column2 ...]) VALUES (value1 [, value2 ... CREATE INDEX
Name_IDX ON Customer_T(CustomerName). 7Advanced SQL : `Join-
relational operation causes 2 or more tables wid common domain 2 b
combined into a single table or view. EquiJoin-joinin condn based on equality
between values in comon columns.comon columns appear redundantly in
result table. |NaturalJoin-equijoin in which 1 f d duplicate columns is
eliminatd.InnerJoin-part of equijoin.rows must hv matchn values 2 apear in
result table.Used instead of WHERE clause.OuterJoin-all rows
included.|UnionJoin-al columns 4m each table n instance 4 each row f each
table. Equijoin/Inner Join-SELECT Customer.ID,OrderD.ID,
Customer.Name,OrderD.ID FROM Customer INNER JOIN ORDERD ON
Customer.ID=Order.CustomerID ORDER BY ORDERID;.NaturalJoin-
SELECT Customer.ID,Customer.Name,OrderD.ID FROM Customer
NATURAL JOIN ORDERD ON Customer.ID= Order.CustomerID ORDER
BY ORDERID;.Instead of Natural Join write LEFT/RIGHT OUTER
JOIN.Customers wid no orders vl also b listed. |SelfJoin-used on tables wid
unary rlshnp. Subquery-placin inner query inside outer query.used in
WHERE, within HAVING,as table f FROM .Noncorrelated-executed 1ce 4
entire outer query.do not depend on data 4m outer query. Correlated-use data
4m outer query.execute 1ce 4 each row returnd by outer query.use d EXISTS
operator. SELECT * FROM OrderLine WHERE EXISTS (SELECT* FROM
Product WHERE Product.productID =OrderLine.productID AND
Product.productFinish='Oak');.Always refer to an attr in outer table.UNION-
combine output 4m multiple queries in 1 table.Qty n datatypes of attr in
SELECT clause must b identical of each query.CASE EXPRESSION-To do
If-Then-Else expression.SELECT CASE WHEN ProductLineID = 1 THEN
productDescription WHEN ProductLineID = 2 THEN productFinish WHEN
ProductLineID=3 THEN '3ds' ELSE 'End' END AS Product,
ProductDescription,productID FROM Product;.Cant write numeric values.
Query Efficiency-Use SELECT clause not SELECT*;limit no f
subqueries;make view if data used many times. Transaction-discrete unit f
work dat must b completely processed or nt processd at all.SQL Commands-
BEGINTRANSACTION|ENDTRANSACTION(boundaries);COMMIT(per
manent updates);ROLLBACK(cancel updates since last COMMIT).BEGIN
Transaction INSERT OrderID, Orderdate, CustomerID into OrderD; INSERT
ID,Qty into OrderLine; END Transaction.Data Dictionary Facilities-system
tabled dat store metadata;users can view some tables bt nt update;Eg in Oracle
11g-DBA_TABLES(table ),DBA_CONSTRAINTS (constraintsdescription),
DBA_USERS(usersinfo); EginSQL-sys.columns(tablencolumn definitions),
sys.indexes(table index info), sys. foreign_key_columns(columns in foreign
key constraints).Routines-prog modules dat execute on demand.Functions-
routines dt return values n take input parameters.Procedures-routines dt nt
return values n cn take input or output parameters.Triggers-routines dt execute
in response 2 DB event(insert, update,delete).Trigger Syntax-CREATE
TRIGGER trigger_name {BEFORE|AFTER|INSTEAD OF} {INSERT|
DELETE|UPDATE} ON table_name [FOR EACH {ROW|STATEMENT}]
[WHEN (search condition)] <triggered SQL statement here>;.Embedded
SQL-includin hard-coded SQL statements in prog written in another lang such
as C or Java.Dynamic SQL-ability 4 app prog 2 generate SQL code on fly as
appisrunnin. Reasons2embed SQL in 3GL-cancreatemoreflexible, accessible