SQL Server KOMPONENTE:: Sistem Za Upravljanje Relacionim Bazama Podataka
SQL Server KOMPONENTE:: Sistem Za Upravljanje Relacionim Bazama Podataka
KOMPONENTE:
za
Sva#a ta'ela ima #$l$ne: atri'ut #a$ n&r. !r. +$risni#a, ime #$risni#a, adresa...Red: entite tj. single $ccurrence .n&r.cust$mer num'er 1/01221-. Relati$nal data'ase engine je di)ajniran )a s&remanje sl$g$va transa#cija generirani3 $nline transa#cijama 4L56 sistema #a$ i $nline anali)a 4LA6 #$ji )a3tijevaju data 7are3$uses. 4LA6 * anali)a &$data#a, i)vje8(a, $'rada veli#e #$li9ine &$data#a 4L56 * veli# 'r$j transa#cija $d #$ji3 sva#a sadr:ava malu #$li9inu &$data#a
Skladitenje podataka je &r$ces integracije &$data#a $ &$sl$vanju ne#e $rgani)acije u jednu 'a)u &$data#a .u l$gi9#$m smislu-, i) #$je #rajnji #$risnici * analiti9ari, menad:eri, d$n$sitelji &$sl$vni3 $dlu#a * m$gu raditi i)vje8(a, &$stavljati u&ite i anali)irati &$dat#e. data #art S#ladi8te &$data#a se 9est$ sast$ji $d ra)li9iti3 manji3 s#u&$va &$data#a #$je m$:em$ na)vati &$dru9nim s#ladi8tima &$data#a.
A$$lication S"$$ort
Transact-SQL
Stru#tuirani u&itni je)i# . Structured Query Language, SQL- jeste je)i# )a )adavanje u&ita nad 'a)$m &$data#a. %Pat! q"eries &indo s data access inter'aces: suc3 as "icr$s$ft Active; ata 4'jects .A 4-, 4LE !, $r 4&en ata'ase <$nnectivity .4 !<- t$ send 5ransact*SQL statements $r ;6at3 queries t$ t3e relati$nal data'ase engine using a native 4LE ! &r$vider $r 4 !< driver. A client a&&licati$n can als$ use =y&erte>t 5ransfer 6r$t$c$l .=556- t$ send 5ransact* SQL statements $r ;6at3 queries t$ t3e relati$nal data'ase engine.
Additional (o#$onents
SQL Server 2000 )ata Trans'or#ation Services *)TS+ SQL Server 2000 ,e$lication SQL Server 2000 Englis! Q"ery Meta )ata Services
Hl$'al All$cati$n "a&, @nf$rmati$n a'$ut all$cated e>tents. Sec$ndary Hl$'al All$cati$n "a& 6age Iree S&ace @nde> All$cati$n "a& !ul# <3anged "a& ifferential <3anged "a& @nf$rmati$n a'$ut free s&ace availa'le $n &ages. @nf$rmati$n a'$ut e>tents used 'y a ta'le $r inde>. @nf$rmati$n a'$ut e>tents m$dified 'y 'ul# $&erati$ns since t3e last !A<+J6 L4H statement. @nf$rmati$n a'$ut e>tents t3at 3ave c3anged since t3e last !A<+J6 A5A!ASE statement.
L$g files d$ n$t c$ntain &ages t3ey c$ntain a series $f l$g rec$rds. ?e sadr:i &ages ve( ni) l$g )a&isa. ata &ages c$ntain all t3e data in data r$7s e>ce&t te>t, nte>t, and image data, 73ic3 is st$red in se&arate &ages. ata r$7s are &laced serially $n t3e &age starting immediately after t3e 3eader. A r$7 $ffset ta'le starts at t3e end $f t3e &age. 53e r$7 $ffset ta'le c$ntains $ne entry f$r eac3 r$7 $n t3e &age and eac3 entry rec$rds 3$7 far t3e first 'yte $f t3e r$7 is fr$m t3e start $f t3e &age. 53e entries in t3e r$7 $ffset ta'le are in reverse sequence fr$m t3e sequence $f t3e r$7s $n t3e &age.
R$7s cann$t s&an &ages in SQL Server. @n SQL Server 2000, t3e ma>imum am$unt $f data c$ntained in a single r$7 is 20F0 'ytes, n$t including te>t, nte>t, and image data.
E1tents are t3e 'asic unit in 73ic3 s&ace is all$cated t$ ta'les and inde>es.
Extents 8 pages u
sljedu
An e>tent is 2 c$ntigu$us &ages, $r F1 +!. 53is means SQL Server 2000 data'ases 3ave 1F e>tents &er mega'yte. 5$ ma#e its s&ace all$cati$n efficient, SQL Server 2000 d$es n$t all$cate entire e>tents t$ ta'les 7it3 small am$unts $f data. SQL Server 2000 3as t7$ ty&es $f e>tents: 5ni'or# e>tents are $7ned 'y a single $'jectK all eig3t &ages in t3e e>tent can $nly 'e used 'y t3e $7ning $'ject. Mi1ed e>tents are s3ared 'y u& t$ eig3t $'jects. A ne7 ta'le $r inde> is usually all$cated &ages fr$m mi>ed e>tents. L3en t3e ta'le $r inde> gr$7s t$ t3e &$int t3at it 3as eig3t &ages, it is s7itc3ed t$ unif$rm e>tents. @f y$u create an inde> $n an e>isting ta'le t3at 3as en$ug3 r$7s t$ generate eig3t &ages in t3e inde>, all all$cati$ns t$ t3e inde> are in unif$rm e>tents.
Security Architecture?
2 niv$ security: * Authentication
- Authorization
53e 'irst level $f security is aut3enticati$n. A"t!entication determines 73et3er t3e user 3as a valid l$gin acc$unt t$ c$nnect t$ an instance $f SQL Server 2000. 53e second level $f security is aut3$ri)ati$n, 73ic3 is als$ called &ermissi$n validati$n. A"t!ori.ation determines 73at activities t3e user can &erf$rm in 73ic3 data'ases after 'eing aut3enticated 'y SQL Server 2000.
A"tori.aci9a
Aedn$m #ada je SQL Server autentificira$ usera, SQL Server $dre%uje #$ji (e l$gin @ 'iti $vla8ten,aut$ri)iran )a i)vr8avanje 'il$ #$je a#tivn$sti u 'a)i. L$gin @ sam &$ se'i ne daje user d$)v$le )a &ristu& $'je#tu u 'a)i ve( d$)v$ljava useru &r$sljediti )a sljede(i #$ra# #$ji je aut$ri)acija, $vla8tenje ili &remissi$n, d$)v$la &r$vjera valjan$sti. JSER A<<4J?5 A admin m$ra &$ve)ati l$gin @ sa user @ u 'a)i &rije 'il$ #$je #$ne#cije sa tim l$gin$m @ .
HJES5 JSER A<<4J?5 L$gin @ nije e#s&licitn$ ve)an sa user @ u 'a)i, ve( sa guset user @ . A#$ 'a)a ima guest user a#$unt l$g$n je $grani9en na &rava #$ja &ri&adaju guest useru. A#$ 'a)a nema guest user a#$unta l$gi ne m$:e &ristu&iti 'a)i $sim a#$ nije &$ve)an sa $dre%enim user @ . R4LES R$le s#u&ljaju usere u sam$stalnu jedinicu &rema #$jima se setiraju d$)v$le.
ollation Settings
Collation definira kako e se podaci usporeivati i sortitati. The collation order specified here determines the default code page and sort order for all non-UNICODE characters and is the UNICODE collation order for all !" erver s#stem data$ases. The sort order determines %hether operations on #our data %ill $e case-sensitive or not. You can always reconfigure your server for a different collation/sort order later. There is a high price to payyou have to rebuild all your databases and possibly lose some data.
Deciding on a
SQL Server 2000 supports two client licensin& modes, per processor and per seat. ith per-processor licensin&, %ou need a license on the server runnin& SQL Server 2000 $or each processor on the computer. +$ this client licensin& mode is selected, no additional licenses are needed $or an% clients connectin& to this installation o$ SQL Server 2000. #his client licensin& mode is intended to be most cost-e$$ective $or installations with lar&e numbers o$ users, particularl% anon%mous +nternet users. ith per-seat licensin&, each client connectin& to an installation o$ SQL Server 2000 must have a separate -lient Access License .-AL/. #his client licensin& mode is intended to be most cost-e$$ective $or installations with a small to medium number o$ de$ined users connectin& to more than one server. #he Licensin& !ode option is not available when installin& the (nterprise Evaluation edition. 'er seat is the licensin& mode $or the (nterprise (valuation edition.
How do you identify the named instances from a client? #he named instances are identi$ied b% the network name o$ the computer plus the instance name, like this,
Na#eO'(o#$"ter;Na#eO'7nstance S$ my test system instance called ?e7Server 'ec$mes: !J<+5ES5N?ELSERVER N2=0>);MSSQL
2or each named instance o$ SQL Server that %ou install, the de$ault directories are,
N6r$gram IilesN"icr$s$ft SQL ServerN"SSQLO@nstance?ameN!inn f$r e>ecuta'le files. N6r$gram IilesN"icr$s$ft SQL ServerN"SSQLO@nstance?ameN ata f$r data files
Shared tools $or all instances, both de$ault and named instances, are located in the 3'ro&ram 2iles3!icroso$t SQL Server3*03#ools director%. 4ou can speci$% $ile paths other than the de$ault locations $or pro&ram and data $ile $or multiple instances. #he $ollowin& illustration shows the simplest case o$ multiple instances o$ !icroso$t SQL Server 2000, the de$ault instance and one named instance, Instance . A named instance has its own $ull set o$ data $iles and e"ecutable $iles. -ommon $iles used b% both the de$ault instance and an% named instances are installed in the $older 3'ro&ram 2iles3!icroso$t SQL Server3*0.
#nderstanding #ni+ue
hen %ou install multiple instances o$ SQL Server 2000 .or SQL Server 2000 and either SQL Server 5.6 and 7.0/, s%stem and user databases are uni8ue and completel% independent o$ each other. #here is no direct connection between s%stem or user databases in one instance and s%stem and user databases in another instance. #hese databases $unction as i$ the% were residin& on separate SQL Server installations. Each instance has its own SQL Server and SQL Server !"ent services . 2or the de$ault instance, the names o$ these services are #SSQLServer and SQLServer-!"ent. 2or named instances, the names o$ these services are #SSQL$instancename and SQL!"ent$instancename. #he database en&ine $or each instance is con$i&ured completel% independentl% o$ an% other instance. 9obs on one instance have no knowled&e o$ and do not interact with jobs on an% other instance.
jeljene #$m&$nente:
ee previous lo& for older entries. av lo& (e spreml(en kao stari i otvara novi
Stoppin& and restartin& the SQL Server service b% usin& the sp_cycle_errorlog s%stem stored procedure. This is useful on a busy system where the error lo" file can become %uite lar"e.
hen addin& these re&istr% ke%s, the SQL Server Setup pro&ram &enerall% limits read or write access to these ke%s to the SQL Server services domain user account and members o$ the local Administrators &roup .and sometimes the S%stem &roup/. 2or certain ke%s, read access is &ranted to authenticated users and members o$ the local 'ower 1sers &roup. +n addition, owners o$ objects ma% have access to subke%s throu&h the -reator ?wner &roup i$ the% are &ranted permission to create objects. @% de$ault, the SQL Server services domain user account and members o$ the local Administrators &roup have 2ull -ontrol access to these re&istr% ke%s and their subke%s.
Lesson Su%%ary
#he SQL Server 2000 Setup pro&ram installs SQL Server 2000 $iles into a number o$ di$$erent $older structures. ?ne $older structure .3'ro&ram 2iles3!icroso$t SQL Server3*0/ contains the $iles common to all SQL Server 2000 instances on the computer. Another $older structure .either 3'ro&ram 2iles3!icroso$t SQL Server3!SSQL or 3'ro&ram 2iles3!icroso$t SQL Server3!ss8lAInstanceName/ contains the pro&ram and data $iles uni8ue to the particular SQL Server 2000 instance. ?n an B#2S partition, the Setup pro&ram secures the $older structure containin& the pro&ram and data $ile $olders b% limitin& access permissions to this $older structure to the SQL Server services domain user account and members o$ the local Administrators &roup. +n addition, the Setup pro&ram adds and limits access to a number o$ ke%s in the indows re&istr%. +t also ensures that the SQL Server services domain user account has write access to two e"istin& re&istr% ke%s. 2inall%, the !icroso$t SQL Server pro&ram &roup is created containin& shortcuts to the most commonl% used SQL Server 2000 e"ecutable pro&rams and wizards, as well as to @ooks ?nline.