Database Server TroubleShooting

Table Of Content
01. Failure in Executing SP on other Server in LinkServer Environment
02. Failed to update SQL Server linktable in Access 2000


01. Failure in Executing SP on other Server in LinkServer Environment
You got failure in executing SP with the following message (but you  get no probs with common SELECT operation):


Msg 7411, Level 16, State 1, Line 1 Server '202.129.191.112' is not configured for RPC.
 
Solution:
In The Link Server property, RPC Out should be set as True.
Applies to SQL Server 2005



02.Failed to update SQL Server linktable in Access 2000
Ever had this error message when editing SQL Server link tables in Access?

"this record has been changed by another user....etc"

I have experienced this before, and curious on the Primary keys/Index in the SQL Server Table. (one of major cause in update failure)

The cause is there is one or more fields in the table containing bit type data type without default value. (the fields are not allowed to be empty)
source: http://stackoverflow.com/questions/973076/linked-access-db-record-has-been-changed-by-another-user

Incredible Tool : SQL Profiler

Incredible tool: SQL Profiler

have you ever tried SQL Profiler for SQL Server 2005?

This is pretty good stuff, and i wish other rdbms engines has the same thing as this SS2005 provide.

In the middle of the User Interface crowd, Profiler is very helpful that you can monitor every query against your beloved data. You don't need to go to debugging mode of your coding. Many parameters are involved! too crowded? Calm down, if seen messy, you can choose which one fits your need: Audit Login, Session, Stored Procedures or, TSQL.

parameters involved in the monitor

Experience your best sql-debugging, even without peeping your code!

Wid, 2008