Viewing 13 posts - 1 through 13 (of 13 total)
Why do you need certificates.
Does all of the server connected to the same domain.
Take a look at this tutorial - http://www.dbsnaps.com/articles/sql_mirror_1/[/url]
Oded
June 21, 2009 at 4:41 am
You maintenance plan to run backups, there you can specify the interval of the backups.
Oded
June 14, 2009 at 2:39 am
I think you can't, did you check, right click on the database and select "properties" I advise you against it, you will result in database that can't recover to the...
June 14, 2009 at 2:04 am
From my experience - You shouldn't move any of the system databases to the new database when upgrading from 2000 to 2005.
Oded
June 11, 2009 at 11:27 pm
Yes, you can't change the recovery model when you do log shipping - keep it full.
The Mass work will not be affected by the log shipping - it async operation.
Oded
June 11, 2009 at 11:16 pm
It seems that you have server access problem, check that the domain_admins have serveradmin role.
June 11, 2009 at 2:30 pm
In order to restore to the most recent point in time (not only the the last full backup) we have to enable full recovery model.
In full recovery model the transaction...
June 11, 2009 at 2:14 pm
I seems that the database role datawriter is cousing you the problems, remove that db role and grant specific access writes the db objects for that user.
Oded
June 11, 2009 at 2:01 pm
The SQL Server error log will have more relevant error that related to your problem, can you please upload the errors in the sql server log,
Oded
June 11, 2009 at 1:52 pm
1. SQL Maintenance plan can be configured to delete files older then X days, check up under "Maintenance" tab for existing maintenance plan.
2. The*.bak files are probably the full backups...
June 11, 2009 at 1:38 pm
Use grant / revoke statements to control specific access writes.
CREATE ROLE SELECT_ONLY;
GRANT SELECT ON TABLE1,TABLE2 TO SELECT_ONLY;
EXEC sp_addrolemember 'SELECT_ONLY', 'USER1';
EXEC sp_addrolemember 'SELECT_ONLY', 'USER2';
Oded
June 11, 2009 at 9:32 am
This problem can indicate that the user that SQL Server instance is running under doesn't have privliges to write on the other disks.
Oded
June 11, 2009 at 9:04 am
Yes there is, you will have to use backup T/SQL command :
BACKUP DATABASE AdventureWorks
TO DISK='\\\AdventureWorks.bak',
Only using T/SQL You can specify the \\PATH.
Oded
June 11, 2009 at 8:48 am
Viewing 13 posts - 1 through 13 (of 13 total)