Korayem/sql

From the page: "Have you ever run an update or delete query by mistake and you need to roll back or at least want to know the last run query to fix the problem? The following SQL statement can help in that."

The SQL Server family offers two products suitable for local storage: Microsoft SQL Server Compact 3.5 and Microsoft SQL Server 2005 Express Edition. With the release of SQL Server Compact for desktop scenarios, Microsoft is positioning SQL Server Compact as the default local database. However, both editions are free to download and deploy. Choosing between the SQL Server Express and SQL Server Compact of SQL Server can be difficult because they seem to target the same scenarios. This paper helps developers understand the benefits of each edition and when each edition should be used for local data storage.

From the page: "At Microsoft, we believe that software should provide you with choices that let you find the solution best tailored to your business†needs. To that end, we have redesigned the SQL Server 2005 product family to better meet the needs of each customer segment with four new editions: Express, Workgroup, Standard, and Enterprise. As a low-cost mainstream database, SQL Server 2005 will deliver unprecedented value and functionality compared with competitive solutions. The four new editions will offer a range of features, from high availability and robust scalability to advanced business intelligence tools, designed to empower the people across your organization through a more secure, reliable, and productive data management platform. Additionally, with the reduced application downtime, robust scalability and performance, and tight security controls, SQL Server 2005 represents a dramatic step forward in supporting the most demanding enterprise systems in the world. Because SQL Server is part of Windows Server System, you will also receive the added benefits of reduced total cost of ownership and faster development time through the increased manageability and integration that result from the common engineering strategy implemented across Windows Server System products. The table below presents details about each of the different editions."

From the page: "The following tables specify the maximum sizes and numbers of various objects defined in Microsoft SQL Server 2005 components."

From the page: "A very common question asked on the ASP.NET Forums is how to bind a ListControl's DataTextField or DataValueField to multiple Columns. The ListControl is the base class for controls such as DropDownList, ListBox, RadioButtonList, and CheckBoxList server controls.

One of the ways to do this task will be presented in this Wiki article. The code is shown in both VB.NET and C#.NET."

From the page: "LINQ to Entities allows me to write C# LINQ queries that run against a conceptual data model. This is huge. I cannot stress enough to you how unbelievably forward-thinking and useful it is to be able to run queries against a conceptual object model as opposed to a database schema. The issue that a lot of folks have is in trying to decide if they need to use the Entity Framework or if they are fine with plain-vanilla LINQ to SQL (formerly called DLINQ). The following table provides a summary of the feature set (there is admittedly much more than what I've included in this small table, but this at least made the decision easy for me to make) comparison between the two systems. What you need to realize is that LINQ to Entities is a superset of LINQ to SQL. If the entities you have created in your EDM are backed by a SQL Server 2005 database, LINQ to Entities (L2E for short from now on) will create dynamic SQL statements that connect the entity model with the live database instance and provide your code with results."

From the page: "/* Robyn and Phil feel strongly that there are two striking features in SSMS that extends its usefulness dramatically. The first is the Template, and the second is the powerful functionality hidden by those strange words 'SQLCMD Mode'. Here they try to demonstrate how useful SQLCMD can be to anyone who is tasked with having to administer a database.*/"

You didnt know, now you KNOW!!