|
|
Posted by Erland Sommarskog on 10/02/23 11:53
hatcat (guy.davidson@hatcat.com) writes:
> I work for a game company, and we have decided to drag ourselves
> kicking and screaming into the 21st century by creating all our data in
> a database. Since I have a little Access experience, I have been
> nominated to Sort This Out. So, what I need to do is construct a
> system of work whereby a database on our server (running SQL Server for
> Team Foundation Server if that's relevant) can be queried and updated
> from Access clients on the LAN.
>
> To do this, I guess I need to know how to create a database, tables
> within it, grant privileges for reading and writing, and export the
> tables to another format. I can do nearly all of this in Access with a
> local database - how different is it on a server?
One thing is for sure, Access and SQL Server are very different. They both
use SQL, but there are great differences in the SQL dialects. In an Access
you can reference forms etc within a query, but not in SQL Server, because
it is a server.
I would recommend that you get some training, either by attending a class
or at least read some introductory book. Depending on how big the database
mission of your company is, you may also consider to bring in a consultant
to get you started. SQL Server is a complex tool, and it's easy to get lost.
That is, you may be able to compose an application on your own, but
performance and robustness may be so-so.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|