New SQL Server 2005 Installation

I have just purchased SQL Server 2005 and a new Dell 2800 server to run it on. I was told by my Dell rep to configure the server with the following drives. 2 - 36GB drives in a RAID 0 (15,000 RPM), 2 - 73GB drives in a RAID 0 (10,000 RPM) and 3 - 146GB drives in a RAID 5 (10,000 RPM). Dell pre-installed the OS on the 36GB drive. I was told to install SQL on the 73GB drives and the data (primarily TIFF images) on the 146GB. The server is a 64bit machine with Windows 2003 Server and 4GB of RAM. I was told to put the transaction logs on a different physical drive that the database to speed the writes. Is this a correct installation? Is there any information on a best practice installation? I have spent about 6 hours on MS and Google trying to find an answer. Thanks for any help you can give. Recap of Dell recommendation:

2 - 36GB Mirrored Drives = OS

2 - 73BG Mirrored Drives = SQL Server 2005

3 - 146GB RAID 5 Drives = Data (Images)

Is this correct?

Where should the Transaction Logs Be?

Because transaction logging is a mostly write operation the most efficient place for them is on a mirrored drive set. I usually install SQL Server executables on the same drive as the operating system. (The network admins here configure 10GB for the OS and SQL Server, and it's always been plenty.) I place the data files on the RAID array, and the transaction logs on the mirrored set. When you're running setup specify the RAID drive for the data and the 36GB mirror set for the program files, then after installation set your default location for the log files to the 73GB mirror set and you should be all set.

New Server

I have a win2000 server that is in need of replacement, we
have built a new server and now need to configure sql 2000.
From backups I retored all the databases including msdb.
How do I restore the Master database, as this has lots of
extra system SP that need on the new server.
I tried putting the Instance in single user mode and doing
a restore, which said it worked OK but when trying to
restart SQL it fail to start. Any ideas what I am doing
wrongWhat's the error in the SQL Server error log?
See if this helps too: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
I have a win2000 server that is in need of replacement, we
have built a new server and now need to configure sql 2000.
From backups I retored all the databases including msdb.
How do I restore the Master database, as this has lots of
extra system SP that need on the new server.
I tried putting the Instance in single user mode and doing
a restore, which said it worked OK but when trying to
restart SQL it fail to start. Any ideas what I am doing
wrong|||What was the reason to backup/restore the system DB instead of generating
the script for the SPs (extra system SP)
and running the script on the new server ?
If they are system SPs they should be common across all master DBs, right ?
Gopi
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
>I have a win2000 server that is in need of replacement, we
> have built a new server and now need to configure sql 2000.
> From backups I retored all the databases including msdb.
> How do I restore the Master database, as this has lots of
> extra system SP that need on the new server.
> I tried putting the Instance in single user mode and doing
> a restore, which said it worked OK but when trying to
> restart SQL it fail to start. Any ideas what I am doing
> wrong
>|||Allan
From my experience i have learned that first of all script out all logins
(there are two SP provided by MS) and then jobs as well
There is no need to restore master,msdb databases , instead restore all user
databases and run the script generated by these SP's.
In the same way you can move all DTS packages (to save the as files). You
will not lost anything.
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
> I have a win2000 server that is in need of replacement, we
> have built a new server and now need to configure sql 2000.
> From backups I retored all the databases including msdb.
> How do I restore the Master database, as this has lots of
> extra system SP that need on the new server.
> I tried putting the Instance in single user mode and doing
> a restore, which said it worked OK but when trying to
> restart SQL it fail to start. Any ideas what I am doing
> wrong
>

New Server

I have a win2000 server that is in need of replacement, we
have built a new server and now need to configure sql 2000.
From backups I retored all the databases including msdb.
How do I restore the Master database, as this has lots of
extra system SP that need on the new server.
I tried putting the Instance in single user mode and doing
a restore, which said it worked OK but when trying to
restart SQL it fail to start. Any ideas what I am doing
wrong
What's the error in the SQL Server error log?
See if this helps too: http://vyaskn.tripod.com/moving_sql_server.htm
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
I have a win2000 server that is in need of replacement, we
have built a new server and now need to configure sql 2000.
From backups I retored all the databases including msdb.
How do I restore the Master database, as this has lots of
extra system SP that need on the new server.
I tried putting the Instance in single user mode and doing
a restore, which said it worked OK but when trying to
restart SQL it fail to start. Any ideas what I am doing
wrong
|||What was the reason to backup/restore the system DB instead of generating
the script for the SPs (extra system SP)
and running the script on the new server ?
If they are system SPs they should be common across all master DBs, right ?
Gopi
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
>I have a win2000 server that is in need of replacement, we
> have built a new server and now need to configure sql 2000.
> From backups I retored all the databases including msdb.
> How do I restore the Master database, as this has lots of
> extra system SP that need on the new server.
> I tried putting the Instance in single user mode and doing
> a restore, which said it worked OK but when trying to
> restart SQL it fail to start. Any ideas what I am doing
> wrong
>
|||Allan
From my experience i have learned that first of all script out all logins
(there are two SP provided by MS) and then jobs as well
There is no need to restore master,msdb databases , instead restore all user
databases and run the script generated by these SP's.
In the same way you can move all DTS packages (to save the as files). You
will not lost anything.
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
> I have a win2000 server that is in need of replacement, we
> have built a new server and now need to configure sql 2000.
> From backups I retored all the databases including msdb.
> How do I restore the Master database, as this has lots of
> extra system SP that need on the new server.
> I tried putting the Instance in single user mode and doing
> a restore, which said it worked OK but when trying to
> restart SQL it fail to start. Any ideas what I am doing
> wrong
>

New Server

I have a win2000 server that is in need of replacement, we
have built a new server and now need to configure sql 2000.
From backups I retored all the databases including msdb.
How do I restore the Master database, as this has lots of
extra system SP that need on the new server.
I tried putting the Instance in single user mode and doing
a restore, which said it worked OK but when trying to
restart SQL it fail to start. Any ideas what I am doing
wrongWhat's the error in the SQL Server error log?
See if this helps too: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
I have a win2000 server that is in need of replacement, we
have built a new server and now need to configure sql 2000.
From backups I retored all the databases including msdb.
How do I restore the Master database, as this has lots of
extra system SP that need on the new server.
I tried putting the Instance in single user mode and doing
a restore, which said it worked OK but when trying to
restart SQL it fail to start. Any ideas what I am doing
wrong|||What was the reason to backup/restore the system DB instead of generating
the script for the SPs (extra system SP)
and running the script on the new server ?
If they are system SPs they should be common across all master DBs, right ?
Gopi
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
>I have a win2000 server that is in need of replacement, we
> have built a new server and now need to configure sql 2000.
> From backups I retored all the databases including msdb.
> How do I restore the Master database, as this has lots of
> extra system SP that need on the new server.
> I tried putting the Instance in single user mode and doing
> a restore, which said it worked OK but when trying to
> restart SQL it fail to start. Any ideas what I am doing
> wrong
>|||Allan
From my experience i have learned that first of all script out all logins
(there are two SP provided by MS) and then jobs as well
There is no need to restore master,msdb databases , instead restore all user
databases and run the script generated by these SP's.
In the same way you can move all DTS packages (to save the as files). You
will not lost anything.
"Allan" <asql@.penstonall.co.uk> wrote in message
news:714601c52622$882fe170$a601280a@.phx.gbl...
> I have a win2000 server that is in need of replacement, we
> have built a new server and now need to configure sql 2000.
> From backups I retored all the databases including msdb.
> How do I restore the Master database, as this has lots of
> extra system SP that need on the new server.
> I tried putting the Instance in single user mode and doing
> a restore, which said it worked OK but when trying to
> restart SQL it fail to start. Any ideas what I am doing
> wrong
>

New Guy Question: Which came first ... the chicken or the checkpoint file?

Hello all...here's a question from a newbie ...

I'm attempting to configure my SSIS package to use a checkpoint file. I've checked the docs, and I believe I've set all the package properties for this ... except they are looking for the name of the checkpoint file. I've tried a couple of experiments such as c:\myCheckpoint.txt and c:\myCheckpoint.xml ... just for grins ... to see if SSIS would generate a checkpoint file for me at the start of the package ... no luck:

Message: Checkpoint file "C:\myCheckpoint.xml" failed to open due to error
0x80070002 "The system cannot find the file specified.".

From these runtime errors I've seen, it appears the checkpoint file should be an XML file that is created w/ specific nodes, etc. My question is ... how do I create the checkpoint file in advance so that when the package is executed it will find it and run?

SSIS ... pretty cool stuff!

Thanks!This is controlled by Package.CheckpointUsage property.
You probably have it set to 'Always' which causes package
to require the checkpoint file. You need to set it to 'IfExists' -
then the checkpoint file will be used if it exists.|||Yeah, that's what I figured too. The property options are Always, IfExists and Never. The doc doesn't specify that a file is created for you if you use Always, and on practical experimentation this didn't seem to help. Perhaps there's another property I missed; I did try to follow all the Package property settings that appeared to relate to checkpoints.

Thank you very much for trying!

DB|||The checkpoint is created automatically when the package fails (if it is configured to use checkpoints).

When you set CheckpointUsage=Always, you tell package that it has to start from previously saved checkpoint, i.e. the checkpoint file is expected to exist.

If you don't have checkpoint file yet, set CheckpointUsage=IfExists and run the package. It will run fine, and if it fails the package will create a checkpoint file. Next time when you run this package it will use that checkpoint.|||Thank you very, very much for your help! That makes sense!

Doug|||

Being another newbe, this post has been exceedingly helpful - I ran into the same issue!

Thanks! :-)

New Guy Question: Which came first ... the chicken or the checkpoint file?

Hello all...here's a question from a newbie ...

I'm attempting to configure my SSIS package to use a checkpoint file. I've checked the docs, and I believe I've set all the package properties for this ... except they are looking for the name of the checkpoint file. I've tried a couple of experiments such as c:\myCheckpoint.txt and c:\myCheckpoint.xml ... just for grins ... to see if SSIS would generate a checkpoint file for me at the start of the package ... no luck:

Message: Checkpoint file "C:\myCheckpoint.xml" failed to open due to error
0x80070002 "The system cannot find the file specified.".

From these runtime errors I've seen, it appears the checkpoint file should be an XML file that is created w/ specific nodes, etc. My question is ... how do I create the checkpoint file in advance so that when the package is executed it will find it and run?

SSIS ... pretty cool stuff!

Thanks!This is controlled by Package.CheckpointUsage property.
You probably have it set to 'Always' which causes package
to require the checkpoint file. You need to set it to 'IfExists' -
then the checkpoint file will be used if it exists.|||Yeah, that's what I figured too. The property options are Always, IfExists and Never. The doc doesn't specify that a file is created for you if you use Always, and on practical experimentation this didn't seem to help. Perhaps there's another property I missed; I did try to follow all the Package property settings that appeared to relate to checkpoints.

Thank you very much for trying!

DB|||The checkpoint is created automatically when the package fails (if it is configured to use checkpoints).

When you set CheckpointUsage=Always, you tell package that it has to start from previously saved checkpoint, i.e. the checkpoint file is expected to exist.

If you don't have checkpoint file yet, set CheckpointUsage=IfExists and run the package. It will run fine, and if it fails the package will create a checkpoint file. Next time when you run this package it will use that checkpoint.|||Thank you very, very much for your help! That makes sense!

Doug|||

Being another newbe, this post has been exceedingly helpful - I ran into the same issue!

Thanks! :-)