Server Explorer and SQL
-
Hi all, I have a new installation of SQL 2000 on our domain here at work on a different machine to the one I develop one. For some strange reason however, when I connect to the a database on the SQL Server through Server Explorer in VS.NET (both 2002 and 2003), it won't allow me to do stuff like create new stored procedures, edit exiting ones etc. A real pain in the butt since otherwise I have to open up Access or QA in the background to make changes to the database instead of right in the IDE. What's also weird tho, is that I have MSDE 2000 installed on yet another machine on the domain, and it doesn't have any problems with me editing the stored procedures, or even doing some remote debugging. I've experienced this problem once before with a remote database, and I'd just assumed the problem was because the database was remote and not on the same domain etc. Anyways if anyone else has had a similar experience and knows of a work around, or even what makes VS decide for which DB connections it will enable/disable the "edit stored procedure" menu items etc, that will be great. TIA Andy
-
Hi all, I have a new installation of SQL 2000 on our domain here at work on a different machine to the one I develop one. For some strange reason however, when I connect to the a database on the SQL Server through Server Explorer in VS.NET (both 2002 and 2003), it won't allow me to do stuff like create new stored procedures, edit exiting ones etc. A real pain in the butt since otherwise I have to open up Access or QA in the background to make changes to the database instead of right in the IDE. What's also weird tho, is that I have MSDE 2000 installed on yet another machine on the domain, and it doesn't have any problems with me editing the stored procedures, or even doing some remote debugging. I've experienced this problem once before with a remote database, and I'd just assumed the problem was because the database was remote and not on the same domain etc. Anyways if anyone else has had a similar experience and knows of a work around, or even what makes VS decide for which DB connections it will enable/disable the "edit stored procedure" menu items etc, that will be great. TIA Andy
Edit your Server registration to use SQL Server Login and passwords instead of Windows Domain security. Then, enter a login and password that has rights to create objects (such as sa).
-
Edit your Server registration to use SQL Server Login and passwords instead of Windows Domain security. Then, enter a login and password that has rights to create objects (such as sa).
Thanks for your post. Unfortunately, I've already tried using the sa account etc and still had the same problems. It's really weird. Almost like a different driver is being used to access the database on that server as opposed to databases on other servers. The reason I say this is that if I connect to a database that VS will allow me to edit/add etc etc and the server is MSDE 2000 I get the following folders underneath the database connection: Database Diagrams, Tables, Views, Stored Procedures, Functions. Yet, under the SQL 2000 database connection, I'm only seeing Tables, Views and Stored Procedures. No Database Diagrams and no Functions. Odd. Any thoughts?