sirvikasrana (7/14/2014)

---

Here is my Code:

RESTORE DATABASE SomeDBTest FROM DISK = 'E:\MSSQLBackup\SomeDB.bak'

WITH RECOVERY, REPLACE,

MOVE 'SomeDBTest' TO 'E:\MSSQLBackup\SomeDBTest.mdf',

MOVE 'SomeDBTest_Log' TO 'E:\MSSQLBackup\SomeDBTest_log.ldf'

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

Msg 3234, Level 16, State 2, Line 2

Logical file 'SomeDBTest' is...

Cool. Read up (in Books Online, the help file) on GROUP BY and Count. That should set you on the right track.

Not the article itself. The kb that it links to which describes a bug with (I think) snapshot replication.

sirvikasrana (7/14/2014)

---

Grant Fritchey (7/14/2014)

---

sirvikasrana (7/14/2014)

---

Hema kumar-337490 (7/14/2014)

---

Since you are trying to restore the DB on the same server and both source and destination databases exist exist in the same location....

sirvikasrana (7/14/2014)

---

GilaMonster (7/14/2014)

---

You're specifying logical file names that don't exist. According to the...

I'm still working on mine. Dunno how Steampunk it is though. Limited by the requirement it be easy to pack.

Also, find my "Why is my transaction log full" article here. There's a link in there to a kb article on a bug in snapshot replication (I think) which can...

I don't know them, but I'm sure that's a temporary condition.

I will pack my Starflux cards, maybe Avalon too.

Merge doesn't use the transaction log. Are you sure there's no transactional replication set up, intentionally or otherwise? Transactional replication is what can prevent log reuse.

DateTime2 probably

Read up on GROUP BY and COUNT.

You're specifying logical file names that don't exist. According to the error message,...

You need to use WITH REPLACE on the restore. Since you're overwriting the DB that's there, I don't understand why you say you can't use that option.

This site is for Microsoft SQL Server. As such, we can't necessarily help with problems on non-SQL Server platforms. You'll probably get better help if you find forums specifically for...

Daily? Does that meet your data loss SLAs in cases where mirroring doesn't help (like an accidentally dropped table)?