MS SQL Server :: Restore SMK And System Databases (credentials And Linked Servers)

Accessing System Views Via Linked Servers

Apr 30, 2007

Is there anyway to access system views on/from a linked server?

I have unsuccessfully tried various permutations of
select *
from [MDEDATAWTDss2005].master.[information_schema.colums]

Thanks

View 6 Replies View Related

Restore All System Databases

Feb 8, 2007

Hi All,

I need to do a restore of all my system databases, master, msdb and model, and of course my production database.

The Windows 2003 OS and Sql Server 2005 have both been reinstalled on the server.

I understand I need to be in Single User Mode to restore the master database and I just wanted to clarify the procedure for a successful restore.

I've found this page: http://msdn2.microsoft.com/en-us/library/ms190679.aspx which has instructions for restoring a master database.

So, all I have to do is:

1. Be in single user mode

2. Using SQLCMD run:
C:> sqlcmd
1> RESTORE DATABASE master FROM DISK = 'Z:MyBackLocationmaster.bak';
2> GO

From the instructions:
"After master is restored, the instance of SQL Server shuts down and terminates the sqlcmd process"

My Questions:
When I've restored the master do I repeat the steps above to restore the msdb and model databases?

Are there any other pitfalls?

Thanks for any advice

Melt

View 1 Replies View Related

System Credentials

Jul 27, 2007

On to the next understanding topic. I understand the concept of credentials and why they are needed with the isolation of machine admin authority and running a SQL Server instance. I had a question on the purpose of the system credentials.

##MS_SQLResourceSigningCertificate## is the credential utilized by the instance itself to gain access to Windows for such things as reading and writing to database files, network stacks, writing to the error logs/event logs, etc. ##MS_AgentSigningCertificate## is the credential that is used by SQL Server Agent for accessing any necessary Windows resources.
##MS_SQLReplicationSigningCertificate## is used only by the replication engine to allow it to access Windows resources.
##MS_SQLAuthenticatorCertificate## is used during the authentication process for SQL Logins to provide authenticator services and is also used to access the Windows security API.

Each of the credentials is a certificate which is loaded into the instance and you can find the corresponding certificate within the data folder for the instance. I'm assuming that a mechanism is already in place to prevent someone from mucking with the certificates on the OS to gain access back into the SQL Server by comparing the signature already stored within the instance with the signature of the certificate on the OS. (This is also part of the larger discussion of certificate use within SQL Server itself and explains why you can't change the service account/password using the Service Control Applet.)

Did I get that correct, am I way off base, or is this one of those "no comment" items?

View 5 Replies View Related

Datasource Credentials And Linked Reports

Feb 21, 2007

Hi,

we have a problem with linked reports. We are using the same reports that are run on about 70 different Oracle schemas. The credential information is passed when calling the report. This works fine for reports and reports with subreports. But when linking to another reports, the credential information is lost.

Is the a possibuility to pass the datasource credential information to a linked report?

Thanks in advance for your help

Michael

View 1 Replies View Related

SQL Server Admin 2014 :: How To Do System Restore To Previous Restore Point

Dec 31, 2014

In Windows Server 2012. How do I do a System Restore to a previous restore point?I need to install the 64 bit and 32 bit Oracle Client Install for connections in SSIS and to create Oracle Linked Servers.

If you make a mistake it is not fun removing it. Sometimes it corrupts the machine and it is difficult to uninstall since there is not an Oracle Universal installer for Oracle 11g.If you install the 32 bit before the 64 you mess up the machine.how to create a restore point.