builtin\adminstrators

what is best practice with this group account?
it is installed by default, if i understand correctl, it gives anyone who is
in the server admin group, admin rights to sql server. isn't that a bad id
ea?See:
SQL Server 2000 SP3 Security Features and Best Practices
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
i believe have looked at this article before...however, i just reviewed it
again.
where does this article address my question specifically..am i missing it.
thanks|||Hi Kevin,
Thanks for your update. As the SQL Server 2000 security model is based on
the Windows security model and as the system administrator of windows
operating system, it will have permission on all the activities on the SQL
Server since they are combined together. So, 'buildin\admin' security will
depends on the windows security model for it. SQL Server will benifit from
the Windows security architecture. Please refer to the following article:
Authentication Modes
http://msdn.microsoft.com/library/e...curity_47u6.asp
Security Architecture
http://msdn.microsoft.com/library/e...curity_4fol.asp
Hope this helps. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||let me put it this way, if you have os adminstrators who are in the local ad
ministrators group and you don't want them to have admin rights to the sql s
erver...then you should i remove the builtin\administrators group from the
sql server logins.....is t
hat correct?
thanks
-jason|||Yes.
The following article has a section with links to some
issues that could come up if you remove the group:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
-Sue
On Wed, 14 Apr 2004 14:01:06 -0700, "jason" <jason_fin>
wrote:

>let me put it this way, if you have os adminstrators who are in the local administr
ators group and you don't want them to have admin rights to the sql server...then y
ou should i remove the builtin\administrators group from the sql server logins.....
is
that correct?
>thanks
>-jason|||Hi Kevin,
I just want to add some more information to your question. Please look at
the
"Step 11. SQL Server Logins, Users, and Roles" in "Securing Your Database
Server" at
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/THCMCh18.asp
That is, if you differentiate the role of domain administrator and database
administrator. You'd better remove the BUILTIN\Administrators SQL Server
login and then create a specific Windows group containing specific database
administrations added to SQL server as a server login.
Hope this helps. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi,
I am reviewing you post. Since we have not heard from you for some time, I
wonder if you still have quesitons of the information I provided. For any
question, please feel free to post new message here and we are glad to
help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Thanks Sue and Biasong,
the reason it takes me a while to tget back is because that nospam alias acc
ount doesn't work as far as sending me notifications for replys.
thanks
-jason

Building a database

I am working with SQL server 2000. The database is installed in my machine. Now I have got the ".ldf" and ".mdf" file pertaining to a database from someother server.

Is it possible to build the database present in the above said files in my server.

NOTE : I dont have a direct access to the remote server from where the above said files were obtained (otherwise I think the DTS utility would have come in handy).An example from The Holy book
This example attaches two files from pubs to the current server.

EXEC sp_attach_db @.dbname = N'pubs', @.filename1 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf', @.filename2 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs_log.ldf'|||Thanks for the instant help . That worked !|||BTW, the imported database seems to have a lot of procedures like dt_addtosourcecontrol, dt_adduserobject etc.. what are these for ?|||You might want to take a peek at Microsoft Knowledge Base Article 218172 when attaching/detaching databases on different servers.

Build numbers

I am trying to restore a master database after a server rebuild and need to
get the build number back to 8.00.818. I have installed (or so I thought) t
he SP3a and the 8-11-03 patch to get it to that build number but when I chec
k the build number in Enter
prise Manager it still shows 8.00.194. Help?How are you getting the build number from Enterprise Manager? You should
connect to your SQL Server using Query Analyzer and run the following
command to get the SQL Server's build number:
SELECT @.@.VERSION
GO
May be you haven't installed the service pack on the client machines.
This might be helpful: http://vyaskn.tripod.com/sqlsps.htm
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:819D85D5-070C-4150-87FB-B9A0C5A2B2FB@.microsoft.com...
I am trying to restore a master database after a server rebuild and need to
get the build number back to 8.00.818. I have installed (or so I thought)
the SP3a and the 8-11-03 patch to get it to that build number but when I
check the build number in Enterprise Manager it still shows 8.00.194. Help?|||I have done that as well to get the build number but under properties of the
sql instance name is where I was getting the information from Enterprise Ma
nager (is that wrong?). And after applying SP3a and the 8-11-03 patch it ha
sn't changed the build info
rmation. I have taken the defaults for installation of the SP and patch. I
Have completely rebuilt the machine and reinstalled SQL so there souldn't b
e anything strange with the installation (all default).|||I wouldn't use Enterprise Manager for this. As I posted earlier, query the
server directly. What do you get when you run SELECT @.@.VERSION?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:D18A75A7-4AC6-4917-9334-F056D3E0159F@.microsoft.com...
I have done that as well to get the build number but under properties of the
sql instance name is where I was getting the information from Enterprise
Manager (is that wrong?). And after applying SP3a and the 8-11-03 patch it
hasn't changed the build information. I have taken the defaults for
installation of the SP and patch. I Have completely rebuilt the machine and
reinstalled SQL so there souldn't be anything strange with the installation
(all default).|||I get the original build number of the system (8.00.194). The patches don't
seem to be applying or at least don't seem to be affecting the number at al
l and so the restore of the Master Database failes.|||Can't be right :-) I did this on various servers and I see updated build
numbers. You either applied the service pack to the wrong server, or you
haven't applied the service pack at all.
When you run the service pack exe first it extracts itself into a folder.
Many people mistake that and think they've applied the service pack, just by
extracting the service pack. Hope that's not the case with you. If it is,
you have to run the setup from the extracted folder.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:E97EEE10-091F-4DD8-99EB-B9513B38F1B5@.microsoft.com...
I get the original build number of the system (8.00.194). The patches don't
seem to be applying or at least don't seem to be affecting the number at all
and so the restore of the Master Database failes.|||Narayana Vyas Kondreddi wrote:

>Can't be right :-) I did this on various servers and I see updated build
>numbers. You either applied the service pack to the wrong server, or you
>haven't applied the service pack at all.
>When you run the service pack exe first it extracts itself into a folder.
>Many people mistake that and think they've applied the service pack, just b
y
>extracting the service pack. Hope that's not the case with you. If it is,
>you have to run the setup from the extracted folder.
>
Vyas,
Whether or not this is what happened, it never hurts to remind people
how easy it is not to install the update:
How *not* to install sp3a for Microsoft SQL Server 2000
1. Download the service pack file, SQL2KSP3.exe, from Microsoft
2. Run the service pack file SQL2KSP3.exe
3. Click OK when you see the message "the package has been successfully
delivered"
Guess what? The service pack has not been installed! The download page
says you just need to "Install Database Components SP3a (SQL2KSP3.exe),"
so what's going on?
Youi wouldn't know it from the download page, but you now have to go to
the location where you extracted the files and run setup (and if I
recall, there are many files containing the word setup).
SK

>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>
>"Chad" <anonymous@.discussions.microsoft.com> wrote in message
>news:E97EEE10-091F-4DD8-99EB-B9513B38F1B5@.microsoft.com...
>I get the original build number of the system (8.00.194). The patches don'
t
>seem to be applying or at least don't seem to be affecting the number at al
l
>and so the restore of the Master Database failes.
>
>

Build numbers

I am trying to restore a master database after a server rebuild and need to get the build number back to 8.00.818. I have installed (or so I thought) the SP3a and the 8-11-03 patch to get it to that build number but when I check the build number in Enterprise Manager it still shows 8.00.194. Help?How are you getting the build number from Enterprise Manager? You should
connect to your SQL Server using Query Analyzer and run the following
command to get the SQL Server's build number:
SELECT @.@.VERSION
GO
May be you haven't installed the service pack on the client machines.
This might be helpful: http://vyaskn.tripod.com/sqlsps.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:819D85D5-070C-4150-87FB-B9A0C5A2B2FB@.microsoft.com...
I am trying to restore a master database after a server rebuild and need to
get the build number back to 8.00.818. I have installed (or so I thought)
the SP3a and the 8-11-03 patch to get it to that build number but when I
check the build number in Enterprise Manager it still shows 8.00.194. Help?|||I have done that as well to get the build number but under properties of the sql instance name is where I was getting the information from Enterprise Manager (is that wrong?). And after applying SP3a and the 8-11-03 patch it hasn't changed the build information. I have taken the defaults for installation of the SP and patch. I Have completely rebuilt the machine and reinstalled SQL so there souldn't be anything strange with the installation (all default).|||I wouldn't use Enterprise Manager for this. As I posted earlier, query the
server directly. What do you get when you run SELECT @.@.VERSION?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:D18A75A7-4AC6-4917-9334-F056D3E0159F@.microsoft.com...
I have done that as well to get the build number but under properties of the
sql instance name is where I was getting the information from Enterprise
Manager (is that wrong?). And after applying SP3a and the 8-11-03 patch it
hasn't changed the build information. I have taken the defaults for
installation of the SP and patch. I Have completely rebuilt the machine and
reinstalled SQL so there souldn't be anything strange with the installation
(all default).|||I get the original build number of the system (8.00.194). The patches don't seem to be applying or at least don't seem to be affecting the number at all and so the restore of the Master Database failes.|||Can't be right :-) I did this on various servers and I see updated build
numbers. You either applied the service pack to the wrong server, or you
haven't applied the service pack at all.
When you run the service pack exe first it extracts itself into a folder.
Many people mistake that and think they've applied the service pack, just by
extracting the service pack. Hope that's not the case with you. If it is,
you have to run the setup from the extracted folder.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:E97EEE10-091F-4DD8-99EB-B9513B38F1B5@.microsoft.com...
I get the original build number of the system (8.00.194). The patches don't
seem to be applying or at least don't seem to be affecting the number at all
and so the restore of the Master Database failes.|||Narayana Vyas Kondreddi wrote:
>Can't be right :-) I did this on various servers and I see updated build
>numbers. You either applied the service pack to the wrong server, or you
>haven't applied the service pack at all.
>When you run the service pack exe first it extracts itself into a folder.
>Many people mistake that and think they've applied the service pack, just by
>extracting the service pack. Hope that's not the case with you. If it is,
>you have to run the setup from the extracted folder.
>
Vyas,
Whether or not this is what happened, it never hurts to remind people
how easy it is not to install the update:
How *not* to install sp3a for Microsoft SQL Server 2000
1. Download the service pack file, SQL2KSP3.exe, from Microsoft
2. Run the service pack file SQL2KSP3.exe
3. Click OK when you see the message "the package has been successfully
delivered"
Guess what? The service pack has not been installed! The download page
says you just need to "Install Database Components SP3a (SQL2KSP3.exe),"
so what's going on?
Youi wouldn't know it from the download page, but you now have to go to
the location where you extracted the files and run setup (and if I
recall, there are many files containing the word setup).
SK
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>
>"Chad" <anonymous@.discussions.microsoft.com> wrote in message
>news:E97EEE10-091F-4DD8-99EB-B9513B38F1B5@.microsoft.com...
>I get the original build number of the system (8.00.194). The patches don't
>seem to be applying or at least don't seem to be affecting the number at all
>and so the restore of the Master Database failes.
>
>