Brent,

The exact error will be handy for helping you out.  Can you get it from the SQL errorlog?  Or, at the command prompt try running "sqlservr" from the mssql\binn directory...

...make that 4 people.

There's the DBCC LOG command, but only 3 people on the planet know how to interpret the results.  One works for Microsoft and the other two sell 3rd party products...

If it's a recurring inconsistency on the same table (LinkThree) and index (id 12)then I'd say you do have an inconsistency problem but the good news is that - because...

It sounds like you're trying to enter/update the data using Enterprise Manager.   In that case the maximum you can enter is 1023 characters, even if you have defined a varchar...

Someone must be using a new-fangled version of bcp.  Maybe Yukon's version determines whether to load or unload data depending on how hard you hit enter.

To monitor all connections for deadlocks and get deadlock info printed to the sql errorlog, enter:

    dbcc traceon (-1, 1204, 1205)

To stop this monitoring:

    dbcc traceoff (-1, 1204, 1205)

Keep an...

You'll probably need to delete guest from model to prevent this happening.

Yes it is a security issue.

I remove guest from every database that allows me to.

what do you mean by "and strange ones at that"?

are they tables in that database?  in another database?  on another server?  when the users are connected does sp_who2 show them...

You haven't removed builtin/administrators have you?

It's just a warning that gets very little coverage from MS, but the following excerpt is from http://support.microsoft.com/default.aspx?scid=kb;en-us;811889

SQL Server Service Principle Name Creation

This is one of the...

Try also a computed column.  Eg.

create table xxx

(acct char(3),

acct1 as '0000' + acct)

insert xxx values ('001')

insert xxx values ('002')

insert xxx values ('003')

select * from xxx

acct acct1  

---- -------

001  0000001

002 ...

Have a look at the MS KB article "HOW TO: Manually remove SQL Server 2000 default, named, or virtual instance"  (http://support.microsoft.com/default.aspx?scid=kb;en-us;290991)

If you're doing it through a scheduled job, then use the advanced options of the job step to send output to a text file.

You can try putting the destination database into bulk-logged recovery then doing a SELECT INTO from the source database/table.  If the destination table already exists you may have to do...