April 21, 2009 at 11:51 pm
Comments posted to this topic are about the item SCOME - Setting Up Your Remote Servers - Part 2
April 22, 2009 at 10:29 am
Dude, you got me very interested. Looking forward to you finishing this article and wish you all the best in completing it. I was about to start something like this (I have modified SP2 reports to work on all servers but it wont work on SQL 2008. Will this?)
April 22, 2009 at 12:57 pm
I remain confused by the purpose of this project. SQL Server 2008 provides Centralized Management Server which allows you to register all of your servers in a single location and execute a single command against all of them from one location. This is all built into the product. At a minimum, shouldn't this be the mechanism used to gather your data rather than creating a server table and looping through it to execute DML commands.
http://msdn.microsoft.com/en-us/library/bb934126.aspx
There are also mechanisms for data collector, which will gather data and place it into a "management data warehouse".
http://msdn.microsoft.com/en-us/library/bb677248.aspx
Seems like you're re-inventing a more cumbersome wheel here.
April 22, 2009 at 1:03 pm
Are all your servers on 2008? if not, then this could help in the meantime. I still have a few 2000 boxes. If this will work on all three then I think it is worth it.
Mike
April 22, 2009 at 1:10 pm
The SQL Server Central Management Server does not require the registered servers to be SQL2K8. You can register SQL2K servers and execute T-SQL against them from a central location as long as the T-SQL is supported.
April 22, 2009 at 1:19 pm
michaelberry67 (4/22/2009)
...you got me very interested. Looking forward to you finishing this article and wish you all the best in completing it. I was about to start something like this (I have modified SP2 reports to work on all servers but it wont work on SQL 2008. Will this?)
Thanks Michael. Yeh, it should work on 2008 fine.
No, we don't have any 2008 servers, just 2000 and 2005.
jhadden (4/22/2009)
I remain confused by the purpose of this project. SQL Server 2008 provides Centralized Management Server which allows you to register all of your servers in a single location and execute a single command against all of them from one location. This is all built into the product. At a minimum, shouldn't this be the mechanism used to gather your data rather than creating a server table and looping through it to execute DML commands.http://msdn.microsoft.com/en-us/library/bb934126.aspx
There are also mechanisms for data collector, which will gather data and place it into a "management data warehouse".
http://msdn.microsoft.com/en-us/library/bb677248.aspx
Seems like you're re-inventing a more cumbersome wheel here.
http://www.sqlservercentral.com/Forums/FindPost700958.aspx
I'm fairly confident that down the line, you'll hit a snag when trying to write a particular report using the CMS. It just won't be as flexible as writing your own programme. If you're limited to time, then fair enough, if not, then why not get creative? 🙂
April 22, 2009 at 1:24 pm
Really? Just trying to save you some trouble. Enjoy.
April 23, 2009 at 8:41 am
Thanks for that. really. Any good articles on that new feature? I would be interested since we do have one server running 2008.
Mike
July 1, 2009 at 7:38 am
I am trying this out but having problems with the remote user part of the Linked Server.
I have already created the database under another account and this account owns the database. I cannot see how I can now have the user 'MonitoringReportUser' be the owner of teh SQL_Admin Database.
Anyone thired this part out yet and can help with setting this up?
July 1, 2009 at 7:42 am
Hi
What's the exact error?
Drew
July 1, 2009 at 8:41 am
Drew...
I am creating a linked server as Using SSMS.
I am cautiously only adding one linked server at a time.
I call it MonitorTest and its a SQL Server.
On the Security tab, I add a Local SQL login and as the Remote User I specify a SQL Admin Account (windows account) that has all the necessary permissions. I specify that connections will not be made for logins not defined.
On the Server Options page, I specify the True values for RPC and RPC Out.
I get the SQL Server error:-
'The linked server has been created but failed a connection test......
Error 7416 Access to the remote server is denied because no lohin-mapping exists...)
July 1, 2009 at 8:45 am
Have you followed the MSDTC instructions in the article?
October 28, 2009 at 5:01 pm
For anyone interested, I've uploaded a demo of an application that I have developed primarly using the SCOME technique. It can be viewed here: http://www.sqlservermonitor.com/
If you have any questions regarding a particular report, please feel free to ask.
Drew
May 19, 2010 at 12:51 pm
Hi,
What does this script do?
grant execute on xp_prop_oledb_provider to [User_ID]
I'm currently encountering this error and nto quite sure if this is the only to resolve this error: "Execute permission denied on object 'xp_prop_oledb_provider ', database 'mssqlsystemresource', schema 'sys'"
Is granting execute permission to this extended sp will just grant the user to show the catalogs under there linked server? I'm afraid i will grant them other permission other that what the user and application's linked server should be doing..
Thanks for your inputs! 🙂
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply