If autogrow is checked, then you really have nothing to worry about.

Lookup alter database in BOL

well looks like you got some work ahead of you.  Try running

DBCC CHECKTABLE with the REPAIR_REBUILD option for each table in the database. 

These links should get you started

not sure what the

Database 'gadata' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECK processing.

means....

well it doesn't look like you have any "corrupt" data.  I am at a loss now.

Open Query analyzer -- connect to the database.

Run the command:

DBCC CHECKDB

Post the output...

Have you ran DBCC CHECKDB on the database?

Wow, that is strange.  I would recommend contacting MS about this.  I unfortuneately cannot offer any additional advice.  Is there anything about this table that makes it different than other...

One thing to be aware of is if you have any jobs that reference network paths, etc.

Generating a script for logins, jobs, etc. should work fine (it's also less work than re-creating everything).  The clients logins are going to be the same as yours?  Also, make...

Posting the query and the DDL might help.  Otherwise you will get a lot of responses saying things like:  "well that sucks... good luck fixing it".

Gee thanks for your oh-so-f*&^ing-helpful post.  Yes it is otherwise I would not have posted the question.  I am not an idiot and do not need chumps like yourself second-guessing me. ...

Sorry, that was the only idea I had.  Any errors in the event log, Install.log files, etc? 

You may want to check this out.

http://support.microsoft.com/?kbid=321339

SQL Digger - http://sqldigger.bdsweb.be/

A table is too full when the indexes and load do not allow for optimal performance.  17,000 rows is a tiny table.  If you are having performance issues, look at...