Add Datafile

I have a need to add a secondary datafile. My question pertains to the
FIlegroups tab in Enterprise Manager. Do I need to change the value of the
Primary Filegroup 'Files' from 1 to 2? From researching, I believe that a
database can only have one primary file.
Hi
I prefer to do such things by QA not by EM
CREATE DATABASE databasename
GO
ALTER DATABASE databasename SET RECOVERY FULL
ALTER DATABASE databasename ADD FILEGROUP new_customers
ALTER DATABASE databasename ADD FILEGROUP sales
GO
ALTER DATABASE databasenameADD FILE
(NAME=databasename_data_1',
FILENAME='d:\mw.dat1')
TO FILEGROUP new_customers
ALTER DATABASE databasename
ADD FILE
(NAME='databasename_data_2',
FILENAME='d:\mw.dat2')
TO FILEGROUP sales
"paldba" <paldba@.discussions.microsoft.com> wrote in message
news:560E20AD-0955-44A6-95AF-6C853151F478@.microsoft.com...
>I have a need to add a secondary datafile. My question pertains to the
> FIlegroups tab in Enterprise Manager. Do I need to change the value of
> the
> Primary Filegroup 'Files' from 1 to 2? From researching, I believe that a
> database can only have one primary file.

Add Datafile

I have a need to add a secondary datafile. My question pertains to the
FIlegroups tab in Enterprise Manager. Do I need to change the value of the
Primary Filegroup 'Files' from 1 to 2? From researching, I believe that a
database can only have one primary file.Hi
I prefer to do such things by QA not by EM
CREATE DATABASE databasename
GO
ALTER DATABASE databasename SET RECOVERY FULL
ALTER DATABASE databasename ADD FILEGROUP new_customers
ALTER DATABASE databasename ADD FILEGROUP sales
GO
ALTER DATABASE databasenameADD FILE
(NAME=databasename_data_1',
FILENAME='d:\mw.dat1')
TO FILEGROUP new_customers
ALTER DATABASE databasename
ADD FILE
(NAME='databasename_data_2',
FILENAME='d:\mw.dat2')
TO FILEGROUP sales
"paldba" <paldba@.discussions.microsoft.com> wrote in message
news:560E20AD-0955-44A6-95AF-6C853151F478@.microsoft.com...
>I have a need to add a secondary datafile. My question pertains to the
> FIlegroups tab in Enterprise Manager. Do I need to change the value of
> the
> Primary Filegroup 'Files' from 1 to 2? From researching, I believe that a
> database can only have one primary file.

Add Datafile

I have a need to add a secondary datafile. My question pertains to the
FIlegroups tab in Enterprise Manager. Do I need to change the value of the
Primary Filegroup 'Files' from 1 to 2? From researching, I believe that a
database can only have one primary file.Hi
I prefer to do such things by QA not by EM
CREATE DATABASE databasename
GO
ALTER DATABASE databasename SET RECOVERY FULL
ALTER DATABASE databasename ADD FILEGROUP new_customers
ALTER DATABASE databasename ADD FILEGROUP sales
GO
ALTER DATABASE databasenameADD FILE
(NAME=databasename_data_1',
FILENAME='d:\mw.dat1')
TO FILEGROUP new_customers
ALTER DATABASE databasename
ADD FILE
(NAME='databasename_data_2',
FILENAME='d:\mw.dat2')
TO FILEGROUP sales
"paldba" <paldba@.discussions.microsoft.com> wrote in message
news:560E20AD-0955-44A6-95AF-6C853151F478@.microsoft.com...
>I have a need to add a secondary datafile. My question pertains to the
> FIlegroups tab in Enterprise Manager. Do I need to change the value of
> the
> Primary Filegroup 'Files' from 1 to 2? From researching, I believe that a
> database can only have one primary file.

AD migration and SQL server logins.

Our SQL 2000 servers use Windows authentication. My question pertains to th
e
effect an AD migration has on SQL logins.
After the NT4 user accounts and groups are migrated to the AD domain and the
SQL server is upgraded to the AD domain, do the SQL logins automatically
reference the new user accounts in AD? If not do I have to manually add the
AD users and groups to SQL login and access to the databases? Or are there
tools available?You should not have to manually add the account again to SQL Server if your
network administrator choose to migrate the accounts with sid history. If
the accounts do not use sid history then you will need to add the accounts
back into SQL Server. I beleive one of the stored procedures you could use
is sp_sidmap.
"anthonyp" wrote:

> Our SQL 2000 servers use Windows authentication. My question pertains to
the
> effect an AD migration has on SQL logins.
> After the NT4 user accounts and groups are migrated to the AD domain and t
he
> SQL server is upgraded to the AD domain, do the SQL logins automatically
> reference the new user accounts in AD? If not do I have to manually add t
he
> AD users and groups to SQL login and access to the databases? Or are ther
e
> tools available?