No, because MSDE would require me to install the database and start to write TSQL. I don't want to do that. I am thinking about a .NET assembly that will pretend that it is a real database and return a TDS stream, while it is actually not. Something that would listen on the actual SQL server ports, accept parameters, and return some data just like SQL Server does; but it could live on a developer's system without requiring a full database load.
My development cycle typically includes tiered coders, each are given an explicit document of "what to do", even in calling stored procedures. The problem is that all of the stored procedures are not ready or written (or sometimes fully thought out and need to be changed) on the DB side of things. So it would be to the .NET component developer's advantage to have the DB-calling code in place, but instead of calling the real thing, it just calls this pseudo-MSSQL-host. Then the .NET coders could perform unit testing and etc without having things break when they are actually supposed to get data from "somewhere". ---orig Date: Tue, 6 Jan 2004 21:00:59 -0500 From: Stephen Johnston <[EMAIL PROTECTED]> Subject: Re: SQL Server Emulator? I would think that MSDE fits the bill for this doesn't it? At 07:20 AM 1/6/2004, you wrote: >Can anyone weigh-in on the idea of a C#-based SQL Server emulator? >Something that would accept connection strings from an >ODBC/OLEDB/SQL-Managed client, accept dynamic SQL or a stored procedure,= and >return a TDS? I was thinking it would be nice for prototype systems and/or >test-driven development, without the overhead of having a living SQL server >somewhere. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
