1.65 score from hupso.pl for:
sqlballs.com



HTML Content


Titlesqlballs

Length: 8, Words: 1
Description pusty

Length: 0, Words: 0
Keywords pusty
Robots
Charset UTF-8
Og Meta - Title exist
Og Meta - Description exist
Og Meta - Site name pusty
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 4248
Text/HTML 16.46 %
Headings H1 0
H2 11
H3 3
H4 0
H5 0
H6 0
H1
H2
pages
friday, february 3, 2017
monday, december 5, 2016
monday, august 29, 2016
sql live 360
pass summit 2015
labels
up coming events
search this blog
blog archive
about me
H3
the high availability conversation part 1: introduction
optimize for unknown
sql azure, hekaton, and bob dorr is awesome
H4
H5
H6
strong
b
i
em
Bolds strong 0
b 0
i 0
em 0
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name exist
Pliki zewnętrzne 17
Pliki CSS 2
Pliki javascript 15
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 301
Linki wewnętrzne 72
Linki zewnętrzne 229
Linki bez atrybutu Title 266
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=pagelist&widgetid=pagelist1&action=editwidget§ionid=crosscol
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=image&widgetid=image4&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=image&widgetid=image2&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=adsense&widgetid=adsense1&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=label&widgetid=label1&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=text&widgetid=text2&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=blogsearch&widgetid=blogsearch1&action=editwidget§ionid=sidebar-right-1
▼  javascript:void(0)
▼  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
►  javascript:void(0)
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=blogarchive&widgetid=blogarchive1&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=profile&widgetid=profile1&action=editwidget§ionid=sidebar-right-1
- //www.blogger.com/rearrange?blogid=5485181488522668586&widgettype=attribution&widgetid=attribution1&action=editwidget§ionid=footer-3

Linki zewnętrzne

- http://www.sqlballs.com/
home http://www.sqlballs.com/
training http://www.sqlballs.com/p/training.html
resources http://www.sqlballs.com/p/resources.html
contact http://www.sqlballs.com/p/contact.html
pro 2012 practices http://www.sqlballs.com/p/pro-sql-2012-practices.html
the high availability conversation part 1: introduction http://www.sqlballs.com/2017/02/the-high-availability-conversation-part.html
- https://2.bp.blogspot.com/-mptv861rbua/wjsppahqioi/aaaaaaaaeoc/sx17oshmyrgo5qy8snqcn2zdgp5_owfegclcb/s1600/kenneth%2bfisher%2btwitter.png
- https://1.bp.blogspot.com/-qtss-cbtqpa/wjsq4v-0ysi/aaaaaaaaeoo/l4jqp-4yrdy9zcqxbvnintvoctiuinqigclcb/s1600/saftey%2bfirst.jpg
- https://1.bp.blogspot.com/-ro-emg-3518/wjsrbceuydi/aaaaaaaaeos/azn2ddoegtyquebhfewhil7ypmybrmuzgclcb/s1600/conversation.jpg
- https://1.bp.blogspot.com/-_2gvl3rufw8/wjsr4mrkvyi/aaaaaaaaeo0/z6gunbjqeneq6ayegrfw92sxdsonfqkxgclcb/s1600/cubs%2breaction.jpg
bradley ball https://plus.google.com/114042912444925263953
9:21 am http://www.sqlballs.com/2017/02/the-high-availability-conversation-part.html
1 comment: http://www.sqlballs.com/2017/02/the-high-availability-conversation-part.html#comment-form
- https://www.blogger.com/post-edit.g?blogid=5485181488522668586&postid=1480578059345606025&from=pencil
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=1480578059345606025&target=email
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=1480578059345606025&target=blog
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=1480578059345606025&target=twitter
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=1480578059345606025&target=facebook
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=1480578059345606025&target=pinterest
ha http://www.sqlballs.com/search/label/ha
high availability http://www.sqlballs.com/search/label/high%20availability
optimize for unknown http://www.sqlballs.com/2016/12/optimize-for-unknown.html
- https://4.bp.blogspot.com/-lgurkiuhdcc/wa-conj2fdi/aaaaaaaaemc/xqzh6txhmmebdviapd4md_ikozygk3dpgcew/s1600/fall%2bleaves.jpg
imitation game http://theimitationgamemovie.com/
- https://1.bp.blogspot.com/-tzgdrllwtf0/wa-comf1hmi/aaaaaaaaemc/xnn6crqv5-wd_0g1ulbxm7qvclwnnw8pwcew/s1600/roller%2bcoasters%2bfrom%2bthe%2bair.jpg
- https://3.bp.blogspot.com/-uu7hljbdpce/wa-yja6yfpi/aaaaaaaaemg/uckkxr6ukeggtajyjbc58bae-guigbblqclcb/s1600/results%2b1.png
- https://4.bp.blogspot.com/-vtpkbaotglu/wa-zcmxllni/aaaaaaaaemk/p7m3u34r8wwfo5socpmncg3s4u9l4peugclcb/s1600/results%2b2.png
- https://3.bp.blogspot.com/-y9lri89as_m/wa-cnq0yr5i/aaaaaaaaemc/5kxrhsxat-k4qoaxoaiijx_w2e2bggdqwcew/s1600/execution%2bplan%2b1.png
- https://3.bp.blogspot.com/-t9zisktcfne/wa-cnhtmvmi/aaaaaaaaemc/xrbhoyyjcqobw4xwtrqnebhs2rmzicirwcew/s1600/execution%2bplan%2b2.png
- https://4.bp.blogspot.com/-xuzzhuvvo0s/wa-cngdanti/aaaaaaaaemc/mvssminqgj0jagprflubabbsmcnklk7dqcew/s1600/execution%2bplan%2b3.png
- https://3.bp.blogspot.com/-gn950tnu0ys/wa_vxvzifei/aaaaaaaaem4/xiiebqopqi8hjho8ginfwdupy3lgclejgclcb/s1600/execution%2bplan%2b5.png
- https://3.bp.blogspot.com/-c5l27tefitw/wbc_-ogvyki/aaaaaaaaeni/ys5ktnuiaxeh-fbds0nw2odnaufyees8qclcb/s1600/histogram.png
bradley ball https://plus.google.com/114042912444925263953
9:12 am http://www.sqlballs.com/2016/12/optimize-for-unknown.html
2 comments: http://www.sqlballs.com/2016/12/optimize-for-unknown.html#comment-form
- https://www.blogger.com/post-edit.g?blogid=5485181488522668586&postid=5839311768826728512&from=pencil
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=5839311768826728512&target=email
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=5839311768826728512&target=blog
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=5839311768826728512&target=twitter
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=5839311768826728512&target=facebook
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=5839311768826728512&target=pinterest
data skew http://www.sqlballs.com/search/label/data%20skew
database administration http://www.sqlballs.com/search/label/database%20administration
performance tuning http://www.sqlballs.com/search/label/performance%20tuning
sql azure, hekaton, and bob dorr is awesome http://www.sqlballs.com/2016/08/sql-azure-hekaton-and-bob-dorr-is.html
how many tables can i have in sql azure db & sql server https://blogs.msdn.microsoft.com/sql_pfe_blog/2016/08/22/how-many-tables-can-i-have-in-sql-azure-db-sql-server/
- https://1.bp.blogspot.com/-olsvikx2sr0/v8q_nxuypri/aaaaaaaaela/hzucrxvtqzoewplb3kfeyfnk33dw7tlrqclcb/s1600/the%2bbook%2bof%2bface%2bquestion.png
blog https://blogs.msdn.microsoft.com/bobsql/
@bobwardms https://twitter.com/bobwardms
blog https://blogs.msdn.microsoft.com/bobsql/
https://blogs.msdn.microsoft.com/bobsql/ https://blogs.msdn.microsoft.com/bobsql/
click here https://blogs.msdn.microsoft.com/bobsql/2016/08/23/create-table-disk-vs-in-memory-optimized/
- https://1.bp.blogspot.com/-b6ftrpcxwis/v8rdmhytbri/aaaaaaaaelm/5uh5l-jxtjclmpzn8qkoaqxtttsiouckaclcb/s1600/a%2bteam.jpg
bradley ball https://plus.google.com/114042912444925263953
10:17 am http://www.sqlballs.com/2016/08/sql-azure-hekaton-and-bob-dorr-is.html
no comments: http://www.sqlballs.com/2016/08/sql-azure-hekaton-and-bob-dorr-is.html#comment-form
- https://www.blogger.com/post-edit.g?blogid=5485181488522668586&postid=8239840211335071870&from=pencil
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=8239840211335071870&target=email
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=8239840211335071870&target=blog
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=8239840211335071870&target=twitter
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=8239840211335071870&target=facebook
https://www.blogger.com/share-post.g?blogid=5485181488522668586&postid=8239840211335071870&target=pinterest
hekaton http://www.sqlballs.com/search/label/hekaton
in-memory oltp http://www.sqlballs.com/search/label/in-memory%20oltp
sql azure http://www.sqlballs.com/search/label/sql%20azure
sql internals http://www.sqlballs.com/search/label/sql%20internals
older posts http://www.sqlballs.com/search?updated-max=2016-08-29t10:17:00-04:00&max-results=3
home http://www.sqlballs.com/
posts (atom) http://www.sqlballs.com/feeds/posts/default
24 hop http://www.sqlballs.com/search/label/24%20hop
acid http://www.sqlballs.com/search/label/acid
ad http://www.sqlballs.com/search/label/ad
advice http://www.sqlballs.com/search/label/advice
apply http://www.sqlballs.com/search/label/apply
backwards compatibility http://www.sqlballs.com/search/label/backwards%20compatibility
bi http://www.sqlballs.com/search/label/bi
books http://www.sqlballs.com/search/label/books
bpe http://www.sqlballs.com/search/label/bpe
certifications http://www.sqlballs.com/search/label/certifications
cetificates http://www.sqlballs.com/search/label/cetificates
cloud http://www.sqlballs.com/search/label/cloud
compression http://www.sqlballs.com/search/label/compression
corruption http://www.sqlballs.com/search/label/corruption
cte http://www.sqlballs.com/search/label/cte
data skew http://www.sqlballs.com/search/label/data%20skew
database administration http://www.sqlballs.com/search/label/database%20administration
dba question of the day http://www.sqlballs.com/search/label/dba%20question%20of%20the%20day
dba virtual chapter http://www.sqlballs.com/search/label/dba%20virtual%20chapter
denali http://www.sqlballs.com/search/label/denali
devconnections http://www.sqlballs.com/search/label/devconnections
duplicate sids http://www.sqlballs.com/search/label/duplicate%20sids
goals http://www.sqlballs.com/search/label/goals
ha http://www.sqlballs.com/search/label/ha
heaps http://www.sqlballs.com/search/label/heaps
hekaton http://www.sqlballs.com/search/label/hekaton
high availability http://www.sqlballs.com/search/label/high%20availability
humor http://www.sqlballs.com/search/label/humor
in-memory oltp http://www.sqlballs.com/search/label/in-memory%20oltp
indexes http://www.sqlballs.com/search/label/indexes
learning http://www.sqlballs.com/search/label/learning
magicpass http://www.sqlballs.com/search/label/magicpass
maintenance plans http://www.sqlballs.com/search/label/maintenance%20plans
master data management http://www.sqlballs.com/search/label/master%20data%20management
master data services http://www.sqlballs.com/search/label/master%20data%20services
mcm http://www.sqlballs.com/search/label/mcm
meme monday http://www.sqlballs.com/search/label/meme%20monday
microsoft http://www.sqlballs.com/search/label/microsoft
mvp http://www.sqlballs.com/search/label/mvp
myths http://www.sqlballs.com/search/label/myths
nomcom http://www.sqlballs.com/search/label/nomcom
opass http://www.sqlballs.com/search/label/opass
orlando http://www.sqlballs.com/search/label/orlando
partitioning http://www.sqlballs.com/search/label/partitioning
pass http://www.sqlballs.com/search/label/pass
pass dba virtual chapter http://www.sqlballs.com/search/label/pass%20dba%20virtual%20chapter
pass election http://www.sqlballs.com/search/label/pass%20election
pass summit http://www.sqlballs.com/search/label/pass%20summit
pass summit 2011 http://www.sqlballs.com/search/label/pass%20summit%202011
performance tuning http://www.sqlballs.com/search/label/performance%20tuning
performance tuning workshop http://www.sqlballs.com/search/label/performance%20tuning%20workshop
personal http://www.sqlballs.com/search/label/personal
powershell http://www.sqlballs.com/search/label/powershell
pragmatic works http://www.sqlballs.com/search/label/pragmatic%20works
pre-cons http://www.sqlballs.com/search/label/pre-cons
presentations http://www.sqlballs.com/search/label/presentations
professional development http://www.sqlballs.com/search/label/professional%20development
publix http://www.sqlballs.com/search/label/publix
reference http://www.sqlballs.com/search/label/reference
scripts http://www.sqlballs.com/search/label/scripts
security http://www.sqlballs.com/search/label/security
setting up a virtual lab http://www.sqlballs.com/search/label/setting%20up%20a%20virtual%20lab
slide decks http://www.sqlballs.com/search/label/slide%20decks
snapshots http://www.sqlballs.com/search/label/snapshots
sql 2008 http://www.sqlballs.com/search/label/sql%202008
sql 2008 r2 http://www.sqlballs.com/search/label/sql%202008%20r2
sql 2012 http://www.sqlballs.com/search/label/sql%202012
sql 2014 http://www.sqlballs.com/search/label/sql%202014
sql azure http://www.sqlballs.com/search/label/sql%20azure
sql community http://www.sqlballs.com/search/label/sql%20community
sql fundamentals http://www.sqlballs.com/search/label/sql%20fundamentals
sql internals http://www.sqlballs.com/search/label/sql%20internals
sql live 360 http://www.sqlballs.com/search/label/sql%20live%20360
sql os http://www.sqlballs.com/search/label/sql%20os
sql rally http://www.sqlballs.com/search/label/sql%20rally
sql saturday http://www.sqlballs.com/search/label/sql%20saturday
sql saturday 62 http://www.sqlballs.com/search/label/sql%20saturday%2062
sql server http://www.sqlballs.com/search/label/sql%20server
sql university http://www.sqlballs.com/search/label/sql%20university
ssis http://www.sqlballs.com/search/label/ssis
statistics http://www.sqlballs.com/search/label/statistics
t-sql http://www.sqlballs.com/search/label/t-sql
t-sql tuesday http://www.sqlballs.com/search/label/t-sql%20tuesday
tales from the query processor http://www.sqlballs.com/search/label/tales%20from%20the%20query%20processor
tde http://www.sqlballs.com/search/label/tde
thank you http://www.sqlballs.com/search/label/thank%20you
training http://www.sqlballs.com/search/label/training
transparent data encryption http://www.sqlballs.com/search/label/transparent%20data%20encryption
twitter http://www.sqlballs.com/search/label/twitter
ucp http://www.sqlballs.com/search/label/ucp
views http://www.sqlballs.com/search/label/views
vm http://www.sqlballs.com/search/label/vm
windows 2012 for the dba http://www.sqlballs.com/search/label/windows%202012%20for%20the%20dba
windows server http://www.sqlballs.com/search/label/windows%20server
workload generator http://www.sqlballs.com/search/label/workload%20generator
2017 http://www.sqlballs.com/search?updated-min=2017-01-01t00:00:00-05:00&updated-max=2018-01-01t00:00:00-05:00&max-results=1
february http://www.sqlballs.com/2017_02_01_archive.html
the high availability conversation part 1: introdu... http://www.sqlballs.com/2017/02/the-high-availability-conversation-part.html
2016 http://www.sqlballs.com/search?updated-min=2016-01-01t00:00:00-05:00&updated-max=2017-01-01t00:00:00-05:00&max-results=5
december http://www.sqlballs.com/2016_12_01_archive.html
august http://www.sqlballs.com/2016_08_01_archive.html
may http://www.sqlballs.com/2016_05_01_archive.html
february http://www.sqlballs.com/2016_02_01_archive.html
2015 http://www.sqlballs.com/search?updated-min=2015-01-01t00:00:00-05:00&updated-max=2016-01-01t00:00:00-05:00&max-results=4
december http://www.sqlballs.com/2015_12_01_archive.html
june http://www.sqlballs.com/2015_06_01_archive.html
january http://www.sqlballs.com/2015_01_01_archive.html
2014 http://www.sqlballs.com/search?updated-min=2014-01-01t00:00:00-05:00&updated-max=2015-01-01t00:00:00-05:00&max-results=15
november http://www.sqlballs.com/2014_11_01_archive.html
october http://www.sqlballs.com/2014_10_01_archive.html
september http://www.sqlballs.com/2014_09_01_archive.html
june http://www.sqlballs.com/2014_06_01_archive.html
may http://www.sqlballs.com/2014_05_01_archive.html
april http://www.sqlballs.com/2014_04_01_archive.html
february http://www.sqlballs.com/2014_02_01_archive.html
2013 http://www.sqlballs.com/search?updated-min=2013-01-01t00:00:00-05:00&updated-max=2014-01-01t00:00:00-05:00&max-results=34
october http://www.sqlballs.com/2013_10_01_archive.html
september http://www.sqlballs.com/2013_09_01_archive.html
august http://www.sqlballs.com/2013_08_01_archive.html
july http://www.sqlballs.com/2013_07_01_archive.html
june http://www.sqlballs.com/2013_06_01_archive.html
may http://www.sqlballs.com/2013_05_01_archive.html
april http://www.sqlballs.com/2013_04_01_archive.html
march http://www.sqlballs.com/2013_03_01_archive.html
february http://www.sqlballs.com/2013_02_01_archive.html
january http://www.sqlballs.com/2013_01_01_archive.html
2012 http://www.sqlballs.com/search?updated-min=2012-01-01t00:00:00-05:00&updated-max=2013-01-01t00:00:00-05:00&max-results=33
december http://www.sqlballs.com/2012_12_01_archive.html
november http://www.sqlballs.com/2012_11_01_archive.html
october http://www.sqlballs.com/2012_10_01_archive.html
september http://www.sqlballs.com/2012_09_01_archive.html
august http://www.sqlballs.com/2012_08_01_archive.html
july http://www.sqlballs.com/2012_07_01_archive.html
june http://www.sqlballs.com/2012_06_01_archive.html
may http://www.sqlballs.com/2012_05_01_archive.html
april http://www.sqlballs.com/2012_04_01_archive.html
march http://www.sqlballs.com/2012_03_01_archive.html
february http://www.sqlballs.com/2012_02_01_archive.html
january http://www.sqlballs.com/2012_01_01_archive.html
2011 http://www.sqlballs.com/search?updated-min=2011-01-01t00:00:00-05:00&updated-max=2012-01-01t00:00:00-05:00&max-results=50
december http://www.sqlballs.com/2011_12_01_archive.html
november http://www.sqlballs.com/2011_11_01_archive.html
october http://www.sqlballs.com/2011_10_01_archive.html
september http://www.sqlballs.com/2011_09_01_archive.html
august http://www.sqlballs.com/2011_08_01_archive.html
july http://www.sqlballs.com/2011_07_01_archive.html
june http://www.sqlballs.com/2011_06_01_archive.html
may http://www.sqlballs.com/2011_05_01_archive.html
april http://www.sqlballs.com/2011_04_01_archive.html
march http://www.sqlballs.com/2011_03_01_archive.html
february http://www.sqlballs.com/2011_02_01_archive.html
january http://www.sqlballs.com/2011_01_01_archive.html
2010 http://www.sqlballs.com/search?updated-min=2010-01-01t00:00:00-05:00&updated-max=2011-01-01t00:00:00-05:00&max-results=8
december http://www.sqlballs.com/2010_12_01_archive.html
november http://www.sqlballs.com/2010_11_01_archive.html
- https://plus.google.com/114042912444925263953
bradley ball https://plus.google.com/114042912444925263953
view my complete profile https://plus.google.com/114042912444925263953
blogger https://www.blogger.com

Zdjęcia

Zdjęcia 32
Zdjęcia bez atrybutu ALT 28
Zdjęcia bez atrybutu TITLE 32
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

http://2.bp.blogspot.com/-0guzx8pthpc/tcnc4ezetbi/aaaaaaaaake/dxs06etlqjy/s1600/sqlballsheaderlogo%2bcopy.jpg
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://2.bp.blogspot.com/-mptv861rbua/wjsppahqioi/aaaaaaaaeoc/sx17oshmyrgo5qy8snqcn2zdgp5_owfegclcb/s400/kenneth%2bfisher%2btwitter.png
https://1.bp.blogspot.com/-qtss-cbtqpa/wjsq4v-0ysi/aaaaaaaaeoo/l4jqp-4yrdy9zcqxbvnintvoctiuinqigclcb/s320/saftey%2bfirst.jpg
https://1.bp.blogspot.com/-ro-emg-3518/wjsrbceuydi/aaaaaaaaeos/azn2ddoegtyquebhfewhil7ypmybrmuzgclcb/s320/conversation.jpg
https://1.bp.blogspot.com/-_2gvl3rufw8/wjsr4mrkvyi/aaaaaaaaeo0/z6gunbjqeneq6ayegrfw92sxdsonfqkxgclcb/s1600/cubs%2breaction.jpg
https://resources.blogblog.com/img/icon18_edit_allbkg.gif
https://4.bp.blogspot.com/-lgurkiuhdcc/wa-conj2fdi/aaaaaaaaemc/xqzh6txhmmebdviapd4md_ikozygk3dpgcew/s320/fall%2bleaves.jpg
https://1.bp.blogspot.com/-tzgdrllwtf0/wa-comf1hmi/aaaaaaaaemc/xnn6crqv5-wd_0g1ulbxm7qvclwnnw8pwcew/s320/roller%2bcoasters%2bfrom%2bthe%2bair.jpg
https://3.bp.blogspot.com/-uu7hljbdpce/wa-yja6yfpi/aaaaaaaaemg/uckkxr6ukeggtajyjbc58bae-guigbblqclcb/s1600/results%2b1.png
https://4.bp.blogspot.com/-vtpkbaotglu/wa-zcmxllni/aaaaaaaaemk/p7m3u34r8wwfo5socpmncg3s4u9l4peugclcb/s1600/results%2b2.png
https://3.bp.blogspot.com/-y9lri89as_m/wa-cnq0yr5i/aaaaaaaaemc/5kxrhsxat-k4qoaxoaiijx_w2e2bggdqwcew/s320/execution%2bplan%2b1.png
https://3.bp.blogspot.com/-t9zisktcfne/wa-cnhtmvmi/aaaaaaaaemc/xrbhoyyjcqobw4xwtrqnebhs2rmzicirwcew/s320/execution%2bplan%2b2.png
https://4.bp.blogspot.com/-xuzzhuvvo0s/wa-cngdanti/aaaaaaaaemc/mvssminqgj0jagprflubabbsmcnklk7dqcew/s320/execution%2bplan%2b3.png
https://3.bp.blogspot.com/-gn950tnu0ys/wa_vxvzifei/aaaaaaaaem4/xiiebqopqi8hjho8ginfwdupy3lgclejgclcb/s320/execution%2bplan%2b5.png
https://3.bp.blogspot.com/-c5l27tefitw/wbc_-ogvyki/aaaaaaaaeni/ys5ktnuiaxeh-fbds0nw2odnaufyees8qclcb/s320/histogram.png
https://resources.blogblog.com/img/icon18_edit_allbkg.gif
https://1.bp.blogspot.com/-olsvikx2sr0/v8q_nxuypri/aaaaaaaaela/hzucrxvtqzoewplb3kfeyfnk33dw7tlrqclcb/s320/the%2bbook%2bof%2bface%2bquestion.png
https://1.bp.blogspot.com/-b6ftrpcxwis/v8rdmhytbri/aaaaaaaaelm/5uh5l-jxtjclmpzn8qkoaqxtttsiouckaclcb/s1600/a%2bteam.jpg
https://resources.blogblog.com/img/icon18_edit_allbkg.gif
http://1.bp.blogspot.com/-ytf_wfomvhu/ujh1aibwooi/aaaaaaaadra/cnl7eded0tg/s1600/sqlspk1.tif
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
http://4.bp.blogspot.com/-9bvc_a4wp6w/vmgrtdfkifi/aaaaaaaaefk/2n1999eiv8u/s1600-r/i%2527m%2bspeaking%2bgraphic_small.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
//lh6.googleusercontent.com/-x5j-nngkvte/aaaaaaaaaai/aaaaaaaacb0/qohusbo8zme/s80-c/photo.jpg
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png

Zdjęcia bez atrybutu ALT

https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://2.bp.blogspot.com/-mptv861rbua/wjsppahqioi/aaaaaaaaeoc/sx17oshmyrgo5qy8snqcn2zdgp5_owfegclcb/s400/kenneth%2bfisher%2btwitter.png
https://1.bp.blogspot.com/-qtss-cbtqpa/wjsq4v-0ysi/aaaaaaaaeoo/l4jqp-4yrdy9zcqxbvnintvoctiuinqigclcb/s320/saftey%2bfirst.jpg
https://1.bp.blogspot.com/-ro-emg-3518/wjsrbceuydi/aaaaaaaaeos/azn2ddoegtyquebhfewhil7ypmybrmuzgclcb/s320/conversation.jpg
https://1.bp.blogspot.com/-_2gvl3rufw8/wjsr4mrkvyi/aaaaaaaaeo0/z6gunbjqeneq6ayegrfw92sxdsonfqkxgclcb/s1600/cubs%2breaction.jpg
https://resources.blogblog.com/img/icon18_edit_allbkg.gif
https://4.bp.blogspot.com/-lgurkiuhdcc/wa-conj2fdi/aaaaaaaaemc/xqzh6txhmmebdviapd4md_ikozygk3dpgcew/s320/fall%2bleaves.jpg
https://1.bp.blogspot.com/-tzgdrllwtf0/wa-comf1hmi/aaaaaaaaemc/xnn6crqv5-wd_0g1ulbxm7qvclwnnw8pwcew/s320/roller%2bcoasters%2bfrom%2bthe%2bair.jpg
https://3.bp.blogspot.com/-uu7hljbdpce/wa-yja6yfpi/aaaaaaaaemg/uckkxr6ukeggtajyjbc58bae-guigbblqclcb/s1600/results%2b1.png
https://4.bp.blogspot.com/-vtpkbaotglu/wa-zcmxllni/aaaaaaaaemk/p7m3u34r8wwfo5socpmncg3s4u9l4peugclcb/s1600/results%2b2.png
https://3.bp.blogspot.com/-y9lri89as_m/wa-cnq0yr5i/aaaaaaaaemc/5kxrhsxat-k4qoaxoaiijx_w2e2bggdqwcew/s320/execution%2bplan%2b1.png
https://3.bp.blogspot.com/-t9zisktcfne/wa-cnhtmvmi/aaaaaaaaemc/xrbhoyyjcqobw4xwtrqnebhs2rmzicirwcew/s320/execution%2bplan%2b2.png
https://4.bp.blogspot.com/-xuzzhuvvo0s/wa-cngdanti/aaaaaaaaemc/mvssminqgj0jagprflubabbsmcnklk7dqcew/s320/execution%2bplan%2b3.png
https://3.bp.blogspot.com/-gn950tnu0ys/wa_vxvzifei/aaaaaaaaem4/xiiebqopqi8hjho8ginfwdupy3lgclejgclcb/s320/execution%2bplan%2b5.png
https://3.bp.blogspot.com/-c5l27tefitw/wbc_-ogvyki/aaaaaaaaeni/ys5ktnuiaxeh-fbds0nw2odnaufyees8qclcb/s320/histogram.png
https://resources.blogblog.com/img/icon18_edit_allbkg.gif
https://1.bp.blogspot.com/-olsvikx2sr0/v8q_nxuypri/aaaaaaaaela/hzucrxvtqzoewplb3kfeyfnk33dw7tlrqclcb/s320/the%2bbook%2bof%2bface%2bquestion.png
https://1.bp.blogspot.com/-b6ftrpcxwis/v8rdmhytbri/aaaaaaaaelm/5uh5l-jxtjclmpzn8qkoaqxtttsiouckaclcb/s1600/a%2bteam.jpg
https://resources.blogblog.com/img/icon18_edit_allbkg.gif
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png
https://resources.blogblog.com/img/icon18_wrench_allbkg.png

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

pages home training resources contact pro 2012 practices friday, february 3, 2017 the high availability conversation part 1: introduction hello dear reader! twitter is a fantastic tool if you use sql server. it is a great way to network, find presentations, interact with experts, and #sqlhelp offers some of the best technical forum conversation on the subject. i was on twitter and my friend kenneth fisher asked a question. kenneth’s question was interesting. let’s define a couple terms up front. ha in this case is high availability. it is the capability for a database or data store to maintain availability and connectivity to a graphical user interface, web service, or some other data consuming application despite a localized outage or failure of the primary system. high availability is different from disaster recovery, or dr. disaster recovery is required when a disaster, natural or man-made, prevents the use of resources within a data center and the hardware within to support regular business processes. in this blog, we will be addressing ha only as that was what kenneth had asked about. asked for further explanation kenneth didn’t need ha at his environment, more on this in a moment, he was looking for a rounded point of view. i had a couple replies and then started direct messaging, dm`ing, kenneth to share my insight. this is a conversation you must have with the business. a keen understanding of how business logic translates into technology workflows requires both it and business leaders making the right decisions together. over this series i’m going to give you a couple examples on when ha was needed. some in which ha was not. later we will discuss different ha technologies and understanding when each one is right for you. first i will define some key things to cover in a high availability conversation between the business and it. the high availability conversation there are three types of conversations: technical, business, and budget. business comes first. our first goal is to understand what the business is facing. some of this you may know in advance. if so review the information to ensure business and it communication. · describe the business process – o what product or service are we providing? o what type of employees participate in the process? o what does each employee need to get from the process? · diagram a workflow of how a customer interaction occurs · add the steps that are it specific · critical days, weeks, months, holidays, or times of the day for the specific business process · understand any current paint points first make sure you understand the business process surrounding any technical system. draw shapes on dry erase boards, connect them to business process, make sure you understand who the business owner is for each technical system. force self-examination and business awareness. add your it system to the diagram. highlight business and it dependencies. talk to teams to understand what happens when a system goes down. you can use viso, powerpoint, a dry erase board, or whatever you like. make a visual representation based on the findings from the meeting. confirm that everyone can agree on it, or use it to solicit their teams for additional vetting. you may not get it right on the first run. that is okay. this could be an interview process depending on the complexity of your it environment. there are some standard technical terms that you should use · sla – service level agreement. this is the expected agreement between the business and it for overall system availability. this may represent business hours. in some cases, service providers may have contractual sla’s. if your business has an sla with customers there could be a financial penalty for not meeting the sla. · rpo – recovery point objective. this defines the amount of data that can be lost on a system in and not cause impact or harm to the business. the point at which all data or transactions must be recoverable. the price of any solution increases with lower rpo’s. · rto – recovery time objective. this is the amount of time it takes to get a system online in the event of an outage. the time to recover will vary greatly on size, volume, and type of data discussed. if you seek to reduce recovery time there are strategies or technical solutions that can be utilized. the complexity of these solutions can add to the overall cost. refining ha: using the three bears technique after the first business meeting the technical team should meet to discuss their options. i like to develop three options when working with it managers. this is where we, the technical staff, align a few things. · proposed technical solution · cost of technical solution · cost to maintain technical solution · migration from the existing platform to the new there are many ways to address ha. some could be solutions using third party vendor products that you may already utilize, others can be hardware or virtualization options, and other can be database specific. it the architecture, size of the corporation, and business need for ha will shape these decisions. notice i said three options for it managers. when you meet with the business you should have a cohesive vision. when i started my it career finding a manager with it experience was extremely rare. it is increasingly becoming more common. as it knowledge permeates the business world it will be more common to give the three options to the business for collaboration. if you are lucky you are in an environment like that today. for this step you need to take all business requirements and align them to technical justification for a solution. producing three options may seem difficult. think of this like the old children’s story goldilocks and the three bears. one of these technical solutions will be too cold, too much latency and not viable for 100% of business scenarios. one of these solutions will be too hot, this is the spare-no-expense-throw-everything-you’ve-got-at-it-as-close-to-five-9’s-as-possible option. one will be just right. it will fit the business needs, not be cost prohibitive, and be maintainable solution. you’re natural first reaction will be, “why three options! why not just propose the right one?”. valid point dear reader. the reason is simple. this is a high stakes mental exercise. the business, jobs, profitability, security of our data, and many other things may rest on our solutions. what makes a good it person great? their mind. our ability to make virtual skyscrapers and complex virtual super highways out of thin air. there may be a natural reaction to jump at a ‘best’ quick solution. take your time, think outside of the box. you will find if you push yourself to consider multiple options, one may supplant the ‘best’ quick solution. while too cold and too hot may not work in this situation, they may next time. we’re done, right? wrong. if we are changing an existing system, how are we going to get there? we need to understand if there are production outages windows we must avoid. for example in retail or manufacturing there are normally brown out and blackout windows for it. leading up to black friday, a united states shopping holiday, most retail environments have it blackouts. this means no changes can be made in production unless they are to fix an existing bug. everything must wait. leading up to a blackout window there is a brown out window. during a brown out no changes can be made to existing server infrastructures, this can limit the ability to allocate more storage from san’s, networking equipment, or networking changes in general. if we are performing an upgrade to use a new ha technology, when will that happen? how do we migrate? what are the steps? have we coordinated with the application development teams? they will need to regression test their applications when a migration occurs. this means changes in the development, qa/uat, and eventually the production environments. additional coordination will require the server and san teams. depending on the size of your it organization this may be a large effort or the act of shouting over your cubical wall. the ha conversation ii: the solution & the response we’ve spoken with the business. we understand their process. we drew it up, passed it around, and found a few new things along the way. we met as an it team. we produced tentative solutions. took the ideas to management and now we have a winner. we’ve coordinated with our counterparts to make sure we knew what a tentative timeline would look like. our next step? present the solution to the business. after this meeting the goal is to move forward. to get the project going. we’ve spent a lot of work on this, and you want to see it implemented. sometimes that happens. sometimes it doesn’t. there are a lot of factors that can go into why something doesn’t happen. because they can be legion, and it distracts from our overall topic, i’m going to skip why things do not happen. it is an intriguing topic that i may blog on later. when we move forward the goal it to do so in a collaborative way. a good solution addresses business needs, technical requirements, project timelines, and budget. there may be changes, there may be wrinkles that occur along the way. what looked good on paper doesn’t always translate to technical viability. it is important to maintain the communication amongst key stake holders along the way. alright dear reader, this has been a good kick off towards our topic. if you have questions or comments please sound off below! i look forward to hearing from you. next we will review a couple real-life examples of when ha was needed and when it wasn’t. as always, thank you for stopping by. thanks, brad posted by bradley ball at 9:21 am 1 comment: email thisblogthis!share to twittershare to facebookshare to pinterest labels: ha, high availability monday, december 5, 2016 optimize for unknown hello dear reader! it's been a while. i was working with a friend and we came across an interesting problem. they had a large amount of skewness/data skew. this led to some performance issues for them. the way this manifested itself was in a set of queries that ran quickly, normally within seconds. then occasionally they ran much longer. to be precise, they ran about x800 times longer. as you can imagine this is a less than ideal situation for a production environment. their solution was to add option (recompile) to all of their stored procedures. this solved the issue with their data skew. it caused additional side effects. increased cpu as every stored procedure now had to recompile before execution. no stored procedure could experience plan reuse. using dmv's to track stored procedure utilization and statistics no longer worked. "so balls", you say, "what is the alternative? is there an alternative? and what in the name of king and country is skewness/data skew!" ahh great question dear reader! dear reader why are you english today? "because you watched the imitation game last night, and benedict cumberbatch's voice is still stuck in your head." right as always dear reader! good point let's explain it and then do a demo! skewness/data skew skewness is a term from statistics and probability theory that refers to the asymmetry on the probability distribution of a real valued random variable about its mean. this could get complicated quickly. in simpler terms that i can understand it means that there are patterns based on variables with an assigned real value. based on those variables skewness can be determined and it is the difference of the normal. how does this effect our query plans. with data skew we have a over abundance of data that fits one statistical model and it does not fit for others. this means the way the sql server cardinality estimator estimates for one may be different for another based on statistics. here's a quick example. i have a school with 100,000 students. every student has a combination of 10 different last names. on average one could assume that every 10,000 students will have different last names. if we randomly assign these values, there will be a slight skewness. most of the ranges will be similar. for this example i'll use my students table from my college database. select lastname, count(*) from dbo.students group by lastname order by count(*) desc; now we move a new student to the area. this one student will give us quite a bit of data skew, and will be extremely asymmetrical to the other results. in order to show this in action we'll make a stored procedure that returns our first name, last name, and the course name of students by last name. remember some students will have multiple courses. this means we will have more results than we do last names. if exists(select name from sys.procedures where name='p_sel_get_stu_name') begin drop procedure p_sel_get_stu_name end go create procedure p_sel_get_stu_name(@lname varchar(50)) as begin select s.firstname ,s.lastname ,c.coursename from dbo.students s left join enrollment e on s.studentid=e.studentid left join courses c on e.courseid = c.courseid where lastname=@lname end so now we will execute this query and see the difference between our query plans and benchmark the performance. exec p_sel_get_stu_name 'bradley' with recompile; exec p_sel_get_stu_name 'segarra' with recompile; the first query took a little over a second to return two rows. the second query was sub-second and returned 13,843 rows. each execution plan was different. one was parallel, the other was serial. that makes sense parallel returned over 13,000 rows, serial only returned 2 row. the statistical variance is different. the cardinality estimate gave us different results. now let's make this bad. i'm going to run the first query and second query again. this time i'm removing the with recompile. exec p_sel_get_stu_name 'bradley'; exec p_sel_get_stu_name 'segarra'; the first query did not change. the second one did. we used the cached plan. because of data skew we forced 13,843 rows through the serial execution plan. the result was 8 minutes and 42 seconds instead of a sub-second query. this is data skew. we've shown that recompiling the query forces both to execute with their least cost plan. is there another option? in this case we could use the query hint optimize for unknown. the benefit of optimize for unknown is that we can remove the recompile. this will allow us to get the best/least cost plan based on data skewness of the statistics. if exists(select name from sys.procedures where name='p_sel_get_stu_name') begin drop procedure p_sel_get_stu_name end go create procedure p_sel_get_stu_name(@lname varchar(50)) as begin select s.firstname ,s.lastname ,c.coursename from dbo.students s left join enrollment e on s.studentid=e.studentid left join courses c on e.courseid = c.courseid where lastname=@lname option (optimize for unknown) end exec p_sel_get_stu_name 'bradley'; exec p_sel_get_stu_name 'segarra'; now we execute our procedures and we get our execution plans. here are our new query plans. you'll notice that the execution plan based on statistical variance was parallel plan. both queries executed sub-second. this is not the least cost plan for the first query. in case you were curious here is a look at the histogram. wrap it up so what does this mean? for the business purpose of speeding up a query option recompile is completely valid. it comes at a cost. recompilations, increased cpu utilization, and you loose the history of the execution of the stored procedure from dmvs. if those costs do not effect you, or effect the system less than the fluctuation of query performance then it is valid. there is also another alternative to use in your tool belt. that is what we used today. like all things in computers use it judiciously. test, test, and retest before deploying into production. as always dear reader, thanks for stopping by. thanks, brad posted by bradley ball at 9:12 am 2 comments: email thisblogthis!share to twittershare to facebookshare to pinterest labels: data skew, database administration, performance tuning monday, august 29, 2016 sql azure, hekaton, and bob dorr is awesome hello dear reader! i had recently written a blog for the pfe blog, "how many tables can i have in sql azure db & sql server". it was a fun blog that i had written during a very long layover when traveling home. it covers the maximum number of objects that you can create in sql server. in this blog i had written up a demo to create the maximum number of tables you can in a database. i also explained that based on table creation rates it would take around 64 days for me to reach that limit. as a point of interest i tried creating in-memory oltp/hekaton tables vs. native t-sql tables. there i noticed something very interesting. creating in-memory oltp tables was slower than creating t-sql tables. a lot slower. to be crystal clear this is specifically on the creation of tables nothing more. this has nothing to do with the insert, deletion, or reading of data. my blog was about how many objects could a database hold, and i had a tight loop creating tables over and over again. i explored different options to get as many tables created as quickly as possible. "so balls", you say, "you said this was slow. how slow?" great point dear reader, back to the question! i was able to create 388 native t-sql tables per second and only 3 in-memory oltp tables. on the book of faces someone asked about the results very quickly. i reached out to my colleague robert dorr (blog) from the sql team. he and bob ward, from the sql tiger team, (@bobwardms | blog) are running a great blog called bob sql, https://blogs.msdn.microsoft.com/bobsql/ , you should check this out. he was kind enough to write up a reply that covered how things work under the covers. to read his blog click here. quick summary each in-memory table is managed compiled code. by making in-memory objects compiled this allows us to save cpu cycles and allows us to skip some of the traditional over head of native t-sql objects. when we issue the ddl to create an in-memory table we follow the same processes as a native t-sql table. we also do two additional steps we create the access ddl code and we compile the access ddl code. these steps give us a one time hit on creation of an object that give us long term benefits as we execute against our in-memory oltp/hekaton tables. wrap up there are nothing but great questions out there dear reader. the worst kind of question is the one that is not asked. in this case the question pushed me to look for an answer that i already wanted to know. in this case a demo that i almost didn't write, a question from a place that i normally do not look for questions, are all that we needed to get an answer. my thanks again to robert dorr for taking the time to give us the answer. i love it when a plan comes together. until next time thanks for stopping by. thanks, bradley ball posted by bradley ball at 10:17 am no comments: email thisblogthis!share to twittershare to facebookshare to pinterest labels: hekaton, in-memory oltp, sql azure, sql internals older posts home subscribe to: posts (atom) sql live 360 pass summit 2015 labels 24 hop acid ad advice apply backwards compatibility bi books bpe certifications cetificates cloud compression corruption cte data skew database administration dba question of the day dba virtual chapter denali devconnections duplicate sids goals ha heaps hekaton high availability humor in-memory oltp indexes learning magicpass maintenance plans master data management master data services mcm meme monday microsoft mvp myths nomcom opass orlando partitioning pass pass dba virtual chapter pass election pass summit pass summit 2011 performance tuning performance tuning workshop personal powershell pragmatic works pre-cons presentations professional development publix reference scripts security setting up a virtual lab slide decks snapshots sql 2008 sql 2008 r2 sql 2012 sql 2014 sql azure sql community sql fundamentals sql internals sql live 360 sql os sql rally sql saturday sql saturday 62 sql server sql university ssis statistics t-sql t-sql tuesday tales from the query processor tde thank you training transparent data encryption twitter ucp views vm windows 2012 for the dba windows server workload generator up coming events search this blog blog archive ▼  2017 (1) ▼  february (1) the high availability conversation part 1: introdu... ►  2016 (5) ►  december (1) ►  august (1) ►  may (2) ►  february (1) ►  2015 (4) ►  december (2) ►  june (1) ►  january (1) ►  2014 (15) ►  november (2) ►  october (2) ►  september (5) ►  june (2) ►  may (1) ►  april (1) ►  february (2) ►  2013 (34) ►  october (5) ►  september (4) ►  august (2) ►  july (9) ►  june (1) ►  may (2) ►  april (5) ►  march (1) ►  february (1) ►  january (4) ►  2012 (33) ►  december (2) ►  november (2) ►  october (5) ►  september (1) ►  august (7) ►  july (2) ►  june (1) ►  may (5) ►  april (2) ►  march (1) ►  february (4) ►  january (1) ►  2011 (90) ►  december (1) ►  november (2) ►  october (12) ►  september (7) ►  august (16) ►  july (9) ►  june (10) ►  may (11) ►  april (9) ►  march (7) ►  february (3) ►  january (3) ►  2010 (8) ►  december (2) ►  november (6) about me bradley ball hi i'm brad, i'm a certified sql server database administrator. i've been in the it business for over 10 years and worked as a dba for the u.s. army, executive office of the president, and publix supermarkets in the great state of florida. and now i'm a sr. consultant for pragmatic works. view my complete profile awesome inc. template. powered by blogger.


Here you find all texts from your page as Google (googlebot) and others search engines seen it.

Words density analysis:

Numbers of all words: 3660

One word

Two words phrases

Three words phrases

the - 5.98% (219)
and - 2.08% (76)
his - 1.69% (62)
for - 1.64% (60)
this - 1.58% (58)
►  - 1.56% (57)
you - 1.34% (49)
pro - 1.28% (47)
are - 1.09% (40)
name - 1.04% (38)
that - 1.01% (37)
our - 1.01% (37)
sql - 1.01% (37)
business - 0.93% (34)
all - 0.85% (31)
data - 0.85% (31)
here - 0.82% (30)
get - 0.71% (26)
will - 0.68% (25)
was - 0.66% (24)
not - 0.66% (24)
over - 0.66% (24)
able - 0.66% (24)
with - 0.63% (23)
there - 0.57% (21)
out - 0.57% (21)
may - 0.57% (21)
thin - 0.55% (20)
use - 0.52% (19)
can - 0.52% (19)
solution - 0.52% (19)
from - 0.52% (19)
some - 0.49% (18)
blog - 0.49% (18)
per - 0.49% (18)
exec - 0.49% (18)
ability - 0.46% (17)
table - 0.46% (17)
day - 0.46% (17)
lab - 0.46% (17)
one - 0.46% (17)
(1) - 0.46% (17)
plan - 0.46% (17)
skew - 0.46% (17)
work - 0.44% (16)
time - 0.44% (16)
query - 0.44% (16)
student - 0.41% (15)
technical - 0.41% (15)
when - 0.41% (15)
read - 0.41% (15)
what - 0.41% (15)
act - 0.38% (14)
now - 0.38% (14)
(2) - 0.38% (14)
very - 0.38% (14)
option - 0.38% (14)
first - 0.38% (14)
have - 0.36% (13)
procedure - 0.36% (13)
way - 0.36% (13)
last - 0.33% (12)
than - 0.33% (12)
tables - 0.33% (12)
p_sel_get_stu_name - 0.33% (12)
add - 0.3% (11)
process - 0.3% (11)
brad - 0.3% (11)
under - 0.3% (11)
how - 0.3% (11)
cover - 0.3% (11)
reader - 0.3% (11)
need - 0.3% (11)
question - 0.3% (11)
dear - 0.3% (11)
high - 0.3% (11)
second - 0.27% (10)
ran - 0.27% (10)
course - 0.27% (10)
share - 0.27% (10)
other - 0.27% (10)
end - 0.27% (10)
understand - 0.27% (10)
availability - 0.27% (10)
compile - 0.27% (10)
system - 0.27% (10)
in-memory - 0.25% (9)
different - 0.25% (9)
pass - 0.25% (9)
too - 0.25% (9)
point - 0.25% (9)
make - 0.25% (9)
your - 0.25% (9)
their - 0.25% (9)
king - 0.25% (9)
server - 0.25% (9)
cost - 0.25% (9)
options - 0.25% (9)
create - 0.22% (8)
any - 0.22% (8)
long - 0.22% (8)
could - 0.22% (8)
thank - 0.22% (8)
team - 0.22% (8)
students - 0.22% (8)
three - 0.22% (8)
right - 0.22% (8)
conversation - 0.22% (8)
quick - 0.22% (8)
had - 0.22% (8)
bradley - 0.22% (8)
database - 0.22% (8)
rest - 0.22% (8)
great - 0.22% (8)
store - 0.19% (7)
they - 0.19% (7)
old - 0.19% (7)
skewness - 0.19% (7)
ball - 0.19% (7)
recompile - 0.19% (7)
based - 0.19% (7)
interest - 0.19% (7)
look - 0.19% (7)
object - 0.19% (7)
solutions - 0.19% (7)
things - 0.19% (7)
each - 0.19% (7)
february - 0.19% (7)
know - 0.19% (7)
met - 0.19% (7)
recover - 0.19% (7)
product - 0.19% (7)
does - 0.19% (7)
t-sql - 0.19% (7)
native - 0.19% (7)
like - 0.16% (6)
thanks - 0.16% (6)
window - 0.16% (6)
view - 0.16% (6)
part - 0.16% (6)
twitter - 0.16% (6)
performance - 0.16% (6)
execution - 0.16% (6)
ways - 0.16% (6)
every - 0.16% (6)
these - 0.16% (6)
new - 0.16% (6)
term - 0.16% (6)
sla - 0.16% (6)
take - 0.16% (6)
environment - 0.16% (6)
stored - 0.16% (6)
more - 0.16% (6)
step - 0.16% (6)
(5) - 0.16% (6)
give - 0.16% (6)
fit - 0.16% (6)
lastname - 0.16% (6)
about - 0.16% (6)
december - 0.16% (6)
meet - 0.16% (6)
oltp - 0.16% (6)
case - 0.16% (6)
virtual - 0.16% (6)
i'm - 0.14% (5)
action - 0.14% (5)
where - 0.14% (5)
present - 0.14% (5)
why - 0.14% (5)
good - 0.14% (5)
plans - 0.14% (5)
many - 0.14% (5)
execute - 0.14% (5)
led - 0.14% (5)
production - 0.14% (5)
two - 0.14% (5)
return - 0.14% (5)
select - 0.14% (5)
statistics - 0.14% (5)
changes - 0.14% (5)
means - 0.14% (5)
example - 0.14% (5)
require - 0.14% (5)
hekaton - 0.14% (5)
cause - 0.14% (5)
bob - 0.14% (5)
august - 0.14% (5)
june - 0.14% (5)
dba - 0.14% (5)
asked - 0.14% (5)
rpo - 0.14% (5)
recovery - 0.14% (5)
kenneth - 0.14% (5)
result - 0.14% (5)
going - 0.14% (5)
reader! - 0.14% (5)
book - 0.14% (5)
service - 0.14% (5)
labels - 0.11% (4)
way. - 0.11% (4)
business. - 0.11% (4)
again - 0.11% (4)
must - 0.11% (4)
always - 0.11% (4)
books - 0.11% (4)
then - 0.11% (4)
effect - 0.11% (4)
its - 0.11% (4)
did - 0.11% (4)
(4) - 0.11% (4)
next - 0.11% (4)
best - 0.11% (4)
2012 - 0.11% (4)
off - 0.11% (4)
april - 0.11% (4)
find - 0.11% (4)
side - 0.11% (4)
september - 0.11% (4)
october - 0.11% (4)
maintain - 0.11% (4)
black - 0.11% (4)
november - 0.11% (4)
january - 0.11% (4)
couple - 0.11% (4)
quickly - 0.11% (4)
windows - 0.11% (4)
it. - 0.11% (4)
goal - 0.11% (4)
develop - 0.11% (4)
has - 0.11% (4)
teams - 0.11% (4)
additional - 0.11% (4)
optimize - 0.11% (4)
should - 0.11% (4)
unknown - 0.11% (4)
see - 0.11% (4)
meeting - 0.11% (4)
azure - 0.11% (4)
procedures - 0.11% (4)
existing - 0.11% (4)
event - 0.11% (4)
rows - 0.11% (4)
plan. - 0.11% (4)
move - 0.11% (4)
working - 0.11% (4)
tables. - 0.11% (4)
join - 0.11% (4)
left - 0.11% (4)
specific - 0.11% (4)
- 0.11% (4)
creating - 0.11% (4)
results - 0.11% (4)
begin - 0.11% (4)
steps - 0.11% (4)
objects - 0.11% (4)
sure - 0.11% (4)
times - 0.11% (4)
solution. - 0.11% (4)
test - 0.11% (4)
labels: - 0.08% (3)
twittershare - 0.08% (3)
skew. - 0.08% (3)
by. - 0.08% (3)
thanks, - 0.08% (3)
posted - 0.08% (3)
less - 0.08% (3)
skewness/data - 0.08% (3)
thisblogthis!share - 0.08% (3)
facebookshare - 0.08% (3)
interesting - 0.08% (3)
issue - 0.08% (3)
pinterest - 0.08% (3)
2016 - 0.08% (3)
email - 0.08% (3)
home - 0.08% (3)
cpu - 0.08% (3)
code - 0.08% (3)
dorr - 0.08% (3)
written - 0.08% (3)
demo - 0.08% (3)
creation - 0.08% (3)
days - 0.08% (3)
nothing - 0.08% (3)
ddl - 0.08% (3)
answer - 0.08% (3)
alternative - 0.08% (3)
summit - 0.08% (3)
hop - 0.08% (3)
monday - 0.08% (3)
works - 0.08% (3)
july - 0.08% (3)
(9) - 0.08% (3)
march - 0.08% (3)
(7) - 0.08% (3)
tuning - 0.08% (3)
also - 0.08% (3)
longer - 0.08% (3)
courses - 0.08% (3)
real - 0.08% (3)
variable - 0.08% (3)
plans. - 0.08% (3)
statistical - 0.08% (3)
another - 0.08% (3)
names. - 0.08% (3)
dbo.students - 0.08% (3)
name, - 0.08% (3)
'bradley' - 0.08% (3)
allow - 0.08% (3)
'segarra' - 0.08% (3)
sub-second - 0.08% (3)
returned - 0.08% (3)
parallel - 0.08% (3)
serial - 0.08% (3)
run - 0.08% (3)
used - 0.08% (3)
least - 0.08% (3)
stopping - 0.08% (3)
lot - 0.08% (3)
needed - 0.08% (3)
notice - 0.08% (3)
agree - 0.08% (3)
development - 0.08% (3)
natural - 0.08% (3)
address - 0.08% (3)
within - 0.08% (3)
force - 0.08% (3)
made - 0.08% (3)
connect - 0.08% (3)
size - 0.08% (3)
most - 0.08% (3)
only - 0.08% (3)
blackout - 0.08% (3)
brown - 0.08% (3)
along - 0.08% (3)
normally - 0.08% (3)
hot - 0.08% (3)
into - 0.08% (3)
manager - 0.08% (3)
both - 0.08% (3)
complex - 0.08% (3)
amount - 0.08% (3)
type - 0.08% (3)
comes - 0.08% (3)
valid - 0.08% (3)
between - 0.08% (3)
discuss - 0.08% (3)
we’ve - 0.08% (3)
them - 0.08% (3)
just - 0.08% (3)
using - 0.08% (3)
hello - 0.08% (3)
overall - 0.08% (3)
occur - 0.08% (3)
lower - 0.08% (3)
because - 0.08% (3)
comments - 0.08% (3)
topic - 0.08% (3)
define - 0.08% (3)
doesn’t - 0.08% (3)
terms - 0.08% (3)
reader, - 0.08% (3)
been - 0.08% (3)
application - 0.08% (3)
forward - 0.08% (3)
outage - 0.08% (3)
system. - 0.08% (3)
questions - 0.08% (3)
disaster - 0.08% (3)
oltp/hekaton - 0.05% (2)
were - 0.05% (2)
diagram - 0.05% (2)
employee - 0.05% (2)
review - 0.05% (2)
vs. - 0.05% (2)
process? - 0.05% (2)
represent - 0.05% (2)
reach - 0.05% (2)
slower - 0.05% (2)
budget. - 0.05% (2)
business, - 0.05% (2)
back - 0.05% (2)
key - 0.05% (2)
you. - 0.05% (2)
workflow - 0.05% (2)
depending - 0.05% (2)
customer - 0.05% (2)
environment. - 0.05% (2)
azure, - 0.05% (2)
hekaton, - 0.05% (2)
like. - 0.05% (2)
awesome - 0.05% (2)
complexity - 0.05% (2)
happens - 0.05% (2)
comments: - 0.05% (2)
robert - 0.05% (2)
fun - 0.05% (2)
test, - 0.05% (2)
around - 0.05% (2)
erase - 0.05% (2)
agreement - 0.05% (2)
covers - 0.05% (2)
valid. - 0.05% (2)
maximum - 0.05% (2)
number - 0.05% (2)
dry - 0.05% (2)
days, - 0.05% (2)
occurs - 0.05% (2)
wrap - 0.05% (2)
together. - 0.05% (2)
blog) - 0.05% (2)
events - 0.05% (2)
master - 0.05% (2)
hardware - 0.05% (2)
microsoft - 0.05% (2)
2011 - 0.05% (2)
pragmatic - 0.05% (2)
presentations - 0.05% (2)
publix - 0.05% (2)
2008 - 0.05% (2)
2014 - 0.05% (2)
saturday - 0.05% (2)
coming - 0.05% (2)
▼  - 0.05% (2)
chapter - 0.05% (2)
availability. - 0.05% (2)
interesting. - 0.05% (2)
friend - 0.05% (2)
interact - 0.05% (2)
server. - 0.05% (2)
tool - 0.05% (2)
2017 - 0.05% (2)
friday, - 0.05% (2)
(3) - 0.05% (2)
worked - 0.05% (2)
state - 0.05% (2)
resources - 0.05% (2)
blog, - 0.05% (2)
administration - 0.05% (2)
out. - 0.05% (2)
hit - 0.05% (2)
kind - 0.05% (2)
write - 0.05% (2)
later - 0.05% (2)
compiled - 0.05% (2)
code. - 0.05% (2)
allows - 0.05% (2)
head - 0.05% (2)
which - 0.05% (2)
processes - 0.05% (2)
access - 0.05% (2)
examples - 0.05% (2)
i’m - 0.05% (2)
but - 0.05% (2)
cte - 0.05% (2)
decisions - 0.05% (2)
answer. - 0.05% (2)
making - 0.05% (2)
internals - 0.05% (2)
older - 0.05% (2)
posts - 0.05% (2)
live - 0.05% (2)
360 - 0.05% (2)
technology - 0.05% (2)
2015 - 0.05% (2)
understanding - 0.05% (2)
started - 0.05% (2)
objective. - 0.05% (2)
managers. - 0.05% (2)
benefit - 0.05% (2)
while - 0.05% (2)
"so - 0.05% (2)
balls", - 0.05% (2)
say, - 0.05% (2)
alternative? - 0.05% (2)
environments - 0.05% (2)
leading - 0.05% (2)
let's - 0.05% (2)
explain - 0.05% (2)
retail - 0.05% (2)
probability - 0.05% (2)
random - 0.05% (2)
cold - 0.05% (2)
quickly. - 0.05% (2)
utilization - 0.05% (2)
variables - 0.05% (2)
those - 0.05% (2)
difference - 0.05% (2)
multiple - 0.05% (2)
push - 0.05% (2)
‘best’ - 0.05% (2)
fits - 0.05% (2)
super - 0.05% (2)
cardinality - 0.05% (2)
statistics. - 0.05% (2)
person - 0.05% (2)
makes - 0.05% (2)
everything - 0.05% (2)
during - 0.05% (2)
assign - 0.05% (2)
timeline - 0.05% (2)
stake - 0.05% (2)
communication - 0.05% (2)
translate - 0.05% (2)
skip - 0.05% (2)
monday, - 0.05% (2)
happen. - 0.05% (2)
something - 0.05% (2)
sometimes - 0.05% (2)
want - 0.05% (2)
training - 0.05% (2)
project - 0.05% (2)
would - 0.05% (2)
set - 0.05% (2)
before - 0.05% (2)
queries - 0.05% (2)
management - 0.05% (2)
longer. - 0.05% (2)
took - 0.05% (2)
tentative - 0.05% (2)
team. - 0.05% (2)
situation - 0.05% (2)
large - 0.05% (2)
san - 0.05% (2)
increased - 0.05% (2)
coordinated - 0.05% (2)
networking - 0.05% (2)
limit - 0.05% (2)
solutions. - 0.05% (2)
security - 0.05% (2)
query. - 0.05% (2)
migration - 0.05% (2)
lastname=@lname - 0.05% (2)
experience - 0.05% (2)
finding - 0.05% (2)
said - 0.05% (2)
recompile; - 0.05% (2)
shape - 0.05% (2)
options, - 0.05% (2)
rows. - 0.05% (2)
others - 0.05% (2)
already - 0.05% (2)
13,843 - 0.05% (2)
different. - 0.05% (2)
few - 0.05% (2)
e.courseid - 0.05% (2)
variance - 0.05% (2)
estimate - 0.05% (2)
align - 0.05% (2)
again. - 0.05% (2)
recompile. - 0.05% (2)
'bradley'; - 0.05% (2)
'segarra'; - 0.05% (2)
after - 0.05% (2)
bears - 0.05% (2)
cost. - 0.05% (2)
takes - 0.05% (2)
seconds - 0.05% (2)
c.courseid - 0.05% (2)
extremely - 0.05% (2)
database. - 0.05% (2)
sys.procedures - 0.05% (2)
mental - 0.05% (2)
count(*) - 0.05% (2)
reader. - 0.05% (2)
order - 0.05% (2)
bit - 0.05% (2)
skew, - 0.05% (2)
results. - 0.05% (2)
show - 0.05% (2)
propose - 0.05% (2)
reaction - 0.05% (2)
needs, - 0.05% (2)
exists(select - 0.05% (2)
name='p_sel_get_stu_name') - 0.05% (2)
s.studentid=e.studentid - 0.05% (2)
much - 0.05% (2)
drop - 0.05% (2)
story - 0.05% (2)
think - 0.05% (2)
requirements - 0.05% (2)
p_sel_get_stu_name(@lname - 0.05% (2)
varchar(50)) - 0.05% (2)
s.firstname - 0.05% (2)
,s.lastname - 0.05% (2)
,c.coursename - 0.05% (2)
today. - 0.05% (2)
common - 0.05% (2)
enrollment - 0.05% (2)
complete - 0.05% (2)
of the - 0.46% (17)
the business - 0.44% (16)
(1) ►  - 0.41% (15)
(2) ►  - 0.38% (14)
data skew - 0.3% (11)
dear reader - 0.3% (11)
to the - 0.27% (10)
this is - 0.27% (10)
will be - 0.25% (9)
on the - 0.25% (9)
that i - 0.25% (9)
is the - 0.25% (9)
there are - 0.25% (9)
high availability - 0.22% (8)
and it - 0.22% (8)
or the - 0.22% (8)
can be - 0.22% (8)
to get - 0.19% (7)
and the - 0.19% (7)
based on - 0.19% (7)
in the - 0.19% (7)
with the - 0.19% (7)
for the - 0.19% (7)
in this - 0.19% (7)
the first - 0.16% (6)
exec p_sel_get_stu_name - 0.16% (6)
if you - 0.16% (6)
from the - 0.16% (6)
sql server - 0.16% (6)
of data - 0.16% (6)
stored procedure - 0.16% (6)
(5) ►  - 0.16% (6)
in-memory oltp - 0.16% (6)
►  december - 0.14% (5)
business process - 0.14% (5)
bradley ball - 0.14% (5)
we will - 0.14% (5)
►  may - 0.14% (5)
dear reader! - 0.14% (5)
►  february - 0.14% (5)
technical solution - 0.14% (5)
►  june - 0.14% (5)
three options - 0.14% (5)
the way - 0.14% (5)
may be - 0.14% (5)
availability conversation - 0.11% (4)
going to - 0.11% (4)
native t-sql - 0.11% (4)
at the - 0.11% (4)
have a - 0.11% (4)
need to - 0.11% (4)
the business. - 0.11% (4)
give us - 0.11% (4)
now we - 0.11% (4)
procedure p_sel_get_stu_name - 0.11% (4)
execution plan - 0.11% (4)
first query - 0.11% (4)
optimize for - 0.11% (4)
this means - 0.11% (4)
►  april - 0.11% (4)
o what - 0.11% (4)
(4) ►  - 0.11% (4)
sql azure - 0.11% (4)
►  january - 0.11% (4)
when a - 0.11% (4)
►  october - 0.11% (4)
business and - 0.11% (4)
this case - 0.11% (4)
you can - 0.11% (4)
►  august - 0.11% (4)
a data - 0.11% (4)
►  september - 0.11% (4)
►  november - 0.11% (4)
►  march - 0.08% (3)
and we - 0.08% (3)
june (1) - 0.08% (3)
to pinterest - 0.08% (3)
to facebookshare - 0.08% (3)
ball at - 0.08% (3)
to twittershare - 0.08% (3)
email thisblogthis!share - 0.08% (3)
skewness/data skew - 0.08% (3)
by bradley - 0.08% (3)
by. thanks, - 0.08% (3)
for stopping - 0.08% (3)
dear reader, - 0.08% (3)
the way. - 0.08% (3)
get the - 0.08% (3)
along the - 0.08% (3)
(7) ►  - 0.08% (3)
as always - 0.08% (3)
brown out - 0.08% (3)
(9) ►  - 0.08% (3)
least cost - 0.08% (3)
to create - 0.08% (3)
posted by - 0.08% (3)
thisblogthis!share to - 0.08% (3)
twittershare to - 0.08% (3)
on table - 0.08% (3)
facebookshare to - 0.08% (3)
pinterest labels: - 0.08% (3)
here is - 0.08% (3)
performance tuning - 0.08% (3)
cost plan - 0.08% (3)
the query - 0.08% (3)
►  july - 0.08% (3)
data skew. - 0.08% (3)
this blog - 0.08% (3)
february (1) - 0.08% (3)
p_sel_get_stu_name 'bradley' - 0.08% (3)
december (2) - 0.08% (3)
from dbo.students - 0.08% (3)
november (2) - 0.08% (3)
will have - 0.08% (3)
the sql - 0.08% (3)
t-sql tables - 0.08% (3)
a demo - 0.08% (3)
the high - 0.08% (3)
and be - 0.08% (3)
that you - 0.08% (3)
to maintain - 0.08% (3)
some of - 0.08% (3)
meeting the - 0.08% (3)
ha was - 0.08% (3)
to give - 0.08% (3)
a good - 0.08% (3)
amount of - 0.08% (3)
there may - 0.08% (3)
make sure - 0.08% (3)
a system - 0.08% (3)
you may - 0.08% (3)
and business - 0.08% (3)
solution · - 0.08% (3)
a database - 0.08% (3)
asked a - 0.08% (3)
the three - 0.08% (3)
of your - 0.05% (2)
access ddl - 0.05% (2)
of tables - 0.05% (2)
objective. this - 0.05% (2)
allows us - 0.05% (2)
in-memory oltp/hekaton - 0.05% (2)
robert dorr - 0.05% (2)
in-memory table - 0.05% (2)
point dear - 0.05% (2)
this may - 0.05% (2)
could a - 0.05% (2)
"so balls", - 0.05% (2)
you say, - 0.05% (2)
asked about - 0.05% (2)
an existing - 0.05% (2)
number of - 0.05% (2)
maximum number - 0.05% (2)
plan based - 0.05% (2)
type of - 0.05% (2)
use the - 0.05% (2)
that we - 0.05% (2)
time to - 0.05% (2)
the amount - 0.05% (2)
'bradley'; exec - 0.05% (2)
p_sel_get_stu_name 'segarra'; - 0.05% (2)
the execution - 0.05% (2)
– recovery - 0.05% (2)
create the - 0.05% (2)
data that - 0.05% (2)
we used - 0.05% (2)
always dear - 0.05% (2)
and bob - 0.05% (2)
in sql - 0.05% (2)
had written - 0.05% (2)
the maximum - 0.05% (2)
the complexity - 0.05% (2)
the access - 0.05% (2)
for an - 0.05% (2)
we execute - 0.05% (2)
he was - 0.05% (2)
i’m going - 0.05% (2)
january (1) - 0.05% (2)
it and - 0.05% (2)
of how - 0.05% (2)
business. a - 0.05% (2)
october (5) - 0.05% (2)
and then - 0.05% (2)
point of - 0.05% (2)
this in - 0.05% (2)
understand what - 0.05% (2)
use of - 0.05% (2)
disaster recovery - 0.05% (2)
a great - 0.05% (2)
march (1) - 0.05% (2)
sql server. - 0.05% (2)
december (1) - 0.05% (2)
part 1: - 0.05% (2)
(3) ►  - 0.05% (2)
and budget. - 0.05% (2)
are we - 0.05% (2)
reader. the - 0.05% (2)
use it - 0.05% (2)
is not - 0.05% (2)
the question - 0.05% (2)
complexity of - 0.05% (2)
depending on - 0.05% (2)
this could - 0.05% (2)
right on - 0.05% (2)
comments: email - 0.05% (2)
may not - 0.05% (2)
them to - 0.05% (2)
the process? - 0.05% (2)
sql live - 0.05% (2)
database administration - 0.05% (2)
virtual chapter - 0.05% (2)
master data - 0.05% (2)
dba virtual - 0.05% (2)
dry erase - 0.05% (2)
you understand - 0.05% (2)
sql internals - 0.05% (2)
the day - 0.05% (2)
with their - 0.05% (2)
the technical - 0.05% (2)
these solutions - 0.05% (2)
solutions will - 0.05% (2)
thank you - 0.05% (2)
a high - 0.05% (2)
dear reader. - 0.05% (2)
brad posted - 0.05% (2)
business needs, - 0.05% (2)
it will - 0.05% (2)
and not - 0.05% (2)
be too - 0.05% (2)
one of - 0.05% (2)
when ha - 0.05% (2)
of this - 0.05% (2)
was in - 0.05% (2)
they ran - 0.05% (2)
less than - 0.05% (2)
increased cpu - 0.05% (2)
for this - 0.05% (2)
balls", you - 0.05% (2)
there an - 0.05% (2)
great question - 0.05% (2)
was needed - 0.05% (2)
been a - 0.05% (2)
in your - 0.05% (2)
we have - 0.05% (2)
there is - 0.05% (2)
a brown - 0.05% (2)
during a - 0.05% (2)
no changes - 0.05% (2)
changes in - 0.05% (2)
leading up - 0.05% (2)
we are - 0.05% (2)
too cold - 0.05% (2)
and now - 0.05% (2)
what a - 0.05% (2)
this has - 0.05% (2)
goal is - 0.05% (2)
one may - 0.05% (2)
and you - 0.05% (2)
lot of - 0.05% (2)
‘best’ quick - 0.05% (2)
we move - 0.05% (2)
way. a - 0.05% (2)
ability to - 0.05% (2)
to technical - 0.05% (2)
you are - 0.05% (2)
options to - 0.05% (2)
13,843 rows - 0.05% (2)
e.courseid = - 0.05% (2)
as begin - 0.05% (2)
select s.firstname - 0.05% (2)
,s.lastname ,c.coursename - 0.05% (2)
· cost - 0.05% (2)
s left - 0.05% (2)
join enrollment - 0.05% (2)
s.studentid=e.studentid left - 0.05% (2)
join courses - 0.05% (2)
c.courseid where - 0.05% (2)
create procedure - 0.05% (2)
query and - 0.05% (2)
our query - 0.05% (2)
with recompile; - 0.05% (2)
it managers. - 0.05% (2)
working with - 0.05% (2)
the second - 0.05% (2)
blackout window - 0.05% (2)
p_sel_get_stu_name 'bradley'; - 0.05% (2)
three bears - 0.05% (2)
p_sel_get_stu_name(@lname varchar(50)) - 0.05% (2)
end go - 0.05% (2)
terms that - 0.05% (2)
different last - 0.05% (2)
the difference - 0.05% (2)
does this - 0.05% (2)
query plans. - 0.05% (2)
skew we - 0.05% (2)
more common - 0.05% (2)
with it - 0.05% (2)
it does - 0.05% (2)
for it - 0.05% (2)
i have - 0.05% (2)
that every - 0.05% (2)
begin drop - 0.05% (2)
size of - 0.05% (2)
names. if - 0.05% (2)
make a - 0.05% (2)
our first - 0.05% (2)
name of - 0.05% (2)
students will - 0.05% (2)
exists(select name - 0.05% (2)
from sys.procedures - 0.05% (2)
where name='p_sel_get_stu_name') - 0.05% (2)
for over - 0.05% (2)
the first query - 0.11% (4)
optimize for unknown - 0.11% (4)
high availability conversation - 0.11% (4)
business and it - 0.11% (4)
in this case - 0.11% (4)
hello dear reader! - 0.08% (3)
to facebookshare to - 0.08% (3)
thisblogthis!share to twittershare - 0.08% (3)
by bradley ball - 0.08% (3)
for stopping by. - 0.08% (3)
this is the - 0.08% (3)
stopping by. thanks, - 0.08% (3)
along the way. - 0.08% (3)
exec p_sel_get_stu_name 'bradley' - 0.08% (3)
to twittershare to - 0.08% (3)
facebookshare to pinterest - 0.08% (3)
there may be - 0.08% (3)
this is a - 0.08% (3)
the high availability - 0.08% (3)
bradley ball at - 0.08% (3)
►  december (2) - 0.08% (3)
►  june (1) - 0.08% (3)
►  november (2) - 0.08% (3)
technical solution · - 0.08% (3)
i had written - 0.05% (2)
join courses c - 0.05% (2)
p_sel_get_stu_name 'bradley'; exec - 0.05% (2)
of data skew - 0.05% (2)
if exists(select name - 0.05% (2)
from sys.procedures where - 0.05% (2)
name='p_sel_get_stu_name') begin drop - 0.05% (2)
procedure p_sel_get_stu_name end - 0.05% (2)
go create procedure - 0.05% (2)
p_sel_get_stu_name(@lname varchar(50)) as - 0.05% (2)
begin select s.firstname - 0.05% (2)
,s.lastname ,c.coursename from - 0.05% (2)
dbo.students s left - 0.05% (2)
join enrollment e - 0.05% (2)
on s.studentid=e.studentid left - 0.05% (2)
►  july (9) - 0.05% (2)
from the sql - 0.05% (2)
►  october (5) - 0.05% (2)
the maximum number - 0.05% (2)
►  january (1) - 0.05% (2)
"so balls", you - 0.05% (2)
on e.courseid = - 0.05% (2)
c.courseid where lastname=@lname - 0.05% (2)
plan based on - 0.05% (2)
►  february (1) - 0.05% (2)
►  may (2) - 0.05% (2)
brad posted by - 0.05% (2)
►  december (1) - 0.05% (2)
comments: email thisblogthis!share - 0.05% (2)
allows us to - 0.05% (2)
in-memory oltp/hekaton tables - 0.05% (2)
s.firstname ,s.lastname ,c.coursename - 0.05% (2)
= c.courseid where - 0.05% (2)
the amount of - 0.05% (2)
leading up to - 0.05% (2)
‘best’ quick solution. - 0.05% (2)
dear reader. the - 0.05% (2)
solutions will be - 0.05% (2)
solution · cost - 0.05% (2)
the three bears - 0.05% (2)
of these solutions - 0.05% (2)
that can be - 0.05% (2)
there is a - 0.05% (2)
between the business - 0.05% (2)
the complexity of - 0.05% (2)
make sure you - 0.05% (2)
of the day - 0.05% (2)
the business and - 0.05% (2)
with the business. - 0.05% (2)
this in a - 0.05% (2)
it is the - 0.05% (2)
no changes can - 0.05% (2)
can be made - 0.05% (2)
c on e.courseid - 0.05% (2)
drop procedure p_sel_get_stu_name - 0.05% (2)
left join courses - 0.05% (2)
e on s.studentid=e.studentid - 0.05% (2)
left join enrollment - 0.05% (2)
from dbo.students s - 0.05% (2)
conversation part 1: - 0.05% (2)
as begin select - 0.05% (2)
procedure p_sel_get_stu_name(@lname varchar(50)) - 0.05% (2)
end go create - 0.05% (2)
where name='p_sel_get_stu_name') begin - 0.05% (2)
depending on the - 0.05% (2)
name from sys.procedures - 0.05% (2)
data skew we - 0.05% (2)
as always dear - 0.05% (2)
balls", you say, - 0.05% (2)
thanks, brad posted - 0.05% (2)
when ha was - 0.05% (2)
i’m going to - 0.05% (2)
goal is to - 0.05% (2)
►  march (1) - 0.05% (2)

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved. FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.