Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
antioch
Starting Member
3 Posts |
Posted - 2005-03-25 : 19:26:58
|
a little background first: i am a sql newb. ive worked with and designed access db's for years, but nothing terribly advanced.my project: a filing cabinet for the 21 century! (that one's goin straight into the sales speech!) various business documents will be imaged in pdf format and referenced in the db by relevant details such as date, name, ref number, document type, etcetera. this db will be used by multiple users with varying levels of access to the vast array of documents to be imaged.i started with a general notion of how i would technically accomplish this. however, in the course of assimilating all the knowledge i could soak up on this forum in the last 24 hours, that notion has been blown to hell. this project im working on may take a while to complete and i have much to learn in the process. during this time, im sure to be asking many questions. i may be a newb to sql, but im not afraid to read and therefore search, before asking. this forum appears to be an excellent resource, rife with many active, knowledgeable ppl. thank you for ur time - in advance. enough mushy crap, onto my issue:since i have little to no experience with db servers (but not other kinds of servers,) i want to go over my overall plan in intentionally vague language just to see if im approaching this the right way. if so, i will ask a couple more questions, followed up some reading in the relative areas where i lack the necessary knowledge.so here goes:im going have one server instance, one db, and a small handful of tables.one of these tables will contain a column (among others) for url's linking users to the document's image (pdf.)document image (pdf) filenames will be based off of its row's GUID.the clients will connect to the db using access with linked tables.so thats round 1. plz point out any areas that are glaring mistakes or misconceptions. i am aware that i have excluded MANY details in my questions, but i am satisfied in general answers, knowing that im going in the right direction.sorry for the massively long post...it wont happen again.  |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-03-26 : 00:12:43
|
| You've got the physical images out of the database, thata good first step.Now use only Stored Procedures for the DML, and don't use any cursors, and you should be fine!I would recommend that all tables have Create and Update User and Date columns.Kristen |
 |
|
|
antioch
Starting Member
3 Posts |
Posted - 2005-03-26 : 13:59:01
|
| thx for ur insight, kristen."Now use only Stored Procedures for the DML, and don't use any cursors, and you should be fine!"so the stored procedures would be for assembling the fully qualified image path? then, this assembled path gets stored in a column in the documents table, right?"I would recommend that all tables have Create and Update User and Date columns."is this for tracking which users created and/or updated the individual rows? |
 |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-03-26 : 18:35:54
|
| GUID's for filename will give each file a unique name,but will not not uniquely identify the file's physical location.path + filename (or url) should be made unique in the table that stores the "locator path" to the file.rockmoose |
 |
|
|
antioch
Starting Member
3 Posts |
Posted - 2005-03-28 : 15:40:46
|
| i intended on storing the path in a single record table expressly for this purpose. then combining the GUID with the path and using that in the 'document' table's path property. i assume this is where dml comes in?is this a sound plan? |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2005-03-29 : 05:35:22
|
| As a by-the-way - Sort out your security model/practices very early on....far better to get it right in the beginning than debug your way through some exercise to convert from an unsecure database to a secure one. Search here for other discussions on same. |
 |
|
|
|
|
|
|
|