Create Database

From: Roy (rx46@hotmail.com)
Date: 03/18/03

  • Next message: Paul Ritchie: "Restrict sysadmin database access?" 
    From: "Roy" <rx46@hotmail.com>
Date: Mon, 17 Mar 2003 18:40:30 -0800

    I have installed sql server 2000 on two systems.
    I add my domain account to the system administrion group
    on the second system.
    I add a new sql server registration on the 1st system so
    that it point to the sql server on the 2nd one.
    I launch the Query Analizer and connect to the sql server
    on the 2nd system by using the previous account. Run a
    script to CREATE DATABASE. It fails by telling me that
    there is a permission problem.
    If I run the script on the query analyzer of the 2nd
    system directly, it is successful. So the script itself
    is correct.
    Why can't I create the db on the 2nd system from the 1st
    system by connecting the query analyzer in this case?

  • Next message: Paul Ritchie: "Restrict sysadmin database access?"

    Relevant Pages

    • Re: SP4 Installation Problem on Win2000/SQL Enterprise Edit.
      ... Hmm...didn't helped (the manual MDAC installation)... ... I’ve tried running the script from Query Analyzer as well. ... > Jasper Smith (SQL Server MVP) ... This should indicate why the script failed. ...
      (microsoft.public.sqlserver.setup)
    • Re: Linked Server Connection Problem
      ... Use SQL authentication to connect to the SQL server from the client, ... set the domain account used to start SQL Server to have permissions in the ... Establish a SPN for your domain account which will enable Kerberos ... Load the Active Directory Users and Computers MMC snap-in. ...
      (microsoft.public.sqlserver.connect)
    • Re: SQL Services account question...
      ... I wish you'd say the reason of not using a domain account as a service account for the SQL Server. ... Backup operations are performed by SQL Server service, at this point I don't know what goes on under hood exactly but SQL Server service may be needed to communicate to the AD for validation of the database owner and as the SQL Server service is a local one, it can't achieve this task. ... > Source: Security Event ID: 537 ...
      (microsoft.public.sqlserver.security)
    • Re: Login failed for user NT AUTHORITYANONYMOUS LOGON
      ... >>I've enabled anonymous access, setting it to the correct domain account, ... >> the correct permissions in sql server ... > That means the local user permissions, the SQL Server, etc. ... >> c) I've enabled anonymous access, setting it to the correct domain account, ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Problems changing the password for the service account in SQL
      ... Adding the domain account which runs SQL Server into SQL Server doesn't ... Server if it is running under the domain account. ... Admin-SQL, Logon Exec - exception from ...
      (microsoft.public.sqlserver.security)
    • Quantcast