We have a commercial product, currently in VFP but being re-developed using SQL Server and .NET using C#.

Standard manufacturer install means 100-150 users. We have about 120 tables...15 of which get hit constantly in production mode. So we have 15 significant update triggers, and about 15 or so stored procs for major queries. Also a requirement for heavy application logging of what users have changed.

Down the road, we know that if we don't support Oracle, we'll lose business. I've been looking at things like dynamic T-SQL [sp_executesql] and other things that have SQL-Server specific syntax.

Is it 'better' to just write straight ANSI SQL, which means it will port to Oracle [or other databases], but also that we potentially won't be able to take advantage of things that will help with performance? It seems to me that since we'll have roughly 1,000 lines of code in the database, I'd rather optimize for performance and just learn to live with managing multiple code bases. But I wanted to find out what others think about this.

Also, I'll sneak another question in here...one can connect to a backend database in ADO.NET one of two general ways...SQLCONNECT and OLEDBCONNECT. I've been told SQLCONNECT is faster...where specifically would one see measurable performance differences?

Thanks,
Kevin