Likes : Having a stored procedure that attempts to do everything, as in the whole CRUD salad. Dislikes : Having to create lots of separate stored procedures if I can the first option is feasible. Thank God for dynamic queries for that. /* * Name : MY_LAZY_SP * Purpose : multiple crud operations for group...
In one of the website I have developed, we feature random products displayed on a webpart. This can be done several ways either of the code behind or via t-sql but I think the simplest way to do it is via t-sql with the help of Guid columns. Globally Unique Identifier or GUID is a randomly generated...
I previously posted my views regarding @@IDENTITY variable and SCOPE_IDENTITY() functions in sql server here and luckily with the single stored procedure in our project using NHibernate, i was able to revisit some of its definitions. My teammate whom i asked help from in developing the said stored procedure...
i previously have an experience on debugging stored procedures especially those that involve dynamic sql generation and execution. my experience told me that debugging stored procedure of this type is better with visual studio compared to query analyzer. i encountered a problem with query analyzer before...
When you are developing software product to be catered to diverse customers, it must be a standard to localized your software. With .NET this has never been easy, on .NET 2.0 its even easier with striongly typed resource files. But localizing application must be part of the architectture and should not...
Posted to
Rodel E. Dagumampan
by
rdagumampan
on
11-07-2006
Filed under:
Filed under: .NET, sql server , ASP.NET, usability and design, Development Process, how to, L10N, localization, scripts, stored procedures, user interface, sql, sequel server
I have been wanting to put stored procedures in our current project under source control. Although changes to SPs will be minimal, we all know what we can get when we keep history of parts of our code and the ease of comparing them side by side. Searching usenet as usual, it brought me to this KB: How...