Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?Refer "Instance Name" under "instance names" in BOL
--
Thanks
Ravi
"Andy Gaskell" wrote:
> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose to
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. For
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know the
> specific rules for a naming a named instance? For example - how long can the
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:
>> Hi, I'm trying to wrap the MSDE command line installer with an
>> InstallShield setup. One of the requirements is that the user can choose
>> to
>> install a named instance and can choose the name of the named instance.
>> Here's what I found on SQL BOL:
>> "A new instance name must begin with a letter, an ampersand (&), or an
>> underscore (_), and can contain numbers, letters, or other characters.
>> SQL
>> Server sysnames and reserved names should not be used as instance names.
>> For
>> example, the term "default" should not be used as an instance name
>> because
>> it is a reserved name used by Setup."
>> That's a little vague for trying to write an installer. Does anyone know
>> the
>> specific rules for a naming a named instance? For example - how long can
>> the
>> name be? can there be spaces in the name? what exactly are "other
>> characters" - anything?
>>

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?Refer "Instance Name" under "instance names" in BOL
--
Thanks
Ravi
"Andy Gaskell" wrote:

> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose t
o
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. F
or
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know t
he
> specific rules for a naming a named instance? For example - how long can t
he
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...[vbcol=seagreen]
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:
>sql

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?
Refer "Instance Name" under "instance names" in BOL
Thanks
Ravi
"Andy Gaskell" wrote:

> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose to
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. For
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know the
> specific rules for a naming a named instance? For example - how long can the
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>
|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...[vbcol=seagreen]
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:

Name of database

I am currently installing SQL Server and need a name for my database. Is there a naming convention to follow.no there is not. but use whole meaningful words.|||The only naming convention I've seen, which works well in quite some cases, is having table names that are plural form of nouns, eg Customers, Contracts, Addresses etc.|||Use Cyrillic characters, and substitute the ascii value 160 for spaces. This will ensure long-term job security.|||if you use brackets, you can name each of your tables and columns a varying number of blank spaces. that makes for fun times.

select * from [ ] a join [ ] b on a.[ ]=b.[ ]

or, just read the bible: http://mindprod.com/jgloss/unmain.html|||Use Cyrillic characters, and substitute the ascii value 160 for spaces. This will ensure long-term job security.

Where do you work again...?

:D|||I have always been fond of the name Allison. If you have a female database, I heartily suggest Allison.

Sorry. Been a long day.|||Allison is OK, but "Brynn" makes my heart flutter. I'm sure all Brynns have brown eyes. I could fall in love with a database named Brynn.|||Allison is OK, but "Brynn" makes my heart flutter. I'm sure all Brynns have brown eyes. I could fall in love with a database named Brynn.

Wow :shocked: ... gettin' a little punchy on the forums, eh?

Regards,

hmscott|||Its Spring.
I can see it out the window across from my cubicle.|||I am currently installing SQL Server and need a name for my database. Is there a naming convention to follow.

Foobar ... I've always wanted to see a database named Foobar ... or Plugh ... or Y2 ... or Plover ... or XYZZY|||... or Plover ... or XYZZY

I actually remember that game. Does that make me old?

Regards,

hmscott|||Database? After installing SS you'll have 4 system databases: master, tempdb, model, and msdb.
Then you create new databases for the data you want to work with. Choose a logical, descriptive name. If its for payroll data, "Payroll" might be a good name.
Maybe you're talking about the Server and Instance names. I kept the default workstation name when I installed my OS (Win 2K). I also accepted the default instance name when I installed Sql Server with VS.Net. So now I have to type "HOME-76yvI250x/VSdotNet" to specify my server. I'd suggest something easier!|||We used to have a database called "Live" *sigh*|||I never knew database is feminine or musculine... LOL what do you mean Female database...|||It's just like cars.
All cars are female.
Mine is embarrasingly called Ethel :o|||How about applying the suffix "isthenameofthis[objecttype]" to each object?
Create database 'PayrollIsTheNameOfThisDatabase'
Create table PayrollDateIsTheNameOfThisTable
(PayrollIDIsTheNameOfThisIntegerColumn int,
PayrollAmountIsTheNameOfThisMoneyColumn money,
PayrollNoteIsTheNameOfThisVarchar500Column varchar(500))
That should drive the developers mad.|||Ah! Obsucatory naming conventions. This query has soul:


EXEC sp_addtype '[[[][[]]][]', 'varchar(24)', 'NOT NULL'
EXEC sp_addtype '[[[][[][]', 'Int'

DROP TABLE []][]]]

CREATE TABLE []][]]]
(
[]][] [[[[]][[]]]]]][]]],
[[[]][]][] [[[[]][[]][]]]
)

INSERT INTO []][]]]
(
[[[]][]][],
[]][]
)
SELECT 1, '[[]][]' UNION ALL
SELECT 2, '[[]][]]]' UNION ALL
SELECT 3, '[[]][[[[]' UNION ALL
SELECT 4, '[[]][[]]' UNION ALL
SELECT 5, '[[[]][]][[]' UNION ALL
SELECT 6, '][[[]]]][]' UNION ALL
SELECT 7, '[[]][][' UNION ALL
SELECT 8, '][]]][]'

SELECT []]].[]][],
MAX([]][].[[[]][]][]) AS [[[[]][]
FROM []][]]] []]]
INNER JOIN []][]]] []][] ON
[]]].[]][] >= []][].[]][]
GROUP BY
[]]].[]][]|||pootle, you get a gold star for that one. It's beautiful!

there ought to be a sql version of this site, it's one of my favorites: http://www.ioccc.org

:)|||How about applying the suffix "isthenameofthis[objecttype]" to each object?
Create database 'PayrollIsTheNameOfThisDatabase'
Create table PayrollDateIsTheNameOfThisTable
(PayrollIDIsTheNameOfThisIntegerColumn int,
PayrollAmountIsTheNameOfThisMoneyColumn money,
PayrollNoteIsTheNameOfThisVarchar500Column varchar(500))
That should drive the developers mad.

You forgot to prefix the objects with tbl, etc. it should be:

tblPayrollDateIsTheNameOfThisTable,
colPayrollNoteIsTheNameOfThisVarchar500Column|||I actually remember that game. Does that make me old?

Regards,

hmscott

How about playing that game on the mainframe?|||How about playing that game on the mainframe?

Nope. Just an IBM 8086 with no hard drive and about 32KB (?) of memory.

I'm not that old. :D

Regards,

hmscott|||http://www.rickadams.org/adventure/