2zach_john:

"Server 1 db pubs replicates to server 2 db pubreadonly.

...

Log shipping is for disaster recovery not for giving your users a database to run reports off of."

- I already...

Here it is:

RESTORE HEADERONLY

FROM disk = 'D:\ONEC\ONEC_diff.BAK'

--------------------------------------------

BackupName,BackupDescription,BackupType,ExpirationDate,Compressed,Position,DeviceType,UserName,ServerName,DatabaseName,DatabaseVersion,DatabaseCreationDate,BackupSize,FirstLsn,LastLsn,CheckpointLsn,DifferentialBaseLsn,BackupStartDate,BackupFinishDate,SortOrder,CodePage,UnicodeLocaleId,UnicodeComparisonStyle,CompatibilityLevel,SoftwareVendorId,SoftwareVersionMajor,SoftwareVersionMinor,SoftwareVersionBuild,MachineName,Flags,BindingId,RecoveryForkId,Collation

,,5,,0,1,2,DOMAIN.CENTER\sql_admin,SPICA,ONEC,539,2001-10-06 14:15:37.000,43902976,1113000000026400011,1113000000026900001,1113000000026400011,1112000000320600011,2003-07-17 13:34:27.000,2003-07-17 13:34:41.000,106,227,1033,196609,80,4608,8,0,760,SPICA,0,{25F1C387-968E-11D3-8CCC-0090278CBDBB},{59362432-EF65-410B-AB37-174F07E01A37},SQL_Latin1_General_CP1251_CI_AS

(1 row(s) affected)

=====================================================

RESTORE HEADERONLY

FROM disk = 'D:\ONEC\ONEC.TLF'

-----------------------------------------------------

BackupName,BackupDescription,BackupType,ExpirationDate,Compressed,Position,DeviceType,UserName,ServerName,DatabaseName,DatabaseVersion,DatabaseCreationDate,BackupSize,FirstLsn,LastLsn,CheckpointLsn,DifferentialBaseLsn,BackupStartDate,BackupFinishDate,SortOrder,CodePage,UnicodeLocaleId,UnicodeComparisonStyle,CompatibilityLevel,SoftwareVendorId,SoftwareVersionMajor,SoftwareVersionMinor,SoftwareVersionBuild,MachineName,Flags,BindingId,RecoveryForkId,Collation

,,2,,0,1,2,DOMAIN.CENTER\sql_admin,SPICA,ONEC,539,2001-10-06 14:15:37.000,2156032,1112000000094700001,1112000000499500001,1112000000440000009,1112000000320600011,2003-07-17 12:45:00.000,2003-07-17 12:45:01.000,106,227,1033,196609,80,4608,8,0,760,SPICA,0,{25F1C387-968E-11D3-8CCC-0090278CBDBB},{59362432-EF65-410B-AB37-174F07E01A37},SQL_Latin1_General_CP1251_CI_AS

,,2,,0,2,2,DOMAIN.CENTER\sql_admin,SPICA,ONEC,539,2001-10-06 14:15:37.000,647168,1112000000499500001,1112000000609100001,1112000000440000009,1112000000320600011,2003-07-17 13:00:00.000,2003-07-17 13:00:01.000,106,227,1033,196609,80,4608,8,0,760,SPICA,0,{25F1C387-968E-11D3-8CCC-0090278CBDBB},{59362432-EF65-410B-AB37-174F07E01A37},SQL_Latin1_General_CP1251_CI_AS

,,2,,0,3,2,DOMAIN.CENTER\sql_admin,SPICA,ONEC,539,2001-10-06 14:15:37.000,122880,1112000000609100001,1112000000615900001,1112000000440000009,1112000000320600011,2003-07-17 13:14:59.000,2003-07-17 13:15:01.000,106,227,1033,196609,80,4608,8,0,760,SPICA,0,{25F1C387-968E-11D3-8CCC-0090278CBDBB},{59362432-EF65-410B-AB37-174F07E01A37},SQL_Latin1_General_CP1251_CI_AS

,,2,,0,4,2,DOMAIN.CENTER\sql_admin,SPICA,ONEC,539,2001-10-06 14:15:37.000,253952,1112000000615900001,1112000000641700001,1112000000440000009,1112000000320600011,2003-07-17 13:30:00.000,2003-07-17 13:30:01.000,106,227,1033,196609,80,4608,8,0,760,SPICA,0,{25F1C387-968E-11D3-8CCC-0090278CBDBB},{59362432-EF65-410B-AB37-174F07E01A37},SQL_Latin1_General_CP1251_CI_AS

,,2,,0,5,2,DOMAIN.CENTER\sql_admin,SPICA,ONEC,539,2001-10-06 14:15:37.000,975872,1112000000641700001,1113000000167200001,1113000000026400011,1112000000320600011,2003-07-17 13:45:00.000,2003-07-17...

2zach_john:

"If you need to a have a database for your users to do reporting against setup to the same server that your log shipping to. This way you'll get dual...

I used EM to restore full backup first with "leave database non operational, but able to restore additional transactional logs" option (OK), then restored diff backup with the same option...

Here it is:

Server: Msg 8116, Level 16, State 2, Line 1

Argument data type ntext is invalid for argument 1 of len function.

🙁

It works fine, but on the 20th line, for:

exec sp_unprepare 12

It returns this:

Server: Msg 536, Level 16, State 3, Line 1

Invalid length parameter passed to the substring function. 🙁

...

"See if some stored procedures are creating huge temp tables."

- The tempdb itself stays very little ~300Mb(as it was created), its log is growing...

Another thougth:

Understanding the impact of periodic file grouth I work we a server that is not recomended to restart even at night: hundreds of users, so it will be more...

The tempdb itself is not causing problems, its log does. It is located on a 18Gb mirror with other databases logs. The other logs consume ~1,7Gb of space...

2a5xo3z1:

Not yet... Will get the first issue in august or september. I could not find this article online. Will try to find something about it on Microsoft...

What will happen if the size of the tempdb log goes close to 18Gb? The server will stop, because it will not allow other databases logs to grow. ...

Sorry, a little misprint:

not 50%, but 50Mb

I am sure, that no one did this today. This is my authority.

But for this problem I found a very unusual cure:

I limited the grouth rate of...

I am afraid this is not the case, because the tempdb itself is not growing. It started today from 300Mb for data and 500Mb for log. Now it...

Currently I have both data and logs on the same disk array(Raid5), I just want to create another log file on a newly installed mirror and delete the first log...