[AccessD] MDBs vs SQL Server

Well said.

You can't expect to master SQL Server administration straight away without
doing a course, or at least thoroughly studying some good texts.  That's why
there is such as thing as a DBA.  Once you come across a database as
powerful as SQL, there becomes a distinction between the developer and the
administrator.

As with most products (at least when first starting to use them), 99% of the
time problems are due to the user, not the software.

Cheers,
Andrew

-----Original Message-----
From: Mark L. Breen [mailto:subs1847 at solution-providers.ie] 
Sent: Saturday, 27 December 2003 4:15 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] MDBs vs SQL Server

Hello John,

I think that you have to accept that they are different tools and destined
for different jobs.

I use both as you probably know.  For a small db and with limited number of
users. Jet is great.

For big db's, mission critical reliability, online backups, scheduling and
integrated security (which interfaces with NT / W2K), and other things I
cannot bring to mind now, I believe SQL in all its guises is the tool.

I am sorry to hear that you have had problems with it, I have installed
between 10 and 30 SQL server systems and I have no problems with any.

I say again, the tool to select depends on the customers application, both
have a role to play and one the ends of each scale, it is crazy to use the
wrong tool for the job.

Whata think?

Mark




----- Original Message -----
From: "John W. Colby" <jcolby at colbyconsulting.com>
To: "AccessD" <AccessD at databaseadvisors.com>
Sent: Tuesday, December 23, 2003 1:23 AM
Subject: [AccessD] MDBs vs SQL Server


> I'd like to conduct a non-scientific poll to discover what you folks use.
> Please pick one of the numbers and respond to the list.
>
> 1) I use SQL Server for all my data.  I wouldn't touch an MDB BE with a 10
> foot pole.
> 2) I use SQL Server mostly, but will touch an MDB BE with a 10 foot pole,
as
> long as I don't have to be responsible for the mess.
> 3) I have used SQL Server in at least one actual client system but my
bread
> and butter is made with MDB BEs.
> 4) I am fascinated with the possibilities of SQL server, have looked at
it,
> perhaps installed it at my office, but just don't have the call for it
from
> my clients.
> 5) What's this here SQL Server thangie?  All my database BEs are done with
> MDBs.
> 6) I prefer to do my data stores in Excel spreadsheets, but if I must an
MDB
> is at least within my grasp.  SQL Server is for them big boys n they won't
> talk to me.  I would still be using Borland's Reflex if I could get a
copy -
> now THERE's a REAL MAN'S database!!!
>
> Just pick a number and put it in the first line of your response.
>
> As for me, I am a 4.  I have SQL Server installed in my office, moved my
> billing db to it in order to have a real live in use system using it, and
> have regretted it ever since.  In fact I yanked the data back out into an
> MDB last week after having to rebuild my system twice and then ending up
> with torn pages in my SQL Server database.
>
> John W. Colby
> www.ColbyConsulting.com
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.