Viewing 15 posts - 2,281 through 2,295 (of 9,253 total)
they're attempting to shrink the secondary databases files, is that correct?
March 9, 2015 at 5:09 pm
I'd like to know a bit more about the columns in this table, given the potential max row size compression may be of no benefit at all
March 9, 2015 at 11:47 am
see if what is running on the primary node?
code running from where?
March 9, 2015 at 11:05 am
jitendra.padhiyar (3/9/2015)
Still my question is unanswered :crying:How we can install multiple instances on cluster ?
Read my stairway series on this site!
jitendra.padhiyar (3/9/2015)
March 9, 2015 at 11:04 am
ok, so here's the thing, the more readonly workload you pass to the secondary the more it can impede the redo thread and so, the further behind the secondary may...
March 9, 2015 at 10:47 am
the redo obviously has some latency here. Why is the application being forced to read a secondary in this case, it should be querying the primary I would have thought
March 9, 2015 at 9:34 am
why would you want to shrink the log for it just to grow again?
Find out whats causing the log growth first, is the mirror session synchronised or are you storing...
March 9, 2015 at 8:05 am
SQL Server 2005 is not supported on Windows 2012, I'd be very surprised if the installer even lets you complete the install
See this link
March 9, 2015 at 7:53 am
first thing I would ask is what is the recovery model in use on the DW database?
I'm sure you've heard a hundred times "don't shrink your transaction logs".
If you haven't...
March 9, 2015 at 7:51 am
you are also specifying the same replicas secondary role twice, so be careful with that too.
I can see from the query results that luckily QA-DB-DATA2-1A is set to accept readonly...
March 6, 2015 at 9:58 am
T-SQL??
something along the lines of
restore database [thesecondarydb] from disk =
'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\primarydb_diff_backup.bak'
with move 'logicalname' to 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\secondarydb_datafile.mdf',
move 'logicalname' to 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\secondarydb_logfile.ldf'
, replace, norecovery
March 6, 2015 at 4:25 am
need to see the complete history, but its restored 0 files. You likely have an LSN gap.
on the 2 servers that are not working as expected please run the following...
March 6, 2015 at 3:54 am
FabricioLimaDBA (3/5/2015)
The problems with AVG is that only works with enterprise edition.Then I continue to use database mirroring in clients with SQL Standard.
Yes, but you're limited to synch only mode...
March 6, 2015 at 3:48 am
sherrerk (3/5/2015)
I add applicationintent=readonly to the connection string and it connects to the secondary with default database master.
When connecting to a readable secondary you need to specify the database name...
March 6, 2015 at 3:35 am
also, dump the step output history and check for logs being skipped, etc. use this query
selectj.name
, s.step_name
, h.message
, h.sql_severity
from
msdb..sysjobs j inner join msdb..sysjobsteps s
on j.job_id = s.job_id
inner join...
March 5, 2015 at 10:33 am
Viewing 15 posts - 2,281 through 2,295 (of 9,253 total)