Rem70Rem (2/28/2014)

---

Hi,

What is the best way to move a Production database to a test one ever days after processing is done ?

I am thinking about backup/restore as...

eligiable (3/2/2014)

---

Hi All,

I'm trying to update the following table (SQL Server 2008 R2):

MerchantNoTerminalNoCounterNo

7000001370000014NULL

7000001370000015NULL

7000001370000016NULL

7000001370000013NULL

7000003270000032NULL

7000003270000031NULL

I need the CounterNo to be updated as following, against TerminalNo:

MerchantNoTerminalNoCounterNo

7000001370000014Counter 4

7000001370000015Counter 3

7000001370000016Counter 2

7000001370000013Counter 1

7000003270000032Counter 2

7000003270000031Counter 1

I'm trying...

you don't seem to be making any account for mounted volumes in your script, you must try to move away from legacy system catalogs and look at the new catalogs...

Marios Philippopoulos (2/27/2014)

---

Perry Whittle (2/27/2014)

---

Marios Philippopoulos (2/26/2014)

---

We have an active-passive cluster with 2 nodes, A and B, hosting a failover-cluster SQL instance (FCI).

When first installing the FCI, we first installed...

Marios Philippopoulos (2/26/2014)

---

We have an active-passive cluster with 2 nodes, A and B, hosting a failover-cluster SQL instance (FCI).

When first installing the FCI, we first installed it on A and...

see this link from Microsoft

seandakid (2/26/2014)

---

Awesome Matt! Thanks for the information. I was indeed speaking about the requirement when dealing with data at rest.

I am wondering if anyone has any documentation confirming this...

In the connect dialog the instance name should be

Computername\SQLEXPRESS

robin.pryor (2/26/2014)

---

Thanks for all the advice! I ended up deciding against restoring the system db's. There's too much complexity in the security and the jobs to chance bringing it down...

AlwaysOn databases are bound to an AlwaysOn group,...

That is another way. Typically time it so the database is migrated fairly soon...

grantbanjo (2/24/2014)

---

Hello,

I first ran a search for on the Internet and then on SQL Server Central for this situation, but was unable to find a close match.

I have SQL Server...

When you attach\restore the 2005 database to 2008 the database will go through an internal SQL Server upgrade, this does complete a fair amount of logical checks. Get the database...

check the cluster events for any errors. Have you perfomed a cluster validation after adding the new node to the Windows cluster but before attempting to run the SQL Server...

Have you checked the restore job step history closely. The step may indicate restore issues but still marks as successful.