meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 3 months |
| seen | yesterday | |
| stats | profile views | 30 |
|
Aug 9 |
asked | How often to backup the master database? |
|
Aug 8 |
awarded | Teacher |
|
Aug 8 |
answered | 70-432 : SQL Server 2008 Implementation and Maintenance |
|
Aug 5 |
awarded | Editor |
|
Aug 5 |
revised |
Should I stop transaction log backups during a full backup? added 2 characters in body |
|
Aug 5 |
accepted | Should I stop transaction log backups during a full backup? |
|
Aug 4 |
asked | Should I stop transaction log backups during a full backup? |
|
Jul 21 |
awarded | Scholar |
|
Jul 21 |
accepted | Does adherence to the DRY principle justify dynamic SQL? |
|
Jul 21 |
accepted | Should I convert empty varchar values to NULL? |
|
Jul 21 |
comment |
Does adherence to the DRY principle justify dynamic SQL? My example is pretty simplistic, but for a more complex query that involved the usage of indexes, would the above approach open you up to parameter sniffing? |
|
Jul 20 |
asked | Does adherence to the DRY principle justify dynamic SQL? |
|
Jul 20 |
awarded | Student |
|
Jul 20 |
comment |
Should I convert empty varchar values to NULL? The developer for the middle tier has offered to implement a method that will convert all empty strings to NULL. I'm wondering though, is it the responsibility of the database to ensure this consistency? Or is it my responsibility to represent what was submitted (correct or not)? |
|
Jul 20 |
comment |
Should I convert empty varchar values to NULL? @MartinSStoller: do you a think it would be better to block these empty strings through an error message? In the context of this particular data, an empty string will not have meaning to the user. |
|
Jul 20 |
asked | Should I convert empty varchar values to NULL? |
|
Jul 20 |
awarded | Supporter |
