What is the best way to place database on client 's machine?
-
Hell all, i have developed an application say inventory management in vb.net/ ms sql. now i want to install this application on different machines of my clients. i have written maximum code in Sp's and have fear that some one copy it or edit/delete it. kindly suggest me a best way in which no one copy my database or edit/copy/delete it. thanks in advance
rmshah Developer
-
Hell all, i have developed an application say inventory management in vb.net/ ms sql. now i want to install this application on different machines of my clients. i have written maximum code in Sp's and have fear that some one copy it or edit/delete it. kindly suggest me a best way in which no one copy my database or edit/copy/delete it. thanks in advance
rmshah Developer
That's a big reason not to use stored procedures. If it's your client's system, you can't lock them out from doing silly things to it, yet you will likely be responsible for repairing any damage they do. At best you could have a written agreement that clearly states what happens when they screw up the system. I've was only required to write stored procedures for one client, and it as dreadful. X|
-
Hell all, i have developed an application say inventory management in vb.net/ ms sql. now i want to install this application on different machines of my clients. i have written maximum code in Sp's and have fear that some one copy it or edit/delete it. kindly suggest me a best way in which no one copy my database or edit/copy/delete it. thanks in advance
rmshah Developer
Don't give database to the users. Keep it in a secured server. Create a web service/WCF service which provides access to this database from your application. This helps to keep database isolated and prevent users from modifying the SPs. Another alternative(worst) what I think is to create the stored procedure with WITH ENCRYPTION clause. This will make the SPs encrypted, but there is no easy way to decrypt it back. Again, this will not prevent users from dropping it. :)
Navaneeth How to use google | Ask smart questions
-
That's a big reason not to use stored procedures. If it's your client's system, you can't lock them out from doing silly things to it, yet you will likely be responsible for repairing any damage they do. At best you could have a written agreement that clearly states what happens when they screw up the system. I've was only required to write stored procedures for one client, and it as dreadful. X|
PIEBALDconsult wrote:
That's a big reason not to use stored procedures.
Not really. The user can just as easily go in and update the tables without.
PIEBALDconsult wrote:
At best you could have a written agreement that clearly states what happens when they screw up the system.
Thats a more common way. At the end of the day, if the database is on your clients server, there is very little you can do to stop them screwing it up, so having a good, watertight, written agreement of responsibilities is probably the best way - if they are fully aware of the consequences then they probably won't.
Bob Ashfield Consultants Ltd Proud to be a 2009 Code Project MVP