July 20, 2013 at 12:19 am
Hi All
1.In mirroring If I add data file in primary server will it reflect in mirror server or not?
If yes can you pls explain me?
2.In transactional replication if we get ‘ log file full on subscriber end’ then how to resolve the issue.
3.In transactional replication with updatable subscriber I have added the data file at subscriber end but it is not reflecting at the publisher end.What should I do to resolve it?
4.In log shipping secondary server if we get log file is full then how to resolve the issue.
July 20, 2013 at 3:06 am
rajeshn29.dba (7/20/2013)
Hi All1.In mirroring If I add data file in primary server will it reflect in mirror server or not?
If yes can you pls explain me?
2.In transactional replication if we get ‘ log file full on subscriber end’ then how to resolve the issue.
3.In transactional replication with updatable subscriber I have added the data file at subscriber end but it is not reflecting at the publisher end.What should I do to resolve it?
4.In log shipping secondary server if we get log file is full then how to resolve the issue.
1. Please refer Gail's comment; Thanks Gail.
2. Do the same workaround as how you will do for other databases. Check the log_reuse_wait_desc column from sys.databases and do accordingly. Ideally you can keep the database in 'SIMPLE' recovery.
3. Refer 1.
4. Shrinking the files in PRIMARY will reflect in SECONDARY in LS/ Mirroring. So shrink the log file in Primary.
July 20, 2013 at 3:32 am
rajeshn29.dba (7/20/2013)
Hi All1.In mirroring If I add data file in primary server will it reflect in mirror server or not?
If yes can you pls explain me?
Yes, it'll be reflected just fine. Just make sure that the secondary has the same drive letters as the primary
2.In transactional replication if we get ‘ log file full on subscriber end’ then how to resolve the issue.
Please read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/
3.In transactional replication with updatable subscriber I have added the data file at subscriber end but it is not reflecting at the publisher end.What should I do to resolve it?
Add it at the publisher. Replication replicates data changes, not database structure changes.
4.In log shipping secondary server if we get log file is full then how to resolve the issue.
Log shipping secondary won't run out of log space. The primary might.
Please read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 20, 2013 at 3:33 am
balasaukri (7/20/2013)
4. Shrinking the files in PRIMARY will reflect in SECONDARY in LS/ Mirroring. So shrink the log file in Primary.
Attempting to shrink a full log is just a waste of time. It's full, there's no space in the file to release to the OS, so why on earth would you try to shrink (release free space to the OS)?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 22, 2013 at 4:36 am
rajeshn29.dba (7/20/2013)
Hi All1.In mirroring If I add data file in primary server will it reflect in mirror server or not?
If yes can you pls explain me?
2.In transactional replication if we get ‘ log file full on subscriber end’ then how to resolve the issue.
3.In transactional replication with updatable subscriber I have added the data file at subscriber end but it is not reflecting at the publisher end.What should I do to resolve it?
4.In log shipping secondary server if we get log file is full then how to resolve the issue.
Are they interview questions, too many topics covered.
Regards
Durai Nagarajan
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply