.NET, MVC, C#.NET, ASP.NET , Jquery, SQL, Kendo UI

Kendo Dropdown: getting the selected item You could use the   dataItem   method of the ComboBox/Dropdown to get the model for the selected item. As a side note, the context of the event handler is the ComboBox and it is accessible via   this . E.g. function   change(e) {      var   text =   this .text();      var   value =   this .value();      var   object =   this .dataItem( this .select()); } I hope that this information was helpful for you. I wish you a great day! and another way is : var ddl = $ ( "#ddl" ). data ( "kendoDropDownList" ). dataItem ( $ ( "#ddl" ). data ( "kendoDropDownList" ). select ()). FieldName ; //FieldName is the text field of DataSource --- .DataTextField("FieldName") Ref :  http://www.telerik.com/forums/getting-the-selected-item Ref : http://stackoverflow.com/questions/21600895/how-to-get-dropdowns-selected-items-text-in-kendo-ui  

As the title suggests, this is quite a dirty solution; it’s not as elegant as you expect. The Story: I got a phone call at night (11 PM) from one of my old friends, requesting a hand. He asked me if I could help him with a very strange situation. He was facing a condition where he was not able to delete data from a table. He already tried to TRUNCATE, DELETE and DROP on the table, but still no luck. I demanded him to let me access it; however, he had to say “No” due to security reasons. Even though he really wanted my help, he was not authorized to even let me glance at his screen. After doing some background checks about the problem, I realized that he had open transactions somewhere, and this finally led to the solution of the issue. In his case, there was a transaction which was unnecessarily open, and was actually open for a long time now. It was safe for him to kill the transaction, so he killed it and everything moved on. However, killing transactions can be too damaging

  a DBA and performance tuning consultant, for Ambient Consulting in Minneapolis , I'm often asked to analyze performance issues on a SQL Server instance with which I'm unfamiliar. It can be a daunting task. Let's face it, most of the time companies do not have good documentation about their databases. Or if they do, it is outdated, or it takes a few days to locate and retrieve it. In this article, I share a set of basic scripts that I've developed, over the years, which mine the metadata in the various system functions, stored procedures, tables, catalog views, and dynamic management views, Together, they reveal all the secrets of the databases on the instance, their size, file locations, and their design, including columns, data types, defaults, keys and indexes. If you've been used to retrieving some of this information by clinging to the mouse with whited knuckles and stabbing at the screen, then I hope you'll be pleasantly surprised at the wealth of i