Brackets appear in column name

I am using Enterprise Manager to create database tables. In the table design view I am trying to create a column called, section. After typing, section, Enterprise Manager automatically puts brackets around the name, ex. [section]. When I view the table by returning all rows the brackets are gone. However, when I go back to desing view the brackets are there. Why is this happening and what affect does it have on my database?

Thanks,

Matt

That is 'normal' and expected behavior when your table or column names contain spaces or other 'invalid' characters.

SQL Server, unlike Access you may have been using, does not allow the use of spaces in object (tables, columns, etc.) names. You will always have to use those 'pesky' square brackets when you write any SQL code specifying the improperly named items.

Other than the extra work always having to use the square brackets when writing code, there is no discernable impact on the database. The database assigns an 'ObjectID' to all tables, columns, etc., and internally, it uses the ObjectID.

|||

Arnie,

The column name I am trying to use is, section, with no spaces but Enterprise Manager is automatically putting the brackets on. Any ideas?

Thanks,

Matt

|||

I should have included that square brackets are also included around 'reserved words' when used as object names.

You may wish to examine the 'reserved word' list in Books Online, and then avoid using any reserved words in your object names.

As I indicated before, if EM adds the square brackets, you will also be required to also use square brackets (or double quotes) when referring to those improperly named objects.

|||

Arnie,

I found the word, section, in the Books Online. It is an ODBC reserved word. Thanks for the help,

Matt

|||

Matt,

If that information helped you solve your issue, please mark the post as helpful.

Thanks

Brackets appear in column name

I am using Enterprise Manager to create database tables. In the table design view I am trying to create a column called, section. After typing, section, Enterprise Manager automatically puts brackets around the name, ex. [section]. When I view the table by returning all rows the brackets are gone. However, when I go back to desing view the brackets are there. Why is this happening and what affect does it have on my database?

Thanks,

Matt

That is 'normal' and expected behavior when your table or column names contain spaces or other 'invalid' characters.

SQL Server, unlike Access you may have been using, does not allow the use of spaces in object (tables, columns, etc.) names. You will always have to use those 'pesky' square brackets when you write any SQL code specifying the improperly named items.

Other than the extra work always having to use the square brackets when writing code, there is no discernable impact on the database. The database assigns an 'ObjectID' to all tables, columns, etc., and internally, it uses the ObjectID.

|||

Arnie,

The column name I am trying to use is, section, with no spaces but Enterprise Manager is automatically putting the brackets on. Any ideas?

Thanks,

Matt

|||

I should have included that square brackets are also included around 'reserved words' when used as object names.

You may wish to examine the 'reserved word' list in Books Online, and then avoid using any reserved words in your object names.

As I indicated before, if EM adds the square brackets, you will also be required to also use square brackets (or double quotes) when referring to those improperly named objects.

|||

Arnie,

I found the word, section, in the Books Online. It is an ODBC reserved word. Thanks for the help,

Matt

|||

Matt,

If that information helped you solve your issue, please mark the post as helpful.

Thanks

BPA configuring 'Object Prefix'

I would like to configure the prefixes for several objects but I cannot figure out how to do so. From what I saw in the Properties section, it will only allow 1 property (I have already set up Stored Procedures) but I would like to do several (Stored Pro
cedure, Functions, Views, etc.) Can anyone point me in the right direction?
Thanks,
Jeff
Hi Jeff
Yes, you can only configure one rule per bet practice group. In order to
accommodate multiple checks, you'll have to create several separate Best
Practice Groups. We'll look into how to provide what you want in a single
best practice group in a future release.
- Christian
___________________________
Christian Kleinerman
Program Manager, SQL Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jeff Kararo" <JeffKararo@.discussions.microsoft.com> wrote in message
news:9A3FBB14-CC30-4691-B4A3-5E3BD29633B3@.microsoft.com...
> I would like to configure the prefixes for several objects but I cannot
figure out how to do so. From what I saw in the Properties section, it will
only allow 1 property (I have already set up Stored Procedures) but I would
like to do several (Stored Procedure, Functions, Views, etc.) Can anyone
point me in the right direction?
> Thanks,
> Jeff
>

boot.ini

I have a server with 8GB RAM. The boot.ini file's section
looks like this:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect
Presumably it should look like this:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /3GB /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect
My questions:
(1) with just /PAE presumably the OS can't access 4 of
the 8GB?
(2) what is the second multi(0)disk(0)rdisk(0)partition
(1) section for? Presumably I don't need to do anything
to it?
Many thanks in advance,
JonYour server is set up correctly. It is usually a good idea to have the
default configuration in the boot.ini just in case something goes wrong with
the modified one.
With /PAE you can address all the RAM, ensure you have run sp_configure 'awe
enabled', 1 to enable AWE in SQL Server. This configures SQL Server to use
a totally different set of Windows APIs to access memory.
I do not recommend using /3GB. This is required if you are not using AWE.
It also removes some memory resources from the OS. I have seen this cause
problems.
Hope this has helped.
Regards
Barry McAuslin
----
--
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:523701c4c8c7$2aa48a50$a401280a@.phx.gbl...
> I have a server with 8GB RAM. The boot.ini file's section
> looks like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect
> Presumably it should look like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /3GB /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect
> My questions:
> (1) with just /PAE presumably the OS can't access 4 of
> the 8GB?
> (2) what is the second multi(0)disk(0)rdisk(0)partition
> (1) section for? Presumably I don't need to do anything
> to it?
> Many thanks in advance,
> Jon
>|||Barry,
this is extremely helpful - thank you.
I now understand the /PAE bit, but the 2 entries in the
boot.ini file still escapes me. Is only the first one
used? Is the second one there so someone can replace the
first with the second in safe recovery and then reboot?
Or can the second one be used automatically?
Thanks,
Jon|||Jon
In the boot.ini file there is also an entry called timeout. If this is set
to 0 the first one in the list will be used straight away. However if the
time is say 10, you will get to choose which one you would like to boot
windows with. If you do not select an item, the first one will be used when
10 seconds is up.
I alway like to leave both entries there in case things go wrong with the
server and you want to turn /PAE off. You just select a different item from
the list.
You can also change which one is used from system properties (right click My
Computer, and select Properties). Select Startup and Recovery from the
Advanced tab.
Regards
Barry McAuslin
----
--
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
> Barry,
> this is extremely helpful - thank you.
> I now understand the /PAE bit, but the 2 entries in the
> boot.ini file still escapes me. Is only the first one
> used? Is the second one there so someone can replace the
> first with the second in safe recovery and then reboot?
> Or can the second one be used automatically?
> Thanks,
> Jon
>|||Barry - many thanks.
>--Original Message--
>Jon
>In the boot.ini file there is also an entry called
timeout. If this is set
>to 0 the first one in the list will be used straight
away. However if the
>time is say 10, you will get to choose which one you
would like to boot
>windows with. If you do not select an item, the first
one will be used when
>10 seconds is up.
>I alway like to leave both entries there in case things
go wrong with the
>server and you want to turn /PAE off. You just select a
different item from
>the list.
>You can also change which one is used from system
properties (right click My
>Computer, and select Properties). Select Startup and
Recovery from the
>Advanced tab.
>Regards
>Barry McAuslin
>----
--
>--
>Look inside your SQL Server files with SQL File Explorer.
>Go to http://www.sqlfe.com for more information.
>"Jon" <anonymous@.discussions.microsoft.com> wrote in
message
>news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
>> Barry,
>> this is extremely helpful - thank you.
>> I now understand the /PAE bit, but the 2 entries in the
>> boot.ini file still escapes me. Is only the first one
>> used? Is the second one there so someone can replace the
>> first with the second in safe recovery and then reboot?
>> Or can the second one be used automatically?
>> Thanks,
>> Jon
>
>.
>