4

I've had this error for months now. On some databases on my Azure SQL Server, when I go to Edit Rows or enter Designer view in SQL Server Management Studio. I get an error

Could not find stored procedure 'sp_linkedservers'.

I don't know where it's looking or what stored procedure to add.

7
  • The easy solution is to stop using the visual row editor. Just write the update statements you need instead. The visual row editor has some strange bugs that pop up occasionally. You should do the same with editing tables. Commented Nov 10, 2015 at 15:55
  • 1
    That's a good point but when I'm just hopping in to change something from true to false or some other minor change, it's a lot faster to just open and edit that single cell than to find the ID and write the statement. Bulk updates, sure but there's a lot of convenience in this feature. Commented Nov 10, 2015 at 16:02
  • I find it faster to do it with t-sql than the gui. I have SSMS open already most of the time so a simple update is way faster than digging through the list of tables and such to edit the top x rows (and worse if the row you want isn't in there). Once you are more comfortable writing t-sql you will find it is much faster. Commented Nov 10, 2015 at 17:21
  • What version of SSMS is this? I don't have this issue on SSMS 2014 Commented Nov 10, 2015 at 19:15
  • 1
    Thanks for the input everyone but the "stop using the visual editor" is not an answer to the question. I know how to write my SQL statements, I simply have a preference and an error I need to clear. Commented Nov 10, 2015 at 20:32

1 Answer 1

3

While this isn't a solution for SSMS 2014, working through SSMS 2016 CTP3 seems to be working and the problem has been solved. Thanks to @Cpt. Monac for the suggestion!

Sign up to request clarification or add additional context in comments.

2 Comments

here's where one can get the latest version of SSMS msdn.microsoft.com/en-us/library/mt238290.aspx
I installed the March 2016 SSMS preview from the above link, but I am still having this problem, although strangely the first time I selected "edit rows" it worked fine.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.