2.54 score from hupso.pl for:
alexpierre.com



HTML Content


Titlepierrekiroule consulting

Length: 24, Words: 2
Description pusty

Length: 0, Words: 0
Keywords pusty
Robots
Charset UTF-8
Og Meta - Title exist
Og Meta - Description exist
Og Meta - Site name exist
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 2571
Text/HTML 25.41 %
Headings H1 1
H2 7
H3 8
H4 0
H5 0
H6 0
H1
pierrekiroule consulting
H2
welcome!
edocs document number file name converter
fast switching users in content server demo site
recursive queries with hierarchical result using sql server
excel macro n00b
creating cascading attributes with open text content server
list the content of a folder in mac os x
H3
step 1: setting up the look-up tables with the data from above (sql server code / transact-sql):
step 2: fixing a “table key lookup” attribute type shortcoming:
step 3: creating the country and city category:
random posts
tag cloud
categories
archives
meta
H4
H5
H6
strong
country_codecountry_encountry_fr cnchinachine degermanyallemagne bebelgiumbelgique
country_codecity_codecity_encity_fr cnbjbeijingpékin cngzguangzhoucanton cnshshanghaishanghaï defrfrankfurtfrancfort dehahamburghambourg debeberlinberlin bebxbrusselbruxelles benanamurnamur begnghentgent
b
i
em
Bolds strong 2
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 pusty
Pliki zewnętrzne 20
Pliki CSS 4
Pliki javascript 16
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 103
Linki wewnętrzne 4
Linki zewnętrzne 99
Linki bez atrybutu Title 78
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

javascript:void(0);
- ?lan=english
- ?lan=french
top #

Linki zewnętrzne

pierrekiroule consulting http://pierrekiroule.com/
home http://pierrekiroule.com/
about http://pierrekiroule.com/?page_id=2
welcome! http://pierrekiroule.com/?p=1
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=1#respond
you can check my linkedin resume and connect to me here (link opens a new window). http://www.linkedin.com/in/apierre
uncategorized http://pierrekiroule.com/?cat=1
edocs document number <--> file name converter http://pierrekiroule.com/?p=236
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=236#respond
ecm http://pierrekiroule.com/?cat=7
tech tips http://pierrekiroule.com/?cat=5
fast switching users in content server demo site http://pierrekiroule.com/?p=209
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=209#respond
- http://pierrekiroule.com/wp-content/uploads/2014/11/screen-shot-2014-11-24-at-10.59.15-am.png
- http://pierrekiroule.com/wp-content/uploads/2014/11/screen-shot-2014-11-24-at-11.04.38-am.png
retrieve some users icons https://duckduckgo.com/?q=user+icons
ecm http://pierrekiroule.com/?cat=7
tech tips http://pierrekiroule.com/?cat=5
content server http://pierrekiroule.com/?tag=content-server
otcs http://pierrekiroule.com/?tag=otcs
recursive queries with hierarchical result using sql server http://pierrekiroule.com/?p=184
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=184#respond
tech tips http://pierrekiroule.com/?cat=5
connect by http://pierrekiroule.com/?tag=connect-by
hierarchy http://pierrekiroule.com/?tag=hierarchy
recursive http://pierrekiroule.com/?tag=recursive
sql http://pierrekiroule.com/?tag=sql
sql server http://pierrekiroule.com/?tag=sql-server
excel macro n00b http://pierrekiroule.com/?p=168
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=168#respond
- http://pierrekiroule.com/wp-content/uploads/2013/12/excel-macro-1.jpg
- http://pierrekiroule.com/wp-content/uploads/2013/12/excel-macro-2.jpg
tech tips http://pierrekiroule.com/?cat=5
creating cascading attributes with open text content server http://pierrekiroule.com/?p=126
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=126#respond
- http://pierrekiroule.com/wp-content/uploads/2012/01/2_add_category.jpg
- http://pierrekiroule.com/wp-content/uploads/2012/01/4_country_attribute_def.jpg
- http://pierrekiroule.com/wp-content/uploads/2012/01/5_city_attribute_def.jpg
- http://pierrekiroule.com/wp-content/uploads/2012/01/6_testing.jpg
ecm http://pierrekiroule.com/?cat=7
tech tips http://pierrekiroule.com/?cat=5
list the content of a folder in mac os x http://pierrekiroule.com/?p=119
alex http://pierrekiroule.com/?author=2
no comments http://pierrekiroule.com/?p=119#respond
creating a “print to file” folder service with automator http://www.youtube.com/watch?v=jyye9rd8smo
creating a “print to file” folder service with automator http://pierrekiroule.com/wp-content/uploads/2011/04/print_folder_service.mov
tech tips http://pierrekiroule.com/?cat=5
older entries http://pierrekiroule.com/?paged=2
rss http://pierrekiroule.com/?feed=rss2
bi vs enterprise search http://pierrekiroule.com/?p=94
a little bit about pierrekiroule consulting… http://pierrekiroule.com/?p=6
welcome! http://pierrekiroule.com/?p=1
asking the right questions http://pierrekiroule.com/?p=18
internet bandwidth cap… http://pierrekiroule.com/?p=110
bi http://pierrekiroule.com/?tag=bi
connect by http://pierrekiroule.com/?tag=connect-by
content server http://pierrekiroule.com/?tag=content-server
convergence http://pierrekiroule.com/?tag=convergence
dm http://pierrekiroule.com/?tag=dm
ecm http://pierrekiroule.com/?tag=ecm
hierarchy http://pierrekiroule.com/?tag=hierarchy
install http://pierrekiroule.com/?tag=install
nuxeo http://pierrekiroule.com/?tag=nuxeo
otcs http://pierrekiroule.com/?tag=otcs
recursive http://pierrekiroule.com/?tag=recursive
sql http://pierrekiroule.com/?tag=sql
sql server http://pierrekiroule.com/?tag=sql-server
structured http://pierrekiroule.com/?tag=structured
unstructured http://pierrekiroule.com/?tag=unstructured
bi thoughts http://pierrekiroule.com/?cat=3
ecm http://pierrekiroule.com/?cat=7
humor http://pierrekiroule.com/?cat=14
tech tips http://pierrekiroule.com/?cat=5
uncategorized http://pierrekiroule.com/?cat=1
march 2017 http://pierrekiroule.com/?m=201703
november 2014 http://pierrekiroule.com/?m=201411
february 2014 http://pierrekiroule.com/?m=201402
december 2013 http://pierrekiroule.com/?m=201312
january 2012 http://pierrekiroule.com/?m=201201
april 2011 http://pierrekiroule.com/?m=201104
september 2010 http://pierrekiroule.com/?m=201009
april 2010 http://pierrekiroule.com/?m=201004
november 2009 http://pierrekiroule.com/?m=200911
october 2009 http://pierrekiroule.com/?m=200910
april 2009 http://pierrekiroule.com/?m=200904
march 2009 http://pierrekiroule.com/?m=200903
february 2009 http://pierrekiroule.com/?m=200902
january 2009 http://pierrekiroule.com/?m=200901
log in http://pierrekiroule.com/wp-login.php
wordpress http://wordpress.org/
neoease http://www.neoease.com/
xhtml 1.1 http://validator.w3.org/check?uri=referer
css 3 http://jigsaw.w3.org/css-validator/check/referer?profile=css3

Zdjęcia

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

Zdjęcia bez atrybutu TITLE

http://pierrekiroule.com/wp-content/plugins/jlanguage/icons/en.png
http://pierrekiroule.com/wp-content/plugins/jlanguage/icons/fr.png
http://pierrekiroule.com/wp-content/uploads/2014/11/screen-shot-2014-11-24-at-10.59.15-am-300x114.png
http://pierrekiroule.com/wp-content/uploads/2014/11/screen-shot-2014-11-24-at-11.04.38-am-300x35.png
http://pierrekiroule.com/wp-content/uploads/2013/12/excel-macro-1.jpg
http://pierrekiroule.com/wp-content/uploads/2013/12/excel-macro-2.jpg

Zdjęcia bez atrybutu ALT

http://pierrekiroule.com/wp-content/uploads/2012/01/1_add_category.jpg
http://pierrekiroule.com/wp-content/uploads/2012/01/2_add_category-300x99.jpg
http://pierrekiroule.com/wp-content/uploads/2012/01/3_add_attribute.jpg
http://pierrekiroule.com/wp-content/uploads/2012/01/4_country_attribute_def-300x264.jpg
http://pierrekiroule.com/wp-content/uploads/2012/01/5_city_attribute_def-300x264.jpg
http://pierrekiroule.com/wp-content/uploads/2012/01/6_testing-300x223.jpg

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

pierrekiroule consulting pragmatic business intelligence for the rest of us home about welcome! january 5th, 2009 alex no comments welcome to pierrekiroule consulting! i share here with you my experience and findings about business intelligence (bi), document management, or other thoughts, findings and experiences. to contact me, please send me an email at: consultant (at) pierrekiroule (dot) com you can check my linkedin resume and connect to me here (link opens a new window). categories: uncategorized tags: edocs document number file name converter march 1st, 2017 alex no comments proof of concept using html5, javascript and css. ! javascript is not enabled. edocs document # file name edocs document number: version number: extension (2 to 4 characters): file name (enhanced, "!"): file name (unix, "_"): type or paste a file name: categories: ecm, tech tips tags: fast switching users in content server demo site november 24th, 2014 alex no comments in content server, some settings are applied at a user level by the administrator. for instance, the access controls on the content, or the ability to create more or less type of objects in the system. in order to quickly test or demonstrate this, it is convenient to switch from one user (with administrative rights) to other users showing the applied settings. here is one convenient way to do this using a custom view on the front page (enterprise workspace): fast switching users in content server first, you need to enable “allow log-in via http get request” under “server configuration > configure security parameters > log-in connection policies” in the admin pages. this may not work in a production environment for security purpose, but is acceptable in a demo or development environment: http get request also, your environment must be using the content server internal authentication (or use a backdoor to access internal accounts on your server) for this switching to work. next, you may want to retrieve some users icons to use on the top row of the custom view (optional). i chose icons with a similar look and feel, and with a 64×64 size. you will save these icons in a location that is mapped in your content server site: by default, the “http://servername/img/” is mapped to the “..opentext/support” folder, so you could use this to save your icons in a subfolder within the “support” folder. check the proper mapping (if different than “img”), and, save the icons in a folder named: “..opentext/support/appearances/users/” you will also need to create and know the users needed for switching, together with their passwords (which will be visible to everyone, thus, making this method unsafe for a production environment) then you need to create a text file which will be used to build a custom view with the following code, using the “ll.login” function to pass the user name and password, and bypass the login screen of content server:

admin john doe
admin john doe
the first row () is for the icons, and the second row displays the text. replace the values between “<>” such as server name, passwords and user names with actual values, and also check for the image (icons) mapping, as well as the instance name (otcs in this case, seen both in the beginning of the url and in the nexturl tag). add as many (cells) in each row of the table as you need users to switch. create a customview in the enterprise workspace using this text file and test it. ensure the custom view has proper permissions to allow all users to see and use it. when your user switching works, you can then hide this custom view from the enterprise workspace. categories: ecm, tech tips tags: content server, otcs recursive queries with hierarchical result using sql server february 10th, 2014 alex no comments recursive queries are not commonly used, yet they are very useful to display hierarchical data stored in flat tables. unlike the “connect by” statement in oracle, sql server doesn’t provide an easy answer to build them. here is a way to solve this with sql server, found after a bit of reading. lets use a flat table named “example” containing some hierarchical data with the following column: idnameparentid 1 root name null 2 child1 1 3 child2 1 4 grandchild1 2 5 crandchild2 2 6 grandchild1 3 in this table, any row can have a parent (except the root one), and therefore a hierarchy view could be created: root: level 1level 2level 3 root name child1 grandchild1 grandchild2 child2 grandchild1 in order to create a query to display this hierarchical view, we first create a recursive source (‘recursive_source’) to provide the expected result. we will need the following 4 columns in our result: id: a unique identifier used for joining itself recursively to the parent id, the name: this is what we want to display in our report, the depth level: to be able to indent the result nicely a sort field: to ensure we display the data in proper hierarchical order 1 2 3 with recursive_source( id, name, depth_level, sort) as ( the first selection is only to get the starting point, the root of our hierarchy (level 1), with the “parent name”: 1 2 3 4 5 6 7 8 9 10 11 select    root.id, convert(varchar(255), root.name), /* the name, we need no discrepancy in the column type so we convert this into varchar */ 1, /* depth level: this is the first iteration, therefore we set it at level 1 */ convert(varchar(255), root.name) /* we will start with the parent name for sorting our output */ from example as root /* we name this first iteration table "root" */ where root.id = /* either know the parent id, or prompt users to select where they would like to start the hierarchical report from */ this is where we create the recursive query 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 union all select    iteration.id, convert(varchar(255), replicate('|---', depth_level) + iteration.name), /* add "|---" as many time as depth_level (= replicate) in front of the name, this creates a natural indentation of the result */ depth_level + 1,  /* increment depth_level for next iteration */ convert(varchar(255), rtrim(sort) + '|---' + iteration.name) /* append the new name at the end of the sort field + "|---" to keep the hierarchical order of the data as previous level are in front of the name */ from example as iteration, recursive_source /* the source is recursively queried */ where recursive_source.id = iteration.parentid ) then create the select statement which will display the sorted recursive result with hierarchical indentation: 1 2 3 4 5 select name 'hierarchical structure' from recursive_source order by sort here is the full query in one block an no comment: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 with recursive_source( id, name, depth_level, sort) as (select  root.id, convert(varchar(255), root.name), 1, convert(varchar(255), root.name) from example as root where root.id = union all select    iteration.id, convert(varchar(255), replicate('|---', depth_level) + iteration.name), depth_level + 1, convert(varchar(255), rtrim(sort) + '|---' + iteration.name) from example as iteration, recursive_source where recursive_source.id = iteration.parentid ) select name 'hierarchical structure' from recursive_source order by sort categories: tech tips tags: connect by, hierarchy, recursive, sql, sql server excel macro n00b december 10th, 2013 alex no comments i just got tired and lazy while formating a report in excel. instead of manually clean the same rows more than 1100 times, i thought i’d better use my time creating a macro to automate the process… all i wanted to do was to cut and paste a cell, and delete 3 rows, then repeat: move the cell to the right of the name (cut and paste it 2 rows above and one column right): delete empty rows (rows 3, 4 and 5 in the example above), and repeat this 1100 times: so this is my extremely basic macro for doing this: 1 2 3 4 5 6 7 8 9 10 11 sub move_action() ' move_action macro ' keyboard shortcut: ctrl+shift+a do while instr(activecell.value, "action") > 0 activecell.cut destination:=activecell.offset(-2, 1) activesheet.range(activecell.offset(-1, 0).entirerow, activecell.offset(1, 0).entirerow).delete activecell.offset(1, 0).select loop end sub i then just selected the first “action” cell, and ran the macro, watching excel (slowly) do the work for me while i was eating my lunch 🙂 categories: tech tips tags: creating cascading attributes with open text content server january 23rd, 2012 alex no comments “categories and attributes” in open text content server is a nice way to add customized metadata to your content stored in the system. if you want to have “cascading” attributes, for instance “country >> city”, where you will only display the list of cities within the selected country, you need to use some look-up tables and a bit of sql. here is an example of how you can implement this, with one pitfall and how you can avoid it. we will use the following sample data: countries: country_codecountry_encountry_fr cn china chine de germany allemagne be belgium belgique cities: country_codecity_codecity_encity_fr cn bj beijing pékin cn gz guangzhou canton cn sh shanghai shanghaï de fr frankfurt francfort de ha hamburg hambourg de be berlin berlin be bx brussel bruxelles be na namur namur be gn ghent gent step 1: setting up the look-up tables with the data from above (sql server code / transact-sql): create the countries table: 1 2 3 4 5 6 7 8 9 create table cat_country( [country_code] [nchar](10) null, [country_en] [nchar](255) null, [country_fr] [nchar](255) null ) on [primary] populate the countries table: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 insert into cat_country( [country_code] ,[country_en] ,[country_fr]) values ('cn','china','chine'), ('de','germany','allemagne'), ('be','belgium','belgique') go create the cities table: 1 2 3 4 5 6 7 8 9 10 11 create table cat_city( [country_code] [nchar](10) null, [city_code] [nchar](10) null, [city_en] [nchar](255) null, [city_fr] [nchar](255) null ) on [primary] populate the cities table: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 insert into cat_city( [country_code] ,[city_code] ,[city_en] ,[city_fr]) values ('cn','bj','beijing','pékin'), ('cn','gz','guangzhou','canton'), ('cn','sh','shanghai','shanghaï'), ('de','fr','frankfurt','francfort'), ('de','ha','hamburg','hambourg'), ('de','be','berlin','berlin'), ('be','bx','brussel','bruxelles'), ('be','na','namur','namur'), ('be','gn','ghent','gent') go step 2: fixing a “table key lookup” attribute type shortcoming: the sql code provided in the “table key lookup” can’t be more than 255 characters, and must be very simple. as we would like to combine and display in our look-up values the english and french description, and in order to keep the select statements simple in the attribute definition, we will then create 2 views from our previous tables as follow: create country_view: 1 2 3 4 5 6 7 select distinct rtrim(country_en) + ' - ' + rtrim(country_fr) as country_desc from cat_country order by country_desc create city_view: 1 2 3 4 5 6 7 8 9 10 11 12 13 select distinct rtrim(dbo.cat_country.country_en) + ' - ' + rtrim(dbo.cat_country.country_fr) as country_desc, rtrim(dbo.cat_city.city_en) + ' - ' + rtrim(dbo.cat_city.city_fr) as city_desc, from cat_city inner join cat_country on dbo.cat_city.country_code = dbo.cat_country.country_code order by country_desc, city_desc step 3: creating the country and city category: in the content server categories volume, create a new category named “country and city” from the “add item” menu: click on the newly created category name to edit it. in the “add attribute” drop down menu, select “text: table key lookup” to create the “country” attribute: name it “country” and use the following settings: the “custom sql statement” box should be checked in order to edit the “values” box where we will add the sql statement to query the list of available countries in our look-up table: use the following simple select statement to retrieve the list of available countries from the look-up table: 1  select country_desc from country_view create the “city” attribute in the same way (except that this one may not be required, and display it after “country”), and with the following sql select statement to retrieve the list of cities based on the selected country: 1 select city_desc from city_view where country_desc = then, test your newly created category by selecting first a country, and then display the available cities you can select: categories: ecm, tech tips tags: list the content of a folder in mac os x april 14th, 2011 alex no comments the little utility i used to “print” the content of a folder or volume into a text file (for instance to save the list of all movies in a folder) didn’t work in snow leopard (mac os x 10.6) anymore, so i looked for an other way of doing it. while not as complete as the utility (printfinder, no longer available or supported) this one was self made and works 🙂 instead of writing how it works, a quick video of creating the service is easier: creating a “print to file” folder service with automator categories: tech tips tags: older entries rss random posts bi vs enterprise searcha little bit about pierrekiroule consulting…welcome!asking the right questionsinternet bandwidth cap… tag cloud bi connect by content server convergence dm ecm hierarchy install nuxeo otcs recursive sql sql server structured unstructured categories bi thoughts ecm humor tech tips uncategorized archives march 2017 november 2014 february 2014 december 2013 january 2012 april 2011 september 2010 april 2010 november 2009 october 2009 april 2009 march 2009 february 2009 january 2009 meta log in top wordpress copyright © pierrekiroule consulting theme by neoease. valid xhtml 1.1 and css 3.


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

Words density analysis:

Numbers of all words: 2299

- 0.13% (3)
start - 0.13% (3)
may - 0.13% (3)
delete - 0.13% (3)
other - 0.13% (3)
step - 0.13% (3)
[nchar](10) - 0.13% (3)
retrieve - 0.13% (3)
like - 0.13% (3)
report - 0.13% (3)
very - 0.13% (3)
also - 0.13% (3)
number - 0.13% (3)
only - 0.13% (3)
   - 0.13% (3)
march - 0.13% (3)
server, - 0.13% (3)
lookup” - 0.13% (3)
november - 0.13% (3)
provide - 0.13% (3)
proper - 0.13% (3)
bit - 0.13% (3)
named - 0.13% (3)
demo - 0.13% (3)
february - 0.13% (3)
settings - 0.13% (3)
ecm, - 0.13% (3)
attributes - 0.13% (3)
than - 0.13% (3)
city_desc - 0.13% (3)
about - 0.13% (3)
selected - 0.13% (3)
paste - 0.13% (3)
which - 0.13% (3)
sub - 0.13% (3)
test - 0.13% (3)
created - 0.13% (3)
indent - 0.13% (3)
simple - 0.13% (3)
above - 0.13% (3)
city” - 0.13% (3)
canton - 0.09% (2)
pékin - 0.09% (2)
shanghaï - 0.09% (2)
guangzhou - 0.09% (2)
shanghai - 0.09% (2)
2010 - 0.09% (2)
beijing - 0.09% (2)
belgique - 0.09% (2)
belgium - 0.09% (2)
allemagne - 0.09% (2)
germany - 0.09% (2)
chine - 0.09% (2)
meta - 0.09% (2)
china - 0.09% (2)
newly - 0.09% (2)
edit - 0.09% (2)
cat_country( - 0.09% (2)
frankfurt - 0.09% (2)
insert - 0.09% (2)
“print - 0.09% (2)
little - 0.09% (2)
service - 0.09% (2)
populate - 0.09% (2)
utility - 0.09% (2)
volume - 0.09% (2)
cat_city( - 0.09% (2)
[country_fr] - 0.09% (2)
quick - 0.09% (2)
[city_code] - 0.09% (2)
self - 0.09% (2)
[city_en] - 0.09% (2)
[city_fr] - 0.09% (2)
“table - 0.09% (2)
[primary] - 0.09% (2)
2011 - 0.09% (2)
francfort - 0.09% (2)
ghent - 0.09% (2)
hamburg - 0.09% (2)
hambourg - 0.09% (2)
brussel - 0.09% (2)
bruxelles - 0.09% (2)
join - 0.09% (2)
box - 0.09% (2)
thoughts - 0.09% (2)
[country_en] - 0.09% (2)
gent - 0.09% (2)
structured - 0.09% (2)
country_desc, - 0.09% (2)
country_view - 0.09% (2)
city_view - 0.09% (2)
distinct - 0.09% (2)
“add - 0.09% (2)
level: - 0.09% (2)
country, - 0.09% (2)
mapping - 0.09% (2)
request - 0.09% (2)
must - 0.09% (2)
internal - 0.09% (2)
top - 0.09% (2)
that - 0.09% (2)
mapped - 0.09% (2)
could - 0.09% (2)
within - 0.09% (2)
know - 0.09% (2)
security - 0.09% (2)
passwords - 0.09% (2)
build - 0.09% (2)
height="64" - 0.09% (2)
">width="64"> - 0.09% (2)
- 0.09% (2)
ensure - 0.09% (2)
allow - 0.09% (2)
see - 0.09% (2)
works, - 0.09% (2)
production - 0.09% (2)
log-in - 0.09% (2)
10th, - 0.09% (2)
javascript - 0.09% (2)
business - 0.09% (2)
intelligence - 0.09% (2)
welcome! - 0.09% (2)
experience - 0.09% (2)
findings - 0.09% (2)
at: - 0.09% (2)
uncategorized - 0.09% (2)
2017 - 0.09% (2)
number: - 0.09% (2)
enable - 0.09% (2)
name: - 0.09% (2)
fast - 0.09% (2)
site - 0.09% (2)
applied - 0.09% (2)
access - 0.09% (2)
system. - 0.09% (2)
this, - 0.09% (2)
convenient - 0.09% (2)
page - 0.09% (2)
queries - 0.09% (2)
they - 0.09% (2)
nice - 0.09% (2)
instead - 0.09% (2)
previous - 0.09% (2)
recursive_source.id - 0.09% (2)
iteration.parentid - 0.09% (2)
'hierarchical - 0.09% (2)
structure' - 0.09% (2)
december - 0.09% (2)
2013 - 0.09% (2)
just - 0.09% (2)
same - 0.09% (2)
field - 0.09% (2)
1100 - 0.09% (2)
cell, - 0.09% (2)
repeat - 0.09% (2)
doing - 0.09% (2)
move_action - 0.09% (2)
activecell.offset(1, - 0.09% (2)
🙂 - 0.09% (2)
cascading - 0.09% (2)
2012 - 0.09% (2)
keep - 0.09% (2)
rtrim(sort) - 0.09% (2)
stored - 0.09% (2)
root.name), - 0.09% (2)
flat - 0.09% (2)
after - 0.09% (2)
have - 0.09% (2)
(except - 0.09% (2)
therefore - 0.09% (2)
recursively - 0.09% (2)
recursive_source( - 0.09% (2)
depth_level, - 0.09% (2)
root.id, - 0.09% (2)
- 0.09% (2)
indentation - 0.09% (2)
id> - 0.09% (2)
would - 0.09% (2)
union - 0.09% (2)
select    - 0.09% (2)
iteration.id, - 0.09% (2)
replicate('|---', - 0.09% (2)
depth_level) - 0.09% (2)
iteration.name), - 0.09% (2)
"|---" - 0.09% (2)
css - 0.09% (2)
- 0.09% (2)
">height="64" width="64"> - 0.09% (2)
as the - 0.09% (2)
and in - 0.09% (2)
as many - 0.09% (2)
content server, - 0.09% (2)
will be - 0.09% (2)
otcs recursive - 0.09% (2)
hierarchical data - 0.09% (2)
stored in - 0.09% (2)
to build - 0.09% (2)
parent id, - 0.09% (2)
display in - 0.09% (2)
used to - 0.09% (2)
a text - 0.09% (2)
hierarchical order - 0.09% (2)
production environment - 0.09% (2)
document number - 0.09% (2)
fast switching - 0.09% (2)
users in - 0.09% (2)
2014 alex - 0.09% (2)
the system. - 0.09% (2)
http get - 0.09% (2)
must be - 0.09% (2)
a production - 0.09% (2)
using the - 0.09% (2)
row of - 0.09% (2)
the custom - 0.09% (2)
your content - 0.09% (2)
to save - 0.09% (2)
know the - 0.09% (2)
the result - 0.09% (2)
recursive_source( id, - 0.09% (2)
id, name, - 0.09% (2)
where recursive_source.id - 0.09% (2)
+ '|---' - 0.09% (2)
the new - 0.09% (2)
sort field - 0.09% (2)
to keep - 0.09% (2)
the hierarchical - 0.09% (2)
as iteration, - 0.09% (2)
= iteration.parentid - 0.09% (2)
depth_level + - 0.09% (2)
) then - 0.09% (2)
name 'hierarchical - 0.09% (2)
structure' from - 0.09% (2)
recursive_source order - 0.09% (2)
by sort - 0.09% (2)
with recursive_source( - 0.09% (2)
convert(varchar(255), rtrim(sort) - 0.09% (2)
in front - 0.09% (2)
name, depth_level, - 0.09% (2)
first iteration - 0.09% (2)
sort) as - 0.09% (2)
convert(varchar(255), root.name), - 0.09% (2)
/* the - 0.09% (2)
depth level: - 0.09% (2)
*/ convert(varchar(255), - 0.09% (2)
as root - 0.09% (2)
*/ where - 0.09% (2)
+ iteration.name), - 0.09% (2)
root.id = - 0.09% (2)
- 0.09% (2)
like to - 0.09% (2)
where we - 0.09% (2)
all select    - 0.09% (2)
iteration.id, convert(varchar(255), - 0.09% (2)
and css - 0.09% (2)

One word

Two words phrases

Three words phrases

the - 6.18% (142)
name - 2.22% (51)
and - 2.09% (48)
country - 1.87% (43)
use - 1.78% (41)
able - 1.26% (29)
our - 1.17% (27)
server - 1.17% (27)
user - 1.13% (26)
city - 1.13% (26)
this - 1.04% (24)
you - 1% (23)
select - 1% (23)
with - 0.96% (22)
create - 0.96% (22)
table - 0.96% (22)
for - 0.91% (21)
recursive - 0.78% (18)
level - 0.74% (17)
from - 0.74% (17)
ran - 0.74% (17)
here - 0.74% (17)
root - 0.7% (16)
com - 0.7% (16)
content - 0.65% (15)
are - 0.65% (15)
sql - 0.61% (14)
code - 0.61% (14)
work - 0.61% (14)
view - 0.57% (13)
255 - 0.57% (13)
iteration - 0.57% (13)
pass - 0.57% (13)
all - 0.52% (12)
row - 0.52% (12)
will - 0.48% (11)
users - 0.48% (11)
otcs - 0.48% (11)
source - 0.48% (11)
order - 0.43% (10)
look - 0.43% (10)
cell - 0.43% (10)
hierarchical - 0.43% (10)
display - 0.43% (10)
text - 0.43% (10)
categories - 0.43% (10)
convert - 0.43% (10)
parent - 0.43% (10)
works - 0.43% (10)
sort - 0.43% (10)
depth - 0.43% (10)
but - 0.39% (9)
file - 0.39% (9)
tag - 0.39% (9)
log - 0.39% (9)
older - 0.39% (9)
recursive_source - 0.39% (9)
one - 0.39% (9)
then - 0.39% (9)
varchar - 0.39% (9)
where - 0.39% (9)
http - 0.39% (9)
admin - 0.39% (9)
set - 0.39% (9)
can - 0.39% (9)
folder - 0.35% (8)
first - 0.35% (8)
custom - 0.35% (8)
need - 0.35% (8)
null - 0.35% (8)
id, - 0.35% (8)
attribute - 0.35% (8)
convert(varchar(255), - 0.35% (8)
depth_level - 0.35% (8)
me, - 0.3% (7)
your - 0.3% (7)
following - 0.3% (7)
example - 0.3% (7)
categories: - 0.3% (7)
next - 0.3% (7)
tags: - 0.3% (7)
switch - 0.3% (7)
cat_country - 0.3% (7)
icons - 0.3% (7)
comments - 0.3% (7)
alex - 0.3% (7)
tech - 0.3% (7)
mac - 0.3% (7)
tips - 0.3% (7)
2009 - 0.3% (7)
statement - 0.3% (7)
data - 0.3% (7)
workspace - 0.3% (7)
eating - 0.26% (6)
country_desc - 0.26% (6)
cat_city - 0.26% (6)
table: - 0.26% (6)
login - 0.26% (6)
any - 0.26% (6)
values - 0.26% (6)
cities - 0.26% (6)
child1 - 0.26% (6)
result - 0.26% (6)
list - 0.26% (6)
add - 0.26% (6)
using - 0.26% (6)
pierrekiroule - 0.22% (5)
- 0.22% (5)
not - 0.22% (5)
it. - 0.22% (5)
way - 0.22% (5)
new - 0.22% (5)
connect - 0.22% (5)
nexturl - 0.22% (5)
ecm - 0.22% (5)
name, - 0.22% (5)
null, - 0.22% (5)
countries - 0.22% (5)
switching - 0.22% (5)
open - 0.22% (5)
look-up - 0.22% (5)
creating - 0.22% (5)
rows - 0.22% (5)
“country - 0.22% (5)
macro - 0.22% (5)
right - 0.22% (5)
tables - 0.17% (4)
into - 0.17% (4)
column - 0.17% (4)
berlin - 0.17% (4)
[nchar](255) - 0.17% (4)
type - 0.17% (4)
query - 0.17% (4)
hierarchy - 0.17% (4)
grandchild1 - 0.17% (4)
child2 - 0.17% (4)
consulting - 0.17% (4)
root.name) - 0.17% (4)
how - 0.17% (4)
end - 0.17% (4)
check - 0.17% (4)
cut - 0.17% (4)
root.id - 0.17% (4)
while - 0.17% (4)
2014 - 0.17% (4)
document - 0.17% (4)
setting - 0.17% (4)
january - 0.17% (4)
time - 0.17% (4)
namur - 0.17% (4)
'|---' - 0.17% (4)
iteration.name) - 0.17% (4)
[country_code] - 0.17% (4)
sort) - 0.17% (4)
key - 0.17% (4)
some - 0.17% (4)
environment - 0.17% (4)
april - 0.17% (4)
enterprise - 0.17% (4)
many - 0.17% (4)
used - 0.17% (4)
more - 0.17% (4)
instance - 0.17% (4)
get - 0.17% (4)
available - 0.17% (4)
category - 0.17% (4)
class="center"> - 0.17% (4)
want - 0.17% (4)
save - 0.17% (4)
was - 0.13% (3)
thought - 0.13% (3)
welcome - 0.13% (3)
excel - 0.13% (3)
move - 0.13% (3)
edocs - 0.13% (3)
“country” - 0.13% (3)
iteration, - 0.13% (3)
front - 0.13% (3)
in the - 0.65% (15)
content server - 0.48% (11)
of the - 0.39% (9)
with the - 0.3% (7)
no comments - 0.3% (7)
tech tips - 0.3% (7)
the following - 0.3% (7)
alex no - 0.3% (7)
tips tags: - 0.26% (6)
create the - 0.26% (6)
sql server - 0.26% (6)
create a - 0.26% (6)
list of - 0.22% (5)
on the - 0.22% (5)
the name - 0.22% (5)
we will - 0.22% (5)
to create - 0.22% (5)
with a - 0.22% (5)
the list - 0.22% (5)
table: 1 - 0.22% (5)
custom view - 0.22% (5)
you can - 0.22% (5)
file name - 0.22% (5)
you need - 0.17% (4)
from example - 0.17% (4)
the first - 0.17% (4)
[nchar](255) null - 0.17% (4)
this is - 0.17% (4)
in our - 0.17% (4)
convert(varchar(255), root.name) - 0.17% (4)
order to - 0.17% (4)
need to - 0.17% (4)
+ iteration.name) - 0.17% (4)
- 0.17% (4)
order by - 0.17% (4)
or the - 0.17% (4)
pierrekiroule consulting - 0.17% (4)
in order - 0.17% (4)
a folder - 0.17% (4)
example as - 0.17% (4)
here is - 0.17% (4)
display the - 0.17% (4)
select statement - 0.17% (4)
the data - 0.13% (3)
key lookup” - 0.13% (3)
to the - 0.13% (3)
to retrieve - 0.13% (3)
want to - 0.13% (3)
ecm, tech - 0.13% (3)
categories: tech - 0.13% (3)
edocs document - 0.13% (3)
which will - 0.13% (3)
[nchar](10) null, - 0.13% (3)
level 1 - 0.13% (3)
way to - 0.13% (3)
the parent - 0.13% (3)
users to - 0.13% (3)
statement to - 0.13% (3)
enterprise workspace - 0.13% (3)
to display - 0.13% (3)
from the - 0.13% (3)
for the - 0.13% (3)
save the - 0.13% (3)
use the - 0.13% (3)
icons in - 0.13% (3)
you will - 0.13% (3)
text file - 0.13% (3)
and use - 0.13% (3)
in content - 0.13% (3)
table key - 0.13% (3)
iteration, recursive_source - 0.09% (2)
the same - 0.09% (2)
how you - 0.09% (2)
'|---' + - 0.09% (2)
creating a - 0.09% (2)
cut and - 0.09% (2)
the selected - 0.09% (2)
bit of - 0.09% (2)
look-up tables - 0.09% (2)
while i - 0.09% (2)
paste a - 0.09% (2)
cell, and - 0.09% (2)
text content - 0.09% (2)
= - 0.09% (2)
1, convert(varchar(255), - 0.09% (2)
instead of - 0.09% (2)
rtrim(sort) + - 0.09% (2)
more than - 0.09% (2)
the look-up - 0.09% (2)
by country_desc - 0.09% (2)
content of - 0.09% (2)
1 select - 0.09% (2)
and with - 0.09% (2)
look-up table: - 0.09% (2)
available countries - 0.09% (2)
retrieve the - 0.09% (2)
of available - 0.09% (2)
sql statement - 0.09% (2)
the “add - 0.09% (2)
to edit - 0.09% (2)
category name - 0.09% (2)
newly created - 0.09% (2)
country and - 0.09% (2)
creating the - 0.09% (2)
country_desc from - 0.09% (2)
the countries - 0.09% (2)
select distinct - 0.09% (2)
keep the - 0.09% (2)
our look-up - 0.09% (2)
cities table: - 0.09% (2)
populate the - 0.09% (2)
on [primary] - 0.09% (2)
null ) - 0.09% (2)
[nchar](255) null, - 0.09% (2)
cat_city( [country_code] - 0.09% (2)
the cities - 0.09% (2)
insert into - 0.09% (2)
[primary] populate - 0.09% (2)
cat_country( [country_code] - 0.09% (2)
create table - 0.09% (2)
where root.id - 0.09% (2)
replicate('|---', depth_level) - 0.09% (2)
depth_level, sort) - 0.09% (2)
the enterprise - 0.09% (2)
the user - 0.09% (2)
alex no comments - 0.3% (7)
tech tips tags: - 0.26% (6)
the list of - 0.22% (5)
from example as - 0.17% (4)
in order to - 0.17% (4)
with the following - 0.13% (3)
categories: ecm, tech - 0.13% (3)
use the following - 0.13% (3)
to create a - 0.13% (3)
ecm, tech tips - 0.13% (3)
you need to - 0.13% (3)
on [primary] populate - 0.09% (2)
recursive_source.id = iteration.parentid - 0.09% (2)
countries table: 1 - 0.09% (2)
'|---' + iteration.name) - 0.09% (2)
[nchar](255) null ) - 0.09% (2)
convert(varchar(255), rtrim(sort) + - 0.09% (2)
open text content - 0.09% (2)
null ) on - 0.09% (2)
the countries table: - 0.09% (2)
cities table: 1 - 0.09% (2)
recursive_source order by - 0.09% (2)
[primary] populate the - 0.09% (2)
to retrieve the - 0.09% (2)
list of available - 0.09% (2)
select statement to - 0.09% (2)
retrieve the list - 0.09% (2)
the content of - 0.09% (2)
of a folder - 0.09% (2)
depth_level + 1, - 0.09% (2)
to keep the - 0.09% (2)
'hierarchical structure' from - 0.09% (2)
display in our - 0.09% (2)
in the system. - 0.09% (2)
switching users in - 0.09% (2)
a production environment - 0.09% (2)
http get request - 0.09% (2)
the content server - 0.09% (2)
in a folder - 0.09% (2)
- 0.09% (2)
the enterprise workspace - 0.09% (2)
2014 alex no - 0.09% (2)
id, name, depth_level, - 0.09% (2)
where recursive_source.id = - 0.09% (2)
sort) as ( - 0.09% (2)
= - 0.09% (2)
the parent id, - 0.09% (2)
union all select    - 0.09% (2)
iteration.id, convert(varchar(255), replicate('|---', - 0.09% (2)
depth_level) + iteration.name), - 0.09% (2)
+ '|---' + - 0.09% (2)
users in content - 0.09% (2)
in front of - 0.09% (2)
a text file - 0.09% (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.