Multi Row Insert

According to the CTP3 BOL the following code should work just fine, unfortunately is giving me the error message (below the code):

create table FamilyNames (

Id int identity,

[Name] varchar(30)

);

go

insert into FamilyNames values (

('Andersson'),

('Ben-Gan'),

('Carlsson'),

('Davidsen')

);

Msg 213, Level 16, State 1, Line 1
Column name or number of supplied values does not match table definition.

Does anybody know why this code fails?

Hi,

Try

insert into FamilyNames values

('Andersson'),

('Ben-Gan'),

('Carlsson'),

('Davidsen');

Kind regards,

Wesley

|||Thanks.

MSSQLSERVER service security

I have a Windows 2000 server on which I am running SQL Server 2000
SP3. Unfortunately, this particular Windows server has far too many
accounts in the Local Administrators group. Recently we had an
incident in which a production SQL Server was stopped and restarted
unexpectedly. I suspect it was a person who did this since the service
was started back up within a minute or so of being shutdown, and the
SQL Server Agent was not restarted. No one has fessed up yet, and I
don't expect anyone to do so.
Securing the server is a long-term solution, but I need to do
something in the short term to prevent this from happening again. The
only thing I can think to do is to further limit who can stop and
start the SQL Server Service. Is there a way to specify who can and
cannot stop/start the SQL Server service, excluding even members of
the Local Administrators group?
P.S. Auditing has been ruled out as an option.
Thanks,
Aaron
Hi,
OS Users who fall under local admin group can stop and start any services.
The best solution is to remove the
users from Local admin groups of sql server machine.
Thanks
Hari
MCDBA
"Vols Fan" <volsfan1998@.hotmail.com> wrote in message
news:2489efb1.0407191441.7c492135@.posting.google.c om...
> I have a Windows 2000 server on which I am running SQL Server 2000
> SP3. Unfortunately, this particular Windows server has far too many
> accounts in the Local Administrators group. Recently we had an
> incident in which a production SQL Server was stopped and restarted
> unexpectedly. I suspect it was a person who did this since the service
> was started back up within a minute or so of being shutdown, and the
> SQL Server Agent was not restarted. No one has fessed up yet, and I
> don't expect anyone to do so.
> Securing the server is a long-term solution, but I need to do
> something in the short term to prevent this from happening again. The
> only thing I can think to do is to further limit who can stop and
> start the SQL Server Service. Is there a way to specify who can and
> cannot stop/start the SQL Server service, excluding even members of
> the Local Administrators group?
> P.S. Auditing has been ruled out as an option.
> Thanks,
> Aaron
|||I am aware of this, but as I said, until we can further secure this
server, I need a short term solution.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message news:<e5EEzXhbEHA.3480@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> Hi,
> OS Users who fall under local admin group can stop and start any services.
> The best solution is to remove the
> users from Local admin groups of sql server machine.
> --
> Thanks
> Hari
> MCDBA
> "Vols Fan" <volsfan1998@.hotmail.com> wrote in message
> news:2489efb1.0407191441.7c492135@.posting.google.c om...

MSSQLSERVER service security

I have a Windows 2000 server on which I am running SQL Server 2000
SP3. Unfortunately, this particular Windows server has far too many
accounts in the Local Administrators group. Recently we had an
incident in which a production SQL Server was stopped and restarted
unexpectedly. I suspect it was a person who did this since the service
was started back up within a minute or so of being shutdown, and the
SQL Server Agent was not restarted. No one has fessed up yet, and I
don't expect anyone to do so.
Securing the server is a long-term solution, but I need to do
something in the short term to prevent this from happening again. The
only thing I can think to do is to further limit who can stop and
start the SQL Server Service. Is there a way to specify who can and
cannot stop/start the SQL Server service, excluding even members of
the Local Administrators group?
P.S. Auditing has been ruled out as an option.
Thanks,
AaronHi,
OS Users who fall under local admin group can stop and start any services.
The best solution is to remove the
users from Local admin groups of sql server machine.
Thanks
Hari
MCDBA
"Vols Fan" <volsfan1998@.hotmail.com> wrote in message
news:2489efb1.0407191441.7c492135@.posting.google.com...
> I have a Windows 2000 server on which I am running SQL Server 2000
> SP3. Unfortunately, this particular Windows server has far too many
> accounts in the Local Administrators group. Recently we had an
> incident in which a production SQL Server was stopped and restarted
> unexpectedly. I suspect it was a person who did this since the service
> was started back up within a minute or so of being shutdown, and the
> SQL Server Agent was not restarted. No one has fessed up yet, and I
> don't expect anyone to do so.
> Securing the server is a long-term solution, but I need to do
> something in the short term to prevent this from happening again. The
> only thing I can think to do is to further limit who can stop and
> start the SQL Server Service. Is there a way to specify who can and
> cannot stop/start the SQL Server service, excluding even members of
> the Local Administrators group?
> P.S. Auditing has been ruled out as an option.
> Thanks,
> Aaron|||I am aware of this, but as I said, until we can further secure this
server, I need a short term solution.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message news:<e5EEzXhbEHA.3480@.TK2MSFTNGP
11.phx.gbl>...[vbcol=seagreen]
> Hi,
> OS Users who fall under local admin group can stop and start any services.
> The best solution is to remove the
> users from Local admin groups of sql server machine.
> --
> Thanks
> Hari
> MCDBA
> "Vols Fan" <volsfan1998@.hotmail.com> wrote in message
> news:2489efb1.0407191441.7c492135@.posting.google.com...

MSSQLSERVER service security

I have a Windows 2000 server on which I am running SQL Server 2000
SP3. Unfortunately, this particular Windows server has far too many
accounts in the Local Administrators group. Recently we had an
incident in which a production SQL Server was stopped and restarted
unexpectedly. I suspect it was a person who did this since the service
was started back up within a minute or so of being shutdown, and the
SQL Server Agent was not restarted. No one has fessed up yet, and I
don't expect anyone to do so.
Securing the server is a long-term solution, but I need to do
something in the short term to prevent this from happening again. The
only thing I can think to do is to further limit who can stop and
start the SQL Server Service. Is there a way to specify who can and
cannot stop/start the SQL Server service, excluding even members of
the Local Administrators group?
P.S. Auditing has been ruled out as an option.
Thanks,
AaronHi,
OS Users who fall under local admin group can stop and start any services.
The best solution is to remove the
users from Local admin groups of sql server machine.
--
Thanks
Hari
MCDBA
"Vols Fan" <volsfan1998@.hotmail.com> wrote in message
news:2489efb1.0407191441.7c492135@.posting.google.com...
> I have a Windows 2000 server on which I am running SQL Server 2000
> SP3. Unfortunately, this particular Windows server has far too many
> accounts in the Local Administrators group. Recently we had an
> incident in which a production SQL Server was stopped and restarted
> unexpectedly. I suspect it was a person who did this since the service
> was started back up within a minute or so of being shutdown, and the
> SQL Server Agent was not restarted. No one has fessed up yet, and I
> don't expect anyone to do so.
> Securing the server is a long-term solution, but I need to do
> something in the short term to prevent this from happening again. The
> only thing I can think to do is to further limit who can stop and
> start the SQL Server Service. Is there a way to specify who can and
> cannot stop/start the SQL Server service, excluding even members of
> the Local Administrators group?
> P.S. Auditing has been ruled out as an option.
> Thanks,
> Aaron|||I am aware of this, but as I said, until we can further secure this
server, I need a short term solution.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message news:<e5EEzXhbEHA.3480@.TK2MSFTNGP11.phx.gbl>...
> Hi,
> OS Users who fall under local admin group can stop and start any services.
> The best solution is to remove the
> users from Local admin groups of sql server machine.
> --
> Thanks
> Hari
> MCDBA
> "Vols Fan" <volsfan1998@.hotmail.com> wrote in message
> news:2489efb1.0407191441.7c492135@.posting.google.com...
> > I have a Windows 2000 server on which I am running SQL Server 2000
> > SP3. Unfortunately, this particular Windows server has far too many
> > accounts in the Local Administrators group. Recently we had an
> > incident in which a production SQL Server was stopped and restarted
> > unexpectedly. I suspect it was a person who did this since the service
> > was started back up within a minute or so of being shutdown, and the
> > SQL Server Agent was not restarted. No one has fessed up yet, and I
> > don't expect anyone to do so.
> >
> > Securing the server is a long-term solution, but I need to do
> > something in the short term to prevent this from happening again. The
> > only thing I can think to do is to further limit who can stop and
> > start the SQL Server Service. Is there a way to specify who can and
> > cannot stop/start the SQL Server service, excluding even members of
> > the Local Administrators group?
> >
> > P.S. Auditing has been ruled out as an option.
> >
> > Thanks,
> > Aaron

MSSQLServer Service Account

Hi,
We have an automated process which imports a file from a
remote server. Unfortunately this requires the
MSSQLServer service to be running under a domain account
in order to be able to access the remote server. I have
been unable to get SQL Server to start with anything other
than Domain Admin rights.
Do you know what rights are required for the MSSQLServer
service to run?
Thanks,
Phil.Hi,
Requirements for Domain User Account
All domain user accounts must have permission to:
Access and change the SQL Server directory (\Program Files\Microsoft SQL
Server\Mssql).
Access and change the .mdf, .ndf, and .ldf database files.
Log on as a service.
Read and write registry keys at and under:
HKEY_LOCAL_MACHINE\Software\Microsoft\MS
SQLServer.
-or- for any named instance service:
HKEY_LOCAL_MACHINE\Software\Microsoft\Mi
crosoft SQL Server.
HKEY_LOCAL_MACHINE\System\CurrentControl
set\Services\MSSQLServer.
-or- for any named instance:
HKEY_LOCAL_MACHINE\System\CurrentControl
set\Services\MSSQL$Instancename.
HKEY_LOCAL_MACHINE\Software\Microsoft\Wi
ndows NT\CurrentVersion\Perflib.
In addition, a domain user account must be able to read and write
corresponding registry keys for these services: SQLAgent$InstanceName,
MSSearch, and MSDTC.
SQL Server startup user should be:-
Member of local Power Users or local Administrators group
SQL Server Agent should be :-
Member of the Administrators local group
Create CmdExec and ActiveScript jobs belonging to someone other than a SQL
Server administrator.
Thanks
Hari
MCDBA
"Phil" <anonymous@.discussions.microsoft.com> wrote in message
news:2273a01c45cfd$6a7f85c0$a001280a@.phx
.gbl...
> Hi,
> We have an automated process which imports a file from a
> remote server. Unfortunately this requires the
> MSSQLServer service to be running under a domain account
> in order to be able to access the remote server. I have
> been unable to get SQL Server to start with anything other
> than Domain Admin rights.
> Do you know what rights are required for the MSSQLServer
> service to run?
> Thanks,
> Phil.|||If you change the service accounts using Enterprise Manager,
the rights and permissions are handled for you. Otherwise
you need to manage these manually and follow this article:
HOW TO: Change the SQL Server or SQL Server Agent Service
Account Without Using SQL Enterprise Manager in SQL Server
2000
http://support.microsoft.com/?id=283811
-Sue
On Mon, 28 Jun 2004 03:48:15 -0700, "Phil"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>We have an automated process which imports a file from a
>remote server. Unfortunately this requires the
>MSSQLServer service to be running under a domain account
>in order to be able to access the remote server. I have
>been unable to get SQL Server to start with anything other
>than Domain Admin rights.
>Do you know what rights are required for the MSSQLServer
>service to run?
>Thanks,
>Phil.