Pardon for jumping in on an existing thread, but, I have a related question.
I am an experienced asp.net (vb) programmer using MS SQL back end databases. I have a client that is considering Cache as a backend instead of SQL (due to cost / dislike of MS / future capabilites utilizing Cache / cross platform compatibility / etc). There current web applications use MS Access (I dont think I need to get into why they are getting rid of Access, the problems with Access are well known). As an experienced .net / SQL programmer, how hard is it going to be for me to utilize Cache as a backend instead of SQL? Will my SQL queries transfer over to Cache utilizing ADO.Net? They have a time crunch issue, so, if it takes too long for me to get up to speed, we are going to have to go SQL and explore Cache at a later date. Thanks for any information. Mike Thomas "Peter Haider" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hello Newsgroup, > currently now i am working with Classic ASP. > In most cases i use Mysql or MS SQL 2k. So far so good. > What i want to know, is it worth to evaluate Cache against .Net? > I think to migrate my application to DotNet, Cache could be also an option. > Do i stay with Dotnet on the right side or is this only a markting > statement? > And what is your experiance to position a product with Cache against DotNet > in the market, could i stand? > Hope to hear (read) a lot of your experiance. > Best regards > Peter Haider > >
