I agree that UNC's are the way to go to avoid potential conflicts. You also might want to check security. In other words do the service accounts have access to...

To make it easy (and get back to the subject) ... I'd use Access ! Realistically why would you waste SQL server on a really small single user database. Or...

Yelena is on target ... At my site we have a dba_stats database on the MSX server and all other servers write to it avoiding all of the mentioned issues....

Could you not make a request of the hosting provider to carve you out a slice of disk space ? That's what I mistakenly assumed you had requested and the...

It sounds as if your hands are tied. Maybe it's time to look for another more 'dba' friendly hosting service ...

For starters, could you list your hardware, OS version and service pack along with your SQL Server version and service pack ? Also, maybe the forst 10-20 lines of the...

happycat59 is 110% correct. SQL Server does not care. I have 22 instances on SAN storage ... some are standard and some are enterprise.

I watched the movie on Monday. It was a little over 90 minutes in length. Had I not read the books I would have totally missed most of the messages....

'autogrowth' is both a blessing and a curse. A blessing to those who do not monitor database size and growth patterns and a curse to those who depend on it....

or you can use

set quoted_identifier off

with this setting you can mix'n'match both single and double quotes.

Just a thought since the errors seem both random and spurious. Have you run hardware diagnostics ? I'd start with memory first since the errors appear and disappear randomly. Then...

Stored procedure execution. I have an 'MSX' Server executing/downloading tasks/Jobs to 'target' servers. Some of the target server procedures reference a database on the MSX server.

Actually I've had to take this a bit farther in some cases ...

SET ANSI_NULLS ON

SET ANSI_WARNINGS ON

GO

CREATE PROC A

AS

SET ANSI_NULLS ON

SET ANSI_WARNINGS ON

Select null

GO

To start with here's a few handy links:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;314546

http://support.microsoft.com/default.aspx?scid=kb;en-us;246133&Product=sql2k

http://support.microsoft.com/kb/224071/EN-US/

http://support.microsoft.com/kb/240872/EN-US/

http://support.microsoft.com/default.aspx?scid=kb;EN-US;295732

As for connections via ODBC, well, you've already gone down the hard path by using computernames or fully...

and to that add:

AIX - IBM Unix

IBM Mainframe as well