You may have a problem with the user having just db_ddladmin role.  Any tables/objects he creates will be owned by his login, and will not be accessible to any other...

Anthony;

It certainly sounds like your Server2 mixed mode authentication is not set.  All cases that you specified indicate that problem on Server2.  I suggest double-checking Authentication mode on Server2.

You mention...

Are you in the sysadmin role? 

If so, it may be that when you are running the query in your QA, it is impersonating your account (not the SQL Service...

Uh.  Replace(ssn,'-','') ?

Yes, I have been having the (slowly) degenerating eyesight, also.  I had read an article or suggestion many years ago about taking breaks for the eyes.  So I try to...

You cannot use SAVE TRANSACTION with a distributed transaction.

I will take a few guesses here at what you are trying to do. 

If you are not intending to do a...

Just as the error message says, you cannot use Save Transaction with distributed transactions.  From BOL:

SAVE TRANSACTION is not supported in distributed transactions started either explicitly with BEGIN DISTRIBUTED...

How large is the database? 

What about setting up a custom MSDE instance install, with SA password that only you know, and with only SQL logins that you control (in...

You may be thinking that is the case because that is how Access databases work.  SQL Server does not work that way. 

Records may be stored in any order that SQL...

I am not much of an expert on replication and what is required or not, but I believe the only concern regarding indexes (clustered or not) are to consider that...

Your situation is why uniqueidentifier columns (guid) were created in SQL Server. 

I suggest that your problem with inserts are not because of guids, but because the tables are physically...

It depends on the ODBC driver.  If you right-click on the linked server, you can set the ODBC settings there, but the exact syntax will depend on the driver.

In addition,...

I had a similar situation with another ODBC driver (to AS/400), but this may also apply. 

Your connection links are using several libraries and translating and transmitting basic SQL commands...

It has been my experience that nt_username will only have a value if the connection was made using Windows Authentication (Integrated Security=SSPI in the ADO connection string, Trusted_Connection=Yes in ODBC...

There are some "gotchas" in running the setup.  Check this article for the details on how to upgrade SQL Server editions:

How to perform an edition upgrade within SQL Server...