kranthi.india123 (2/16/2012)

---

Thank you SSCarpal Tunnel

Configured log shipping--SuccessFully working.

so My qustions is?

If i shrink primary database it will affect log shipping?

If i shrink mdf it will affect log shipping?

If i shrink...

you want sp_update_job

I'd just dynamically create the sql statements via a select out of sysjobs, this script [/url]does a simialar thing with a bit of extra complication.

If you lose a log backup in the chain for whatever reason you would need to reinitialise log shipping from a full backup.

Failover after Loss of the primary depends on...

A shrink does NOT break the log chain. Any idea why your log is so big?

Please clarify your other questions

Only back up the log via the logshipping jobs. There is no need for the duplication and the info in the logshipping tables will be incorrect

the backup will be only 256GB.

Is this the database you are moving be detach\attach in thread

http://www.sqlservercentral.com/Forums/Topic1251467-146-1.aspx#bm1252191 ?

If so leave the file sizes as they are as you will not be...

right click the server, select properties - security, select mixed mode, restart the instance.

the size of the files will be 591102.25 MB, actual space used in the database (i.e about the size a backup would be) is 256965096 KB

for a service account you want the password set not to expire, has that property been set?

Was the password changed in AD but not in SQL configuration manager

Is any other...

that should be done AFTER the migration.

If all objects were owned by dbo in SQL2000 (and they very probably were) you want the dbo schema to be the first schema...

Sys.dm_db_index_usage stats will give you reads and updates (and therefore writes) per index, you could use that to give you an idea.

sys.dm_io_virtual_file_stats is at database file level.

You can take full backups of logshipped databases, full backups do not truncate the log or break the LSN chain.

You can run any other process on logshipped databases EXCEPT log...

9.00.5057 is SP4 + security patch MS11 -049 - you are already completely up to date so nothing to upgrade.

EXACTLY the same rules and caveats apply as SQL2008, but just as doable

compatibilty level would be 90

please post the results of select @@version and the file names of the .exe files you are using for the upgrade