3,759 reputation
21735
bio website
location Bern, Switzerland
age 49
visits member for 3 years, 9 months
seen 9 hours ago

Note to all SO beginner:

Please read (and embrace!) Jon Skeet's helpful hints on how to write a good question (or at least his short version here ) - one that has a chance that someone can answer it.


A Pascal/Delphi programmer and database freak at heart, I work as a C# developer on line-of-business applications (mostly ASP.NET).

I'm interested mostly in distributed systems (WCF), database (design and SQL), and Active Directory.


I'm an MCPD .NET 4 Web Developer, MCPD .NET 4 Windows Developer, MCPD Enterprise Application Developer (.NET 3.5), and MCTS for WCF, ADO.NET, Winforms and ASP.NET.


Oct
4
revised Recover oracle 10g database from old data files
added 2 characters in body; edited title
Oct
3
revised bulk insert not working in stored proc when using exec
added 69 characters in body
Oct
3
revised Move SQL Server 2008 database from machine A to B with no downtime
Product is officially called "SQL Server" - neither MSSQL, nor MS SQL, nor MS-SQL or anything like that....
Oct
3
revised Performance: order of tables in joined statement
added 43 characters in body; edited title
Oct
3
comment How to remove diacritics in computed persisted columns? COLLATE is non-deterministic and cannot be used
Well, you could create an INSERT and an UPDATE trigger on that table to just simply populate a "normal" column that contains no special characters ...
Oct
3
revised SQL Server agent option in SQL Server Express
added 4 characters in body; edited title
Oct
3
comment message table schema - body TEXT or varchar
Depends on the concrete database you're using.... MySQL? Postgres? SQL Server? For SQL Server, Text and NText are deprecated and should not be used anymore
Oct
3
revised How to remove diacritics in computed persisted columns? COLLATE is non-deterministic and cannot be used
edited tags
Oct
3
comment Composite Primary Key efficiency as a Foreign Key
I personally would almost always use a surrogate key (e.g. an INT IDENTITY) in such a case - makes referencing and joining that table just soooooo much easier. To avoid duplicates, put a UNIQUE constraint on those four columns. Also: narrow primary keys are much better for performance reasons (if they're used as clustering key)
Oct
1
revised Inserting Records - How to get next incremented PK for each insert
added 9 characters in body
Oct
1
revised How to set identity_insert to on in SQL Server
deleted 5 characters in body; edited title
Oct
1
revised Unattended SQL install on a remote machine
added 22 characters in body
Sep
30
revised SQL Server Client configuration via file
added 5 characters in body; edited title
Sep
27
revised How to interpret and modify a dBase (.dbf) file?
added 25 characters in body; edited title
Sep
27
comment Xml stored as varbinary
The XML datatype is highly preferable - it stores the XML in a tokenized, optimized fashion and thus uses less storage than a comparable binary or string format. Also: using the XML datatype enables XML operations on the data. If your version of SQL Server has the XML datatype, and your data is XML - then why on earth would you not use the XML datatype?????
Sep
27
revised Xml stored as varbinary
edited tags
Sep
26
revised What is SQL Server 2000 spid -2?
added 21 characters in body; edited title
Sep
25
revised Stored Procedure which accept xml file as input
deleted 5 characters in body; edited title
Sep
25
revised SQL Server Transaction Log File
added 2 characters in body; edited title
Sep
25
revised SQL Server backup fails on disk space error
added 22 characters in body