SQL Server 2005 Question

SandEagle

Lifer
Aug 4, 2007
16,809
13
0
We're conducting a major switch upgrade this weekend that will effectively knock out all network connectivity within our location. Is it okay to leave the SQL Server databases online and re-establish connection once connectivity is restored? Or should we consider shutting down the SQL services and/or server?

thanks
 

Rage187

Lifer
Dec 30, 2000
14,276
4
81
sql should be fine. if you are that worried about it just stop the instance in studio management by right clicking it and choosing STOP. You can also just stop the service.
 

SandEagle

Lifer
Aug 4, 2007
16,809
13
0
Originally posted by: Rage187
sql should be fine. if you are that worried about it just stop the instance in studio management by right clicking it and choosing STOP. You can also just stop the service.

thanks! so no database corruption or anything to worry about if we just leave it as is and restore network connection after maintenance is complete? kinda what I figured too...
 

ebaycj

Diamond Member
Mar 9, 2002
5,418
0
0
Correction.

It will be fine IF IT IS NOT IN A CLUSTER.

It WILL DEFINITELY cause problems if it is in a clustered environment and you kill all network connectivity to the cluster. Trust me, This has happened to me before. Stupid networking people.
 

ebaycj

Diamond Member
Mar 9, 2002
5,418
0
0
Originally posted by: ebaycj
Correction.

It will be fine IF IT IS NOT IN A CLUSTER.

It WILL DEFINITELY cause problems if it is in a clustered environment and you kill all network connectivity to the cluster. Trust me, This has happened to me before. Stupid networking people.

Also, it really depends on your applications as to whether there will be any data level corruption or not.

SQL Server itself should be fine, Correctly designed applications should be fine. Badly designed (home grown, usually) applications might not be fine.

What may happen is that if the application does not correctly "bundle" its SQL work units into SQL transactions, they may be partially committed when the network connection cuts (data in one table but not in another, when data is always expected in both, for example).

This would lead to SQL being fine and not showing any errors, but your application would likely have problems, maybe even sporadic problems, depending on how things are designed.