Without SQL Enterprise - MySQL? XML?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a project I'm working on where I just won't be able to have SQL enterprise.
It's an ASP.Net VB project, and it needs to scale. Can I just use rigid and relational
XML and have the entire site run well without an ODBC database?

Will XML scale? I'm worried if I have a User.xml keeping track of all the
users the same way that a Users table would in SQL, it won't be able
to deal with a lot of simulatneous users.

Will MySQL be a nightmare? It works fine with PHP and mySql.
But the way the Visual Studio .Net environment works, will it
be horribly hard to get views of the mySQL tables with the
same web form designers etc ?

Thankssss
Paul
 
Hi Paul,

MySQL will work just fine with .NET and will scale well.MySQLNet
provider(open source managed .NET provider for MySQL) is great and will
perform well from
my experience.Here is the link for Exploring MySQL in the Microsoft .NET
Environment
http://www.mysql.com/articles/dotnet/index.html#ADO.NET
It will work fine with Visual Studio .NET as well.Regarding XML,it is
based on the nature of your requirement..NET has great classes to deal with
XML which will give superior performance.
For example :
XMLTextReader class provides fast,non-cached,forward-only access to XML
data.
XMLTextWriter Class Represents a writer that provides a fast,
non-cached, forward-only way of generating streams or files containing XML
data that conforms to the
W3C Extensible Markup Language (XML) 1.0 and the Namespaces in XML
recommendations.
Here is a link to explore the System.Xml namespace.

http://msdn.microsoft.com/library/d...l/frlrfsystemxmlxmltextreadermemberstopic.asp

Hope this helps.

Regards
Marshal Antony
http://www.dotnetmarshal.com
 
What is the reason for not using SQL enterprise (I guess you mean full
SQL-Server)?

If you search for a good, stable, easy to maintain and performant database
you might want to take a look at Gupta SQLBase. It comes with all sorts of
connectivity (Native, ODBC, OLEDB and a NDP - .NET data provider) perfectly
integrating into the various environments. Additional information available
at http://www.fecher.at and http://www.guptaworldwide.com.

--
Martin Knopp, Dipl. Ing.

fecher GmbH
D'Orsay-Gasse 4/1, A-1090 Wien
email: (e-mail address removed), web: www.fecher.at
phone: +43-1-3199124-0, fax: +43-1-3199124-80

-- Alle Dienstleistungen von fecher im Überlick!
http://www.fecher.at/services/ --

-- Gupta Roadmap für SQLBase und Team Developer mit Themen wie Unicode,
Linux und .NET - informieren Sie sich hier:
http://www.fecher.at/GuptaRoadmapJuly2003 --

-- Windows style web application powered by Team Developer, Building Blocks
XP and ASP.NET here: http://www2.fecher.de/islandweb/ --
 
XML? I would not head this direction for a large number of users.
MySQL? Not a problem, overall, except I am not as fond of the OleDb drivers
for MySQL as OleDb for other databases. It works.

Other options
MSDE - basically SQL Server for 5 concurrent users. If you use correctly, it
will scale much better than Access (ie, open conn as late as possible (JIT)
and close ASAP).

Of the choices you put forth, I would opt for MySQL personally.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************
 
hey thanks this is awesome, totally the way i am going to g
one thing i noticed, there's a commercial .Net provider an
an open source one. will the open source one do?
 
What is the reason for not using SQL enterprise (I guess you mean full SQL-Server)

its a cost issue -- the price for a fully licensed sql server strikes the funding tea
as extremely expensive.
 
mySQL!!!

It works great with .NET. There are open source native data providers, and
also a couple of commercial ones. I've only used one commercial one so
couldn't tell you which one is best. The one I use is Core Labs.
It works a treat, and i've done time trials against SQL Server, and for read
operations (90% of the sql statements that run on my site) it's faster.
 
Back
Top