>Hi,
>
>One of the tables I am converting from VFP to SQL Server has many Char type fields. In VFP all these fields by default get empty string value (if application does not set any). In SQL Server it fails as I either need to set these fields to accept NULL or specify empty string ('') as a default. I am concerned that if I specify NULL in these fields it will break something in the front end application (VFP) that is not "prepared" to deal with NULLs. So the approach would be to specify empty string as default to all these fields (about 20). Does that many defaults present a potential problem of increased load on SQL Server? How would DBAs look at this?
>
>TIA.

It should not present a problem. We have a lot of defaults in our database.