8114 error w/db maintenance plan

Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.
I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:

>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.

8114 error w/db maintenance plan

Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.

8114 error w/db maintenance plan

Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the followin
g
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 420
00]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:

>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the followi
ng
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42
000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. An
y
>advice? Thanks.

64 bit vs 32 bit with same RAM.

If I’m setting up a server, and I don’t plan on putting a lot of RAM(4GB
maybe 8GB) in it, will 64bit still be better?
thanks
If I'm to make a choice in the specific situation that you described and my
databases have always been on the 32-bit platform, I would most likely just
leave them on 32-bit until I run tests to determine if there is any benefits
going to 64 bit at all.
But there is always this issue of 'scaling forward' to take advantage of
what's coming in computing, and 64-bit generally speaking would put you in a
better position to scale forward. Of course, for your particular app, scaling
forward may or may not be relevant.
Now, note that 64-bit does carry some overhead in terms of larger data
structures and so on. Not all workloads will automatically benefit
performance wise from moving to 64-bit. For instance, if the data set of your
workloads can fit largely in memory, you may find 32-bit faster than 64-bit.
Linchi
"Jason" wrote:

> If I’m setting up a server, and I don’t plan on putting a lot of RAM(4GB
> maybe 8GB) in it, will 64bit still be better?
> thanks

64 bit vs 32 bit with same RAM.

If Iâ'm setting up a server, and I donâ't plan on putting a lot of RAM(4GB
maybe 8GB) in it, will 64bit still be better?
thanksIf I'm to make a choice in the specific situation that you described and my
databases have always been on the 32-bit platform, I would most likely just
leave them on 32-bit until I run tests to determine if there is any benefits
going to 64 bit at all.
But there is always this issue of 'scaling forward' to take advantage of
what's coming in computing, and 64-bit generally speaking would put you in a
better position to scale forward. Of course, for your particular app, scaling
forward may or may not be relevant.
Now, note that 64-bit does carry some overhead in terms of larger data
structures and so on. Not all workloads will automatically benefit
performance wise from moving to 64-bit. For instance, if the data set of your
workloads can fit largely in memory, you may find 32-bit faster than 64-bit.
Linchi
"Jason" wrote:
> If Iâ'm setting up a server, and I donâ't plan on putting a lot of RAM(4GB
> maybe 8GB) in it, will 64bit still be better?
> thanks

5 Day Backup Maintenance Plan Help?

I am just getting used to SQL 2005 coming from SQL 2000 and can't figure
something out. In SQL 2000 I can go into the wizard and create a maintenance
plan to do a backup every night keeping 5 day's worth of (.bak) backup files,
each file having it's own naming convention using the date and time stamp as
part of the file name. Can't be any simpler. From there I backup each of
the .bak files to a tape.
When I go into the maintenance planner in the new SQL 2005 manager I can
create a backup plan but I can't seem to get it to create the same type of
thing. All it wants to do is overwrite the previous nights file, thus I only
have 1 file (most recent date) in my backup directory. What am I doing
wrong? Is there a simple Q article talking about this?
Thanks!
-Richard K
In the backup databases task you need to check the option for "Create a
Backup file for every database"
Andrew J. Kelly SQL MVP
"Richard K" <RichardK@.discussions.microsoft.com> wrote in message
news:F62187FE-7677-4408-8062-047B40D5EFC9@.microsoft.com...
>I am just getting used to SQL 2005 coming from SQL 2000 and can't figure
> something out. In SQL 2000 I can go into the wizard and create a
> maintenance
> plan to do a backup every night keeping 5 day's worth of (.bak) backup
> files,
> each file having it's own naming convention using the date and time stamp
> as
> part of the file name. Can't be any simpler. From there I backup each of
> the .bak files to a tape.
> When I go into the maintenance planner in the new SQL 2005 manager I can
> create a backup plan but I can't seem to get it to create the same type of
> thing. All it wants to do is overwrite the previous nights file, thus I
> only
> have 1 file (most recent date) in my backup directory. What am I doing
> wrong? Is there a simple Q article talking about this?
> Thanks!
> -Richard K
>
|||OK, got that part but no where in the wizard can I specify that I want to
hold 5 days worth of backups. That's what is confusing. Other than that I
like the new SQL Server Management Studio. I just have to get used to it.
"Andrew J. Kelly" wrote:

> In the backup databases task you need to check the option for "Create a
> Backup file for every database"
> --
> Andrew J. Kelly SQL MVP
> "Richard K" <RichardK@.discussions.microsoft.com> wrote in message
> news:F62187FE-7677-4408-8062-047B40D5EFC9@.microsoft.com...
>
>
|||Richard,
Pre SP2 you have to Modify the maintenance plan to add the Maintenance
Cleanup Task which will only delete down to Days.
SP2 CTP includes this Maintenance Cleanup Task in the wizard and allows the
delete to be in Hours.
Chris
"Richard K" <RichardK@.discussions.microsoft.com> wrote in message
news:2264AE56-C465-4DDD-8FE6-546D2C14C30F@.microsoft.com...[vbcol=seagreen]
> OK, got that part but no where in the wizard can I specify that I want to
> hold 5 days worth of backups. That's what is confusing. Other than that
> I
> like the new SQL Server Management Studio. I just have to get used to it.
> "Andrew J. Kelly" wrote:
|||OK, got it. I needed to add in a "cleanup task" to my routine. Very similar
to DTS package setup so very cool and flexible.
Thanks for the help Chris!!!
-Richard
"Chris Wood" wrote:

> Richard,
> Pre SP2 you have to Modify the maintenance plan to add the Maintenance
> Cleanup Task which will only delete down to Days.
> SP2 CTP includes this Maintenance Cleanup Task in the wizard and allows the
> delete to be in Hours.
> Chris
> "Richard K" <RichardK@.discussions.microsoft.com> wrote in message
> news:2264AE56-C465-4DDD-8FE6-546D2C14C30F@.microsoft.com...
>
>