SQL in the Wild » Blog Archive » Are all updates split into delete-insert?

SQL in the Wild » Blog Archive » Are all updates split into delete-insert?

Interesting post that debunks the myth that ALL updates are split into delete-insert pair.

Changing your culture

I recently noticed that the same ASP.Net application behaves differently in terms of formatting between Windows Server 2003 and Windows Server 2008/Windows 7 for culture en-ZA.

Our application has functionality that exports a gridview to a CSV file, and this is where I picked up something is wrong, the digit separator showed as a  character, which is a unicode character which Excel does not handle well in CSV files.

On Windows Server 2003, the digit grouping symbol is a comma (,), whereas on Server 2008 and Windows 7 it is a unicode space. Apparently someone decided that change was necessary, I found a reference here: http://forums.asp.net/t/1424752.aspx/1

Closed a SQL query by accident? There is help

Have a look at this post: Oh ****! | Home Of The Scary DBA

And this one:

Recover Backed-up query files in SQL Server Management Studio

AuthorizationManager check failed - SOLUTION!

I found a solution to the above problem first mentioned here today by pure chance. Since PowerShell is part of SQL Server 2008 (I think!), I decided to restart SQL Server 2008 on my machine when the error surfaced yet again today, as I was not in the mood for a reboot (too many open files & sessions).

Guess what, the error disappeared! So there must be some tight integration between SQL Server and PowerShell for this to be the solution. 

Please see this post for a repeatable solution.