Re: Development Cycle
From: TC (no_at_email.here)
Date: 02/26/04
- Next message: TC: "Re: SpellChecking In A Form"
- Previous message: TC: "Re: Incorrect err returned to caller when cancel and show MsgBox in BeforeUpdate"
- In reply to: Terry: "Re: Development Cycle"
- Next in thread: Terry: "Re: Development Cycle"
- Reply: Terry: "Re: Development Cycle"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 12:46:54 +1030
"Terry" <Tezza.TLL@btinternet.com> wrote in message
news:eomhlH8#DHA.2800@tk2msftngp13.phx.gbl...
(snip)
> i guess what i really want to know is this: Is SQLServer as user-friendly
as
> Access and, given that i have a good understanding of SQL and MS products,
> will I be able to find my way around the application intuitively? If
that's
> still unclear, then perhaps I should just assume I can :)
I've not used SQL Server myself. However, it is basically just another
enterprise-level DBMS (database management system) - and I have used other
such products, eg. Oracle.
In most such products, you have an underlying database management product
(the DBMS), and a set of associated development tools for writing programs,
forms & reports etc. for use with that product.
DBMS Development tools
Access MS Jet MS Access
SQL Server SQL Server ?
I don't know what the development tools are called in SQL server. Your
question really is, are those tools as eay to use as MS Access. I don't know
the answer to that, so someone else might jump in here (or you could post
that as a new question).
However, be aware that the complexity of the DBMS part, will definitely be
greater than the complexity of MS Jet. For example, all enterprise-level
DBMS's have special features for taking live backups, or restoring the data
after file corruption. MS Jet has no such features. Enterprise-level DBMS's
have so-called "ACID transactions". MS Jet has no such feature, & so on.
So there is a learning curve for the DBMS part of SQL Server, over & above
the learning curve its development tools (whatever those are). A "database
administrator" would be expert in the DBMS part, and hopefully have a
reasonable understanding of the development tools. Conversely, a "database
programmer" or developer, would be competent in the development tools, but
would not necessarily know much about the underlying DBMS.
Hope this helps. Good luck with the job!
TC
- Next message: TC: "Re: SpellChecking In A Form"
- Previous message: TC: "Re: Incorrect err returned to caller when cancel and show MsgBox in BeforeUpdate"
- In reply to: Terry: "Re: Development Cycle"
- Next in thread: Terry: "Re: Development Cycle"
- Reply: Terry: "Re: Development Cycle"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|