Kod günlüğü

- Async example with HttpClient Link - Task Continuations: Checking IsFaulted, IsCompleted, and TaskStatus Link - Postgresql drop index Link - Posgresql' de kullanılmayan veya duplicate indexleri bulmak Link 1: SELECT 2: PSUI.indexrelid::regclass AS IndexName 3: ,PSUI.relid::regclass AS TableName 4: FROM pg_stat_user_indexes AS PSUI 5: JOIN pg_index AS PI 6: ON PSUI.IndexRelid = PI.IndexRelid 7: WHERE PSUI.idx_scan = 0 8: AND PI.indisunique IS FALSE; 1: SELECT 2: indrelid::regclass AS TableName 3: ,array_agg(indexrelid::regclass) AS Indexes 4: FROM pg_index 5: GROUP BY 6: indrelid 7: ,indkey 8: HAVING COUNT(*) > 1; - Postgre servisi ubuntu üzerinde restart etmek Link - Postgre'nin config dosyasını hızlıca bulmak Link - Linux sunucunun ram'ini tespit etmek Link - Linux sunucunun cpu sayısını bulmak Link - Postgre için config ayarlayıcı Link - Postgre için profiler kütü...

- Dotnet core entity framework üzerinde birden fazla sql bağlantısını register etmek için Link - Azure üzerinde indexlerin durumunu kontrol etmek ve yeni indexler oluşturmak için Link 1 Link 2 - Git branch rename etmek için Link - Javascript math.abs() fonksiyonu ne işe yarar Link - Javascript to.fixed() fonksiyonu ne işe yarar Link - Api Key oluşturmak için en iyi yaklaşım önerisi Link - Asp.net mvc textbox input length sınır getirmek Link

What is the difference between Index REBUILD and REORGANIZE and when exactly should you use it Couple of days ago, there was an interesting statement (or rather a question) that was brought up by one of the colleagues in the company. Ultimately, the initial statement left us with one simple question, which is the difference between Index  REBUILD  and  REORGANIZE  and when should you be exactly using it. If you Google the aforementioned, you can find numerous posts/blogs regarding this. Therefore, I will keep things very simple and easier way to understand. Rebuilding an index or reorganizing is required when index fragmentation has reached a considerable percentage. The fragmentation percentage can be identified using the Dynamic Management View - sys.dm_db_index_physical_stats  in SQL Server. You may get more details on the view at the following link: https://msdn.microsoft.com/en-us/library/ms188917.aspx . You can get a list of fragmented indexes ...

HOMEWORK: HOMEWORK 4.3: MAKING THE BLOG FAST (MONGOPROC) Please download the handouts to get started. This assignment requires MongoDB 3.0 or above for your server. In this homework assignment you will be adding some indexes to the post collection to make the blog fast. We have provided the full code for the blog application and you don't need to make any changes, or even run the blog. But you can, for fun. We are also providing a generated data set with 10000 entries with comments and tags. You must load this dataset to complete the problem. Unzip the mongodump handout. You should see a "dump" directory in your working directory; the "dump" directory contains your mongodump. First, begin by dropping your blog database, and loading the sample data and taking a look: echo "db.dropDatabase()" | mongo blog mongorestore dump mongo blog Now your 'blog' database should contain 10,000 blog posts (randomly generated) in the 'posts'...