Programming With Sangani

Manually Rebuild Indexing   Indexes can be rebuilt/reorganize in SQL Server Management Studio using the following steps; 1- In Object Explorer locate the table that holds the intended index and expand it. 2- Expand Indexes. 3- Right-click on the index and click on Rebuild or Reorganize. Rebuild All Table Indexing By Script Try the following script: Exec sp_msforeachtable 'SET QUOTED_IDENTIFIER ON; ALTER INDEX ALL ON ? REBUILD' GO Also I prefer(After a long search) to use the following script, it contains  @fillfactor  determines how much percentage of the space on each leaf-level page is filled with data. DECLARE @TableName VARCHAR ( 255 ) DECLARE @sql NVARCHAR( 500 ) DECLARE @fillfactor INT SET @fillfactor = 80 DECLARE TableCursor CURSOR FOR SELECT QUOTENAME(OBJECT_SCHEMA_NAME([object_id])) + '.' + QUOTENAME(name) AS TableName FROM sys.tables OPEN TableCursor FETCH NEXT FROM TableCursor INTO @TableName WHILE @ @FETCH _STATUS = 0 BEGIN SET

  Issue SQL Queries taking longer than normal to complete. Cause when a database is frequently updated via INSERT, UPDATE, or DELETE statements, over time these modifications can cause the information in the index to become scattered in the database (fragmented). Fragmentation exists when indexes have pages in which the logical ordering, based on the key value, does not match the physical ordering inside the data file. If database indexes are fragmented, the SQL Server query optimizer may choose a non-optimal execution plan when using an index to resolve a query. Heavily fragmented indexes can degrade query performance and cause your application to respond slowly. Resolution *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.* The following is a simple query that will list every index on every table in your database, ordered by the

  ASP.NET Web API   is a great tool for building HTTP services with ASP.NET. It makes many things HTTP that used to be ill defined in .NET easy and allows you to build a variety of services very easily. Like other complex abstraction frameworks it makes complex scenarios super easy, while some very simple and common operations are not quite as straight forward or as transparent as they should be.   Capturing the raw Request Body But things are not so easy and transparent when you want to pass simple parameters like strings, numbers, dates etc. Because Web API is based on a host of conventions, some things that should be easy, such as easily picking up the raw content of a POST or PUT operation and capturing it, aren't quite so transparent as the automatic type mapping shown above. One thing you might expect to be able to easily do, is to pick up the entire content body and map it to a parameter like this: [ HttpPost ]         public string PostRawBuffer( strin