Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
aiken
Aged Yak Warrior
525 Posts |
 Posted - 2003-05-30 : 15:52:51
|
| Well, I have to say that I'm very impressed with this new IBM x345 that I'm setting up. That is one fast machine.Too fast, in fact. SQL server is configured to log on as a domain account, and when the machine boots, SQL server starts before W2K gets the network up, so SQL fails to login, and therefore fails to start.Is there any way to tell SQL server to wait X seconds before starting? Or to try to login repeatedly?Thanks-b |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-05-30 : 16:03:41
|
| Options:If you go to the Recovery tab for the MSSQLSERVER service, you can specify what to do when it fails. You could create a batch job that does a NET START which runs at startup. You could also use a local account but that could/would give you problems when your server needs to connect to other SQL Serverds.Have someone figure out why the network isn't up on the box before the service attempts to start? -->I would start here because there must be a problem.Tara |
 |
|
|
aiken
Aged Yak Warrior
525 Posts |
Posted - 2003-05-30 : 16:11:50
|
| I think the network issue is realated to the Alteon switch that it's plugged into; it always takes that switch about 15-20 seconds to put a port live. Usually it's not an issue, but in this caseit is.I'll look into the recovery options first; thanks for the idea. The batch idea is ugly, because the machine will be unattended and nobody will be logging in. Still, it would probably be possible to write a small service which just waits X seconds and then does the net start.Thanks for the ideas.-b |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2003-05-31 : 12:50:55
|
| Are you receiving any other errors in your system or application event logs? What is the exact error you are getting now? Your message about the alteon switch is interesting. Are you using autodetect for the speed/duplex of your ethernet adapters? Try forcing this in both the switch and the server to 100/full or 1000/full (depending if you have gigabit of course)-ecEdited by - eyechart on 06/02/2003 00:50:55 |
|
|
|
aiken
Aged Yak Warrior
525 Posts |
Posted - 2003-06-05 : 03:48:45
|
| Sorry to lag. Forcing both the machine and the switch fixed the problem.Thanks-b |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2003-06-05 : 10:11:00
|
| I have run into this problem quite a bit lately. If the machine and the switch are not both forced to the same speed you get all sorts of crazy stuff happening on the server and the network.Jeff Banschbach, MCDBA |
|
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2003-06-05 : 12:47:53
|
| We've had similar problems with some Cisco networking hardware. If we let everything autosense, it took 10-15 seconds to get on the network, and once you were on the network you were at 10Mbps, instead of 100Mbps. Yikes!Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
|
|
|
|
|
|
|
|
New SQL server *too* fast...