Re: Client Database Solution, or best practice
From: Val Mazur (group51a_at_hotmail.com)
Date: 04/24/04
- Next message: Kevin Yu [MSFT]: "RE: Bitwise Comparison in WHERE Clause"
- Previous message: Val Mazur: "Re: DataSet XmlWrite error (c#) - URI formats not supported"
- In reply to: Elric: "Client Database Solution, or best practice"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Apr 2004 22:47:49 -0400
Hi Elric,
My personal opinion is to use MSDE. Several points, which give advantage to
MSDE:
1. It provides same level of security as SQL Server.
2. It is stable. Access database could be easily corrupted and requires
repairs once in a while
3. It has rich functionality, supported by SQL Server - triggers, SPs,
extended syntax for Transact SQL
4. If your database will require more space, then you could migrate to SQL
Server without writing any additional line of code. Just attach database to
SQL Server and it is done
-- Val Mazur Microsoft MVP "Elric" <LordElric@qwest.net> wrote in message news:5F944EF4-933A-44DA-AB30-79A24D2C247C@microsoft.com... > I'm currently working on a client application in .net, written in C# (VS > 2003). I'd like feedback on a "best fit" for a local client database to > store data. Not a whole lot of data, but enough to require a solid > solutions that is secure and preferably encrypted. > > I've considered access or even the SQL desktop engine. Does anyone have > suggestions, personal experiences, or general best practices on storing > local data in a secure fashion? I'm just not seeing a lot of answers from > MS on this. > > Thanks! > Elric
- Next message: Kevin Yu [MSFT]: "RE: Bitwise Comparison in WHERE Clause"
- Previous message: Val Mazur: "Re: DataSet XmlWrite error (c#) - URI formats not supported"
- In reply to: Elric: "Client Database Solution, or best practice"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|