February 21, 2004 at 11:45 am
I'm new to SQLServer 2000 and would like to know if it is possible to create
a database that would search,retreive and archieve resume? Maybe it should not be done in SQL but in Ms Access I don't but I'd appreciate any feedback. Thanks in advance.
February 23, 2004 at 1:38 am
When you say resume db, I guess you have some Word documents and now want to know if it is possible to store and query them in SQL Server, right?
If so, you can store those files in an image column in some table. As you are on SQL2k you are able to full-text index that column and run queries against that column. For an introduction take a look at BOL for full-text catalogs, overview.
What will your front-end look like? Some kind of VB? If so, you can use the ADO Stream Object to store and retrieve your data quite easily.
Note, that there is no such thing as the Access OLE datatype in SQL Server. Access interprets the data and opens Word right away at a cost of massive storage oberhead. SQL Server only stores this binary data. All interpretation of it you have to do by yourself. But that's still better than using Access.
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
February 23, 2004 at 7:08 am
Thanks Frank for answering my query. As I said before I am new to creating this type of database and I have not thought it thru as to what type of front end to use. Is there a book of some other documentation I can read up on?
thanks again.
February 23, 2004 at 7:40 am
Well, on questions concerning BLOBs I usually refer people to this source
Not sure, if it is terribly useful for you. I don't know if there are books specifically on that topic out there. However, Microsoft knowledgebase and TechNet do provide tons of useful information. Maybe you'll find something here in the article section searching for full-text and/or BLOBs...
But first off, I would think about what you want to do. Maybe you come to the conclusion that a non database solution is better. And and and.....
Don't worry about the actual implementation later on when you decide for a database solution. If you get stuck just ask a question here, and together we'll figure out.
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply