32 bit vs. 64 bit

I'm running SQL Workgroup edition (32 bit) on a 64 bit OS. Would I see a performance gain from upgrading to SQL Standard 64 bit? Hardware is DL385 2 proc AMD 2.8 Ghz with 6 GB RAM. Has anyone made this comparison and how much gain did you see?

I am not sure the performance that can be obtained. But one thing is clear that upgrading 32-bit to 64-bit is not supported directly. If you really want to perform such an upgrading, you can do as follows.

Approach one.

1. Uninstall 32-bit and save database

2. Install 64-bit and attach the saved database

Approach two.

1. Install 64-bit side by side with 32-bit, which is supported.

2. Export 32-bit data to 64-bit.

3. Uninstall 32-bit.

Anyway, please backup your database before doing any major operation on your database.

32 bit vs. 64 bit

I'm running SQL Workgroup edition (32 bit) on a 64 bit OS. Would I see a performance gain from upgrading to SQL Standard 64 bit? Hardware is DL385 2 proc AMD 2.8 Ghz with 6 GB RAM. Has anyone made this comparison and how much gain did you see?

I am not sure the performance that can be obtained. But one thing is clear that upgrading 32-bit to 64-bit is not supported directly. If you really want to perform such an upgrading, you can do as follows.

Approach one.

1. Uninstall 32-bit and save database

2. Install 64-bit and attach the saved database

Approach two.

1. Install 64-bit side by side with 32-bit, which is supported.

2. Export 32-bit data to 64-bit.

3. Uninstall 32-bit.

Anyway, please backup your database before doing any major operation on your database.

2005 Workgroup - 'Create failed for jobstep' error creating backup

Hello,
I am running into an error when creating maintenence jobs in SQL Management
Studio. I can create the new jobs and specify all the options, but when I
attempt to save the job I receive the following error:
"Create failed for JobStep 'jobname'" or
"Create failed for Job 'jobname"
Here's my setup:
SQL 2005 Workgroup Edition SP1
Windows SBS 2003 SP1
I saw a Microsoft KB article, and several forums which confirm this, stating
that SQL Server 2005 Integration Services (SSIS) need to be installed for
maintenance jobs to be created successfully. However, and here's the catch
22, SSIS is not an available installation options in SQL Server 2005
Workgroup edition. So... how do I go about resolving this issue when the
recommended fix is not available for my version of SQL 2005?
Thanks for any help!Sorry, meant to include this in the original post... here is the MS KB
article I was referring to:
http://support.microsoft.com/kb/909036
"Epsil0n" wrote:
> Hello,
> I am running into an error when creating maintenence jobs in SQL Management
> Studio. I can create the new jobs and specify all the options, but when I
> attempt to save the job I receive the following error:
> "Create failed for JobStep 'jobname'" or
> "Create failed for Job 'jobname"
> Here's my setup:
> SQL 2005 Workgroup Edition SP1
> Windows SBS 2003 SP1
> I saw a Microsoft KB article, and several forums which confirm this, stating
> that SQL Server 2005 Integration Services (SSIS) need to be installed for
> maintenance jobs to be created successfully. However, and here's the catch
> 22, SSIS is not an available installation options in SQL Server 2005
> Workgroup edition. So... how do I go about resolving this issue when the
> recommended fix is not available for my version of SQL 2005?
> Thanks for any help!

2005 Maintenance Plan Best Practices?

Does anyone have a link to resources or suggestions on best practices for
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>|||On Aug 6, 1:13 pm, "ML" <schoo...@.accesswave.ca> wrote:
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want to
> make sure we cover off all the bases in setting up our maintenance plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a single
> daily plan sufficient or should we be setting up multiple plans to handle
> backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
There is this: http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspx|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?|||As you probably realize, there are not simple "one size fits all" answers to these question. Reading
up on the subject is what I recommend:
> For the database integrity check, is it best to run this before or after a full backup?
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/23/675963.aspx
And other articles on that blog.
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
>> Does anyone have a link to resources or suggestions on best practices for setting up proper
>> maintenance plans with SQL 2005 (Workgroup)?
>> We have a new 2005 database that we are preparing for production and want to make sure we cover
>> off all the bases in setting up our maintenance plan.
>> This will be for an online reservation system that will process approx 300-600 transactions per
>> day. The system needs to be live 24/7/365 or as near to this as possible.
>> The initial database is expected to be around 600MB is size with approx 40 tables and grow from
>> there with new transactions.
>> What we be a good plan for such a system for a starting point? Is a single daily plan sufficient
>> or should we be setting up multiple plans to handle backups, tuning, shrinking, etc separately?
>> Any suggestions/comments would be appreciated.
> Thank you for the comment so far. I think we will start off with daily full backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
>

2005 Maintenance Plan Best Practices?

Does anyone have a link to resources or suggestions on best practices for
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.
What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>
|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?
|||As you probably realize, there are not simple "one size fits all" answers to these question. Reading
up on the subject is what I recommend:

> For the database integrity check, is it best to run this before or after a full backup?
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/23/675963.aspx
And other articles on that blog.

> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Thank you for the comment so far. I think we will start off with daily full backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistics, etc) how often should
> these typically be run?
>

2005 Maintenance Plan Best Practices?

Does anyone have a link to resources or suggestions on best practices for
setting up proper maintenance plans with SQL 2005 (Workgroup)?
We have a new 2005 database that we are preparing for production and want to
make sure we cover off all the bases in setting up our maintenance plan.
This will be for an online reservation system that will process approx
300-600 transactions per day. The system needs to be live 24/7/365 or as
near to this as possible.
The initial database is expected to be around 600MB is size with approx 40
tables and grow from there with new transactions.
What we be a good plan for such a system for a starting point? Is a single
daily plan sufficient or should we be setting up multiple plans to handle
backups, tuning, shrinking, etc separately?
Any suggestions/comments would be appreciated.What ever you do don't shrink the database. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
How often you do backups are dependent on how much data you can afford to
loose. While this is for 2000 the principles still hold true.
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
Andrew J. Kelly SQL MVP
"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
>|||On Aug 6, 1:13 pm, "ML" <schoo...@.accesswave.ca> wrote:
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
to
> make sure we cover off all the bases in setting up our maintenance plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a singl
e
> daily plan sufficient or should we be setting up multiple plans to handle
> backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
There is this: http://www.microsoft.com/technet/pr...br />
ps4.mspx|||"ML" <schooner@.accesswave.ca> wrote in message
news:%23abfUZG2HHA.728@.TK2MSFTNGP05.phx.gbl...
> Does anyone have a link to resources or suggestions on best practices for
> setting up proper maintenance plans with SQL 2005 (Workgroup)?
> We have a new 2005 database that we are preparing for production and want
> to make sure we cover off all the bases in setting up our maintenance
> plan.
> This will be for an online reservation system that will process approx
> 300-600 transactions per day. The system needs to be live 24/7/365 or as
> near to this as possible.
> The initial database is expected to be around 600MB is size with approx 40
> tables and grow from there with new transactions.
> What we be a good plan for such a system for a starting point? Is a
> single daily plan sufficient or should we be setting up multiple plans to
> handle backups, tuning, shrinking, etc separately?
> Any suggestions/comments would be appreciated.
>
Thank you for the comment so far. I think we will start off with daily full
backups and transaction log backups every 15 mins.
For the database integrity check, is it best to run this before or after a
full backup?
In terms of the other maintenance tasks (rebuild indexes, update statistics,
etc) how often should these typically be run?|||As you probably realize, there are not simple "one size fits all" answers to
these question. Reading
up on the subject is what I recommend:

> For the database integrity check, is it best to run this before or after a full ba
ckup?
http://blogs.msdn.com/sqlserverstor.../23/675963.aspx
And other articles on that blog.

> In terms of the other maintenance tasks (rebuild indexes, update statistic
s, etc) how often should
> these typically be run?
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Above article hasn't been updated for 2005, but basic concepts still applies
.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"ML" <schooner@.accesswave.ca> wrote in message news:OabaWpN2HHA.1124@.TK2MSFTNGP06.phx.gbl...

> "ML" <schooner@.accesswave.ca> wrote in message news:%23abfUZG2HHA.728@.TK2M
SFTNGP05.phx.gbl...
> Thank you for the comment so far. I think we will start off with daily fu
ll backups and
> transaction log backups every 15 mins.
> For the database integrity check, is it best to run this before or after a
full backup?
> In terms of the other maintenance tasks (rebuild indexes, update statistic
s, etc) how often should
> these typically be run?
>