Support NeoGAF

[cubicle47b]

So I found a few interesting things in SQL Server 2000 today and I'm freakin' amazed, really.

1. As the owner of a database I can take it offline but I can't bring it back online. Why? Because the owner role is stored at the database level. When I try to bring it back online I don't have the rights because the rights aren't seen by SQL Server.

2. If your default database is set to an offline database you can't register that server in Enterprise Manager or access the server through Query Analyzer.


So, to cut this story short, I had to call our customer in Puerto Rico and tell their system admin to bring our database online.

 

[cubicle47b]

Xbox development is pretty cool. I could talk about that...?

 

[Manics]

So I found a few interesting things in SQL Server 2000 today and I'm freakin' amazed, really.

Here at work we lovingly call "Enterprise Manager", "Enterprise Mangler"

 

[xsarien]

Here at work we lovingly call "Enterprise Manager", "Enterprise Mangler"

Oh?

I call it "Well, at least it isn't the Access 'database'."

 

[sefskillz]

someone get me a job already. graduating college sucks.

 

[explodet]

Stuff like this is why I don't touch SQL2000 unless I'm just running queries or exporting tables. o_o

 

[ATJaguarX]

If you take it offline, how would expect to bring it back up?

 

[cubicle47b]

I'd expect to bring it back up through Enterprise Manager or Query Analyzer. I'd expect Sql Server to store my owner role on the server level (in the master table) or not let me take it offline.

 

[Manics]

I'd expect to bring it back up through Enterprise Manager or Query Analyzer. I'd expect Sql Server to store my owner role on the server level (in the master table) or not let me take it offline.

What do you think this is, Star Trek?