Thank you for the recommendation Lun Lee.
I've been working with ESRI support, and others, on resolving this issue, and at this point it looks like the root of the problem *may* be related to how ArcGIS for Server is accessing the SQL Server instance- specifically the use of windows authentication vs. SQL server authentication. I assumed this mode of authentication was determined by the settings in the .sde connection file to the database that is set up from ArcCatalog...However- if there is another place to change this mode from windows/OS to SQL server/database authentication- including via ArcGIS for Server Manager, then I would very much appreciate any information that anyone on the forum can provide.
I have no problems doing a query of records in the related non-spatial table from the rest services directory *if* I don't register the non-spatial SQL Server database with ArcGIS for Server OR if I access tables in a SQL server instance on the same machine as ArcGIS for Server 10. Hosting SQL server on the same machine as ArcGIS for Server 10.1 isn't really possible given my current set up- so I need to make the connection to a remote instance of SQL server- ideally one that is stored on a different network than ArcGIS for Server- work. Given these observations though, it seems possible that the issue is related to firewall/network settings/permissions...when the non-spatial data is copied to ArcGIS for Server, there doesn't seem to be a problem.
Any further advice on this issue is much appreciated.
Thank you!
Virginia