How can we help you today? How can we help you today?
fatherjack2
I would agree that diagrams are much quicker for refreshing yourself with a schema and understand what connections there are beyond the 'first hop'. / comments
I would agree that diagrams are much quicker for refreshing yourself with a schema and understand what connections there are beyond the 'first hop'.
0 votes
I hope this helps. Not really. I have never been 'fluent' with Linked Servers as we dont need them a great deal here and your help page seems to be the same as the link to microsoft supplied at the bottom only without the formatting... I have SQL Backup running as a service, using a network logon (eg. domain\SQLB5Admin). This account has high level server access to all SQL Servers - its a member of the serveradmin role. In the linked server properties on ServerA I have alternately set the Security tab to have: Local Login - domain\SQLB5Admin Impersonate - ticked RemoteUser - empty RemotePassword - empty and Local Login - domain\SQLB5Admin Impersonate - unticked RemoteUser - ServerB_SQL_Login RemotePassword - **** and i get the same error. I can only get this to work if i complete further details in the section marked "For a login not defined in the list above, connections will:" here, if i check "Be made using the security context:" and complete the "Remote Login" and "With password" with the ServerB_SQL_Login details, the reports work. My understanding of this situation is that the process requesting data from the remote server (ServerB) doesnt have a local login mapped to the remote server and so uses the one specified. If this is the case surely anyone and everyone attempting to get to the remote server from the local server would get their connection created as ServerB_SQL_Login and therefore assume its elevated priviledges?? Why doesnt the service account running SQL Backup have its login mapped across to the linked server? I may be misunderstanding SQL Server Linked Servers security and if so i apologise but security of our data has to take precedence. footnote: We are using Windows server 2003 R2 64 bit Enterprise with SQL 2005 Standard 64bit sp2 and the microsoft article is dated Jun 2004 and refers to Windows NT4.0 and SQL 2000. Maybe it is still relevant but ... / comments
I hope this helps. Not really. I have never been 'fluent' with Linked Servers as we dont need them a great deal here and your help page seems to be the same as the link to microsoft supplied a...
0 votes
Thanks Matthew, i have the templates moved over. Maybe this process is a potential development for the next version? Using the SQL Backup GUI would have been a lot easier as i can see all my servers from there... cheers Jonathan / comments
Thanks Matthew, i have the templates moved over. Maybe this process is a potential development for the next version? Using the SQL Backup GUI would have been a lot easier as i can see all my server...
0 votes