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.

MSXML parser & SQL Server Memory

The below snippet from SQL Server BOL under the topic "sp_xml_preparedocument" implies that the use of XML can be extremely memory intensive. Is is really the case that MSXML uses 1/8 total SQL Server memory? I find this astounding if true.
"Note A parsed document is stored in the internal cache of SQL Server 2000. The MSXML parser uses one-eighth the total memory available for SQL Server. To avoid running out of memory, run sp_xml_removedocument to free up the memory."
It means that it can use up to 1/8th of the memory. Unless you try to parse
a very large document or never release the allocated memory, you should
never use or reach this limit.
HTH
Michael
"glr" <glr@.discussions.microsoft.com> wrote in message
news:DE9CFF6C-B949-4318-9294-6B4EFB773AF2@.microsoft.com...
> The below snippet from SQL Server BOL under the topic
> "sp_xml_preparedocument" implies that the use of XML can be extremely
> memory intensive. Is is really the case that MSXML uses 1/8 total SQL
> Server memory? I find this astounding if true.
> "Note A parsed document is stored in the internal cache of SQL Server
> 2000. The MSXML parser uses one-eighth the total memory available for SQL
> Server. To avoid running out of memory, run sp_xml_removedocument to free
> up the memory."
>