Thanks, Kevin, for taking the time to make it easy to digest.
@kkb4251
8 жыл бұрын
super kevin, this video gives the 100% clarity about the internal architecture of sql.
@dsc40sundar18
7 ай бұрын
great lecture still we passed 10 years but the lecture get super and it made easy understand architecture great simple a fan made comment
@BeOneWeOne
9 жыл бұрын
Thanks Kevin!!! You helped me learn the SQL architecture to an extent.
@gurupanda4192
4 жыл бұрын
Hey mate you can join this one also kzitem.info/door/PLfz1lS_mCZd9zQKzf0mQGc8QyDK25I6FI
@gurupanda4192
4 жыл бұрын
kzitem.info/news/bejne/y6mhx66dimuQiX4
@abhibansal1234
8 жыл бұрын
This is great, helps understand the internals nicely, thanks Kevin,
@tarikhhistory7869
9 жыл бұрын
Thanks A Lot Kevin.. One of the best explanation..
@rajendrasinghbisht6165
9 жыл бұрын
Thanks Kevin for this excellent presentation !!!
@TheNayan20
8 жыл бұрын
Thanks for uploading this Kevin..
@TechandArt
3 жыл бұрын
I have covered one session abt ARCHITECTURE
@chrisjokuhn3968
6 жыл бұрын
Wow, that was very educational. KK is like the CK Louis of SQL teaching. Many thanks for the upload!
@sqkumar7198
10 жыл бұрын
Hi Kevin, In the video you said you gonna tell about trouble shooting of 30 MB execution plan. Do you have a blog or video about working on that issue?
@mdkhan303
9 ай бұрын
loved it
@michael.333
6 жыл бұрын
Thank you Kevin, this is very helpful.
@mithunmukherjee2311
4 жыл бұрын
Hi Kevin, I wanted to know any co-relation between the removal of any plan from the plan cache and the corresponding data present in the buffer cache. While removing the plan from the plan cache by the lazy writer does it also perform any action to remove the corresponding data page from the buffer cache. What if happens if there is plan in the plan cache but not present in the buffer cache.
@susantakumarrath3311
7 жыл бұрын
How & who does load the newly created Plan from Query Optimizer to Plan cache???
@satishgarepalli5977
4 жыл бұрын
Hi kevin what is the actual job of query executor?
@sunilguragol6395
8 жыл бұрын
Hi Kevin does it use MRU(Most rectently used for frequently running plans),LRU will be in bottom of buffer cache?
@satishkumargarepalli3692
4 жыл бұрын
Awesome session... What happens to the data in the transaction log and has not been written to the disk (mdf). if in that mean time the server crashes?
@balajijayaraman5584
3 жыл бұрын
Data will be lost in the above scenario.
@alexberenguer6423
10 жыл бұрын
Amazing, thanks for that.
@loudravetortoise
6 жыл бұрын
Why were databases created in the first place. To make money for companies. Never thought bout it that way before
@sagarshah4214
10 жыл бұрын
very informative video... thanks
@sandeeepbandaru
4 жыл бұрын
Did he say ACID?
@25prathap
8 жыл бұрын
Best Session!!
@TechandArt
3 жыл бұрын
Good one 👍
@hugokornelis6840
6 жыл бұрын
Very interesting, i did not know about optimizer, funny thing
@haroonmd78
3 жыл бұрын
Very goo content
@mehdicharife2335
Жыл бұрын
42:49 Does that mean that the Cmd Parser is the one in charger of looking up the cache plan for matchinf execution plans for the received query?
@carlitobrigante293
5 жыл бұрын
Wow. I learned a lot
@tjedwin7
4 жыл бұрын
Awesome!
@craigbryant3191
4 жыл бұрын
One of us is seriously confused about what Atomic and Consistent mean. Atomic doesn't remotely mean that a transaction "doesn't do multiple things"; it means that the entire transaction goes as an indivisible unit--precisely so that, if you want to do more than one thing (debit one account and credit another), it either all happens or none of it does. Consistent doesn't mean a transaction does the same thing every time you run it, but that the database transitions from one relationally-consistent state to another. It has nothing to do with repeatability. I'm hoping this gets a lot better, fast. The first two substantive things he said about databases seem to be flat-out wrong.
@craigbryant3191
4 жыл бұрын
So he got Isolation *reasonably* right--like a grade B--and then confused Durable with Atomic. (Durable means that committed transactions remain committed, even if, say, the server crashes.) I guess I should be grateful that he led off with a topic I know. The rest of the video is a pass.
@cb6276
4 жыл бұрын
@@craigbryant3191 Thanks for clarifying, I'm new to ACID and those were a little confusing as I was trying to reason through it in my head.
@satishkumargarepalli3692
4 жыл бұрын
Atomicity means either all the statements should get committed or none of the statements should be committed.
@satishkumargarepalli3692
4 жыл бұрын
Consistency means If there is any disaster in the system also, the transactions should be consistent either by rolling backward or rolling forward after the disaster.
@satishkumargarepalli3692
4 жыл бұрын
Consider ATM of any bank as an example it will be the perfect one to understand easily.
@MsAZAZ00
10 жыл бұрын
from where can we get the slides
@hellonavneet
10 жыл бұрын
I believe here are the slides kevinekline.com/wp-content/uploads/2010/03/UG-SQL-Server-Internals-Architecture.pdf
@MsAZAZ00
10 жыл бұрын
Navneet Gupta thank you brother and the best gift that I can give to you in return is this... quran.com/
@murlikrishna9002
2 жыл бұрын
Hi Kevin.... I told my son I can make pal with you by database reply me
@sinjitasarkar5676
8 жыл бұрын
grt
@neelred10
7 жыл бұрын
examples for consistant and isolated trasaction didnt make sense.. Wikipedia has good example to understand these concepts
Пікірлер: 50