Bad un-install of SQL Server 2005 Tools Express Edition CTP

I have used the tool at this URL

http://msdn.microsoft.com/vstudio/express/support/uninstall/#Tool

and *cannot* get SQL Server 2005 Tools Express Edition CTP to uninstall. I get the following dialog box:

"The setup has encountered an unexpected error in datastore. The action is Write_CommitFlag. The error is:Unable to write property into cache flagCommit Unable to write property into cache: "flagCommit" XmlRW Error: Failure loading xmlrw.dll CheckAllProcedures() returned 2."

Any ideas as to how I can work around this ?

Just dug this out of forums, and I believe it fixed my issues. Reposting for everyone's benefit.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130776&SiteID=1

|||

1.Run 'SQL Server 2005 Tools Express Edition' setup with -x from command prompt this will extract all setup files into a folder.

2. search a help file in that folder and go to ‘command line ‘ help topic, you can run that command(s) from command prompt.

sql

Bad Installation But Cannot Uninstall Reporting Services - Need He

I seem to have had a problem regarding my installation of SQL Server 2005 -
Developer Edition on my Windows XP Pro machine. I have tried to uninstall
either Reporting Services or all of SQL Server. However, it keeps getting
stuck in the Uninstall of Reporting Services and then does a rollback.
The error that I am getting in each case is as follows:
Setup failed to read IISMEMMAP TABLE. The Errorcode is -2147024893.
Does anyone know how to get out of this so I can try to fix the installation?
Thanks for any advice.
--
John GallagherHi John,
You may try using the tools below to remove SQL Server 2005 manually
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301/en-us
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Backward compatiblity in sqlserver 05 Enterprise edition

Hi,
I believe I'm running into a backward compatibility issue with the sqlserver
05 Enterprise edition. I restored a database from sqlserver 2000 to my new
sqlserver 2005. Both of my .net project and Access gets time-out errors
(running remotely) when they try to access to a table that I have modified
via query analyzer in sqlserver 2005. I had no problem reading the table via
those clients before I touched its data, so it looks like modifying data in
those table creating an incompatiblity issue.
Has anybody run into similar situation before? Thank you very much in
advance for your help!Never mind. I had a transaction failed to commit or rollback because of a
fatal error and so my subsequence data modification statements would just
lock up the tables.
"Zen" <zen@.nononospam.com> wrote in message
news:eKrY0y3fGHA.5092@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I believe I'm running into a backward compatibility issue with the
> sqlserver 05 Enterprise edition. I restored a database from sqlserver 2000
> to my new sqlserver 2005. Both of my .net project and Access gets
> time-out errors (running remotely) when they try to access to a table that
> I have modified via query analyzer in sqlserver 2005. I had no problem
> reading the table via those clients before I touched its data, so it looks
> like modifying data in those table creating an incompatiblity issue.
> Has anybody run into similar situation before? Thank you very much in
> advance for your help!
>

Backward compatiblity in sqlserver 05 Enterprise edition

Hi,
I believe I'm running into a backward compatibility issue with the sqlserver
05 Enterprise edition. I restored a database from sqlserver 2000 to my new
sqlserver 2005. Both of my .net project and Access gets time-out errors
(running remotely) when they try to access to a table that I have modified
via query analyzer in sqlserver 2005. I had no problem reading the table via
those clients before I touched its data, so it looks like modifying data in
those table creating an incompatiblity issue.
Has anybody run into similar situation before? Thank you very much in
advance for your help!Never mind. I had a transaction failed to commit or rollback because of a
fatal error and so my subsequence data modification statements would just
lock up the tables.
"Zen" <zen@.nononospam.com> wrote in message
news:eKrY0y3fGHA.5092@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I believe I'm running into a backward compatibility issue with the
> sqlserver 05 Enterprise edition. I restored a database from sqlserver 2000
> to my new sqlserver 2005. Both of my .net project and Access gets
> time-out errors (running remotely) when they try to access to a table that
> I have modified via query analyzer in sqlserver 2005. I had no problem
> reading the table via those clients before I touched its data, so it looks
> like modifying data in those table creating an incompatiblity issue.
> Has anybody run into similar situation before? Thank you very much in
> advance for your help!
>

Backups...daily

Hi,
When using the default backup tool and scheduling them nightly that come
with SQL 2000 Standard Edition are we getting good backups on a daily basis?
Meaning usable data for a restore in the event of disaster, I was told by
an associate that we are getting worthless backups without Backupexe.
Also, I know that we have other solutions by backing up the log files
assuming that the database is not set to "Simple". Suggestions?
Thanks!
Hi,
SQL Server Standard backup is allways safe. So do not worry. If it is a
production database you could set the recovery model to "FULL"
and do a Transaction log backup every 30 minutes. Every night you could do a
Differential or FULL database backup.
Transaction log backup with FULL recovery model will allow you to recover
the database fully in the eve of a crash as well
as you could do a POINT_IN_TIME recovery.
SEE THE BELOW SITE FOR BACKUP AND RECOVERY STRATEGY:-
http://www1.us.dell.com/content/topi...555&l=en&s=biz
Thanks
Hari
SQL Server MVP
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When using the default backup tool and scheduling them nightly that come
> with SQL 2000 Standard Edition are we getting good backups on a daily
> basis? Meaning usable data for a restore in the event of disaster, I was
> told by an associate that we are getting worthless backups without
> Backupexe.
> Also, I know that we have other solutions by backing up the log files
> assuming that the database is not set to "Simple". Suggestions?
> Thanks!
>
|||Thank you!
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eEg2wG0gFHA.2880@.TK2MSFTNGP09.phx.gbl...
> Hi,
> SQL Server Standard backup is allways safe. So do not worry. If it is a
> production database you could set the recovery model to "FULL"
> and do a Transaction log backup every 30 minutes. Every night you could do
> a Differential or FULL database backup.
> Transaction log backup with FULL recovery model will allow you to recover
> the database fully in the eve of a crash as well
> as you could do a POINT_IN_TIME recovery.
> SEE THE BELOW SITE FOR BACKUP AND RECOVERY STRATEGY:-
> http://www1.us.dell.com/content/topi...555&l=en&s=biz
>
> Thanks
> Hari
> SQL Server MVP
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>
|||Are you backing up to the same drive that youre db is on? If so, yes it is
worthless.
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When using the default backup tool and scheduling them nightly that come
> with SQL 2000 Standard Edition are we getting good backups on a daily
> basis? Meaning usable data for a restore in the event of disaster, I was
> told by an associate that we are getting worthless backups without
> Backupexe.
> Also, I know that we have other solutions by backing up the log files
> assuming that the database is not set to "Simple". Suggestions?
> Thanks!
>
|||You say it's worthless because of the obvious hard drive failures or some
other reason?
"ChrisR" <noemail@.bla.com> wrote in message
news:e9V9AN0gFHA.1468@.TK2MSFTNGP14.phx.gbl...
> Are you backing up to the same drive that youre db is on? If so, yes it is
> worthless.
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>
|||The obvious hard drive failures.
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uBrFAl0gFHA.2904@.tk2msftngp13.phx.gbl...
> You say it's worthless because of the obvious hard drive failures or some
> other reason?
> "ChrisR" <noemail@.bla.com> wrote in message
> news:e9V9AN0gFHA.1468@.TK2MSFTNGP14.phx.gbl...
>

Backups...daily

Hi,
When using the default backup tool and scheduling them nightly that come
with SQL 2000 Standard Edition are we getting good backups on a daily basis?
Meaning usable data for a restore in the event of disaster, I was told by
an associate that we are getting worthless backups without Backupexe.
Also, I know that we have other solutions by backing up the log files
assuming that the database is not set to "Simple". Suggestions?
Thanks!Hi,
SQL Server Standard backup is allways safe. So do not worry. If it is a
production database you could set the recovery model to "FULL"
and do a Transaction log backup every 30 minutes. Every night you could do a
Differential or FULL database backup.
Transaction log backup with FULL recovery model will allow you to recover
the database fully in the eve of a crash as well
as you could do a POINT_IN_TIME recovery.
SEE THE BELOW SITE FOR BACKUP AND RECOVERY STRATEGY:-
http://www1.us.dell.com/content/topics/global.aspx/power/en/ps4q00_martin?c=us&cs=555&l=en&s=biz
Thanks
Hari
SQL Server MVP
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When using the default backup tool and scheduling them nightly that come
> with SQL 2000 Standard Edition are we getting good backups on a daily
> basis? Meaning usable data for a restore in the event of disaster, I was
> told by an associate that we are getting worthless backups without
> Backupexe.
> Also, I know that we have other solutions by backing up the log files
> assuming that the database is not set to "Simple". Suggestions?
> Thanks!
>|||Thank you!
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eEg2wG0gFHA.2880@.TK2MSFTNGP09.phx.gbl...
> Hi,
> SQL Server Standard backup is allways safe. So do not worry. If it is a
> production database you could set the recovery model to "FULL"
> and do a Transaction log backup every 30 minutes. Every night you could do
> a Differential or FULL database backup.
> Transaction log backup with FULL recovery model will allow you to recover
> the database fully in the eve of a crash as well
> as you could do a POINT_IN_TIME recovery.
> SEE THE BELOW SITE FOR BACKUP AND RECOVERY STRATEGY:-
> http://www1.us.dell.com/content/topics/global.aspx/power/en/ps4q00_martin?c=us&cs=555&l=en&s=biz
>
> Thanks
> Hari
> SQL Server MVP
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> When using the default backup tool and scheduling them nightly that come
>> with SQL 2000 Standard Edition are we getting good backups on a daily
>> basis? Meaning usable data for a restore in the event of disaster, I was
>> told by an associate that we are getting worthless backups without
>> Backupexe.
>> Also, I know that we have other solutions by backing up the log files
>> assuming that the database is not set to "Simple". Suggestions?
>> Thanks!
>|||Are you backing up to the same drive that youre db is on? If so, yes it is
worthless.
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When using the default backup tool and scheduling them nightly that come
> with SQL 2000 Standard Edition are we getting good backups on a daily
> basis? Meaning usable data for a restore in the event of disaster, I was
> told by an associate that we are getting worthless backups without
> Backupexe.
> Also, I know that we have other solutions by backing up the log files
> assuming that the database is not set to "Simple". Suggestions?
> Thanks!
>|||You say it's worthless because of the obvious hard drive failures or some
other reason?
"ChrisR" <noemail@.bla.com> wrote in message
news:e9V9AN0gFHA.1468@.TK2MSFTNGP14.phx.gbl...
> Are you backing up to the same drive that youre db is on? If so, yes it is
> worthless.
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> When using the default backup tool and scheduling them nightly that come
>> with SQL 2000 Standard Edition are we getting good backups on a daily
>> basis? Meaning usable data for a restore in the event of disaster, I was
>> told by an associate that we are getting worthless backups without
>> Backupexe.
>> Also, I know that we have other solutions by backing up the log files
>> assuming that the database is not set to "Simple". Suggestions?
>> Thanks!
>|||The obvious hard drive failures.
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uBrFAl0gFHA.2904@.tk2msftngp13.phx.gbl...
> You say it's worthless because of the obvious hard drive failures or some
> other reason?
> "ChrisR" <noemail@.bla.com> wrote in message
> news:e9V9AN0gFHA.1468@.TK2MSFTNGP14.phx.gbl...
>> Are you backing up to the same drive that youre db is on? If so, yes it
>> is worthless.
>>
>> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
>> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> When using the default backup tool and scheduling them nightly that come
>> with SQL 2000 Standard Edition are we getting good backups on a daily
>> basis? Meaning usable data for a restore in the event of disaster, I
>> was told by an associate that we are getting worthless backups without
>> Backupexe.
>> Also, I know that we have other solutions by backing up the log files
>> assuming that the database is not set to "Simple". Suggestions?
>> Thanks!
>>
>

Backups...daily

Hi,
When using the default backup tool and scheduling them nightly that come
with SQL 2000 Standard Edition are we getting good backups on a daily basis?
Meaning usable data for a restore in the event of disaster, I was told by
an associate that we are getting worthless backups without Backupexe.
Also, I know that we have other solutions by backing up the log files
assuming that the database is not set to "Simple". Suggestions?
Thanks!Hi,
SQL Server Standard backup is allways safe. So do not worry. If it is a
production database you could set the recovery model to "FULL"
and do a Transaction log backup every 30 minutes. Every night you could do a
Differential or FULL database backup.
Transaction log backup with FULL recovery model will allow you to recover
the database fully in the eve of a crash as well
as you could do a POINT_IN_TIME recovery.
SEE THE BELOW SITE FOR BACKUP AND RECOVERY STRATEGY:-
http://www1.us.dell.com/content/top...
555&l=en&s=biz
Thanks
Hari
SQL Server MVP
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When using the default backup tool and scheduling them nightly that come
> with SQL 2000 Standard Edition are we getting good backups on a daily
> basis? Meaning usable data for a restore in the event of disaster, I was
> told by an associate that we are getting worthless backups without
> Backupexe.
> Also, I know that we have other solutions by backing up the log files
> assuming that the database is not set to "Simple". Suggestions?
> Thanks!
>|||Thank you!
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eEg2wG0gFHA.2880@.TK2MSFTNGP09.phx.gbl...
> Hi,
> SQL Server Standard backup is allways safe. So do not worry. If it is a
> production database you could set the recovery model to "FULL"
> and do a Transaction log backup every 30 minutes. Every night you could do
> a Differential or FULL database backup.
> Transaction log backup with FULL recovery model will allow you to recover
> the database fully in the eve of a crash as well
> as you could do a POINT_IN_TIME recovery.
> SEE THE BELOW SITE FOR BACKUP AND RECOVERY STRATEGY:-
> http://www1.us.dell.com/content/top...=555&l=en&s=biz
>
> Thanks
> Hari
> SQL Server MVP
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>|||Are you backing up to the same drive that youre db is on? If so, yes it is
worthless.
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When using the default backup tool and scheduling them nightly that come
> with SQL 2000 Standard Edition are we getting good backups on a daily
> basis? Meaning usable data for a restore in the event of disaster, I was
> told by an associate that we are getting worthless backups without
> Backupexe.
> Also, I know that we have other solutions by backing up the log files
> assuming that the database is not set to "Simple". Suggestions?
> Thanks!
>|||You say it's worthless because of the obvious hard drive failures or some
other reason?
"ChrisR" <noemail@.bla.com> wrote in message
news:e9V9AN0gFHA.1468@.TK2MSFTNGP14.phx.gbl...
> Are you backing up to the same drive that youre db is on? If so, yes it is
> worthless.
>
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:%23rrTM$zgFHA.3540@.TK2MSFTNGP12.phx.gbl...
>|||The obvious hard drive failures.
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uBrFAl0gFHA.2904@.tk2msftngp13.phx.gbl...
> You say it's worthless because of the obvious hard drive failures or some
> other reason?
> "ChrisR" <noemail@.bla.com> wrote in message
> news:e9V9AN0gFHA.1468@.TK2MSFTNGP14.phx.gbl...
>

BackupIoRequest::WaitForIoCompletion failure when restoring database

I have MS SQL 200 Server Developer Edition Installed from MSDN collection. (New installation with service pack 2). When I try to restore 7GB or bigger database, following error occurs in eventlog:

Source: MSSQLSERVER
Category: (6)
ID: 18210
Date: 11.9.2007
Time: 14:50:09
Description:
BackupIoRequest::WaitForIoCompletion: write failure on backup device ''. Operating system error 1450(here is message in local language like "here is no resources to complete requested service").

But I am not writting to backup device, I am restoring. Thank for any helpful answer.

Not sure about the cause of the error.. Check if its related to this KB : http://support.microsoft.com/default.aspx?scid=kb;en-us;304101

|||

Thank you, dinakar.

KB howto i tried, but with no success.

Backup to network drive using Workgroup/Standard.

I am using SQL Server 2005 Express Edition. I am planning on upgrading to either Workgroup or Standard edition. While working with Express Edition I did find out that this version does not support backup to a network drive.
My question is:

Is it possible to backup directly to a network drive using a Workgroup/ Standard edition of SQL Server rather than backing up to a local drive and then 'copy and paste' to a network drive like the Express Edition.

My other question is :
Given a database limit of 50GB, which one of the editions, Workgroup or Standard, will be appropriate for use.Thank you for your time and patience.
Regards
Berly Sam

You cannot backup to a network share with any edition of SQL Server.

SQL Server Backup will only used locally attached drives, or NAS/SAN LUNs. You can either backup locally, and then move the file to a network share (both tasks can be automated with SQL Agent -not included with SQL Express), or Check out the several third party backup tools. (Idera, Red-Gate, to name a couple.)

Workgroup-Standard-Enterprise, which is 'best'. It depends upon the functionality that you require. With a database of that size, you are definitely between the Standard and Enterprise Editions (in my opinion). You may wish to check out the functionality differences at this site.

|||Thats not exactly true, you cannot see the backup media in the SQL Server dialog as it only displays local fixed drives, but you can specify a UNC share within the dialog textbox or within the script. Depending on the situation you should rather consider using a local /SAN / NAS backup first and then copy it to a network share if needed.

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Jens,

I consider it a gentle ‘challenge’ for me to give more consideration to why I responded as I did. And I appreciate that.

As I contemplate why I thought so, all I can remember is ever since 6.5, I have always taught to backup locally and xcopy to a net share. I can only imagine that was because of the speed issues of what used to be slower networks, as well as the persistence and permissions issues related to mapped drives.

And I now realize that I have not reconsidered or changed that practice in the intervening years.

I’m glad that you challenged me, now I have tested and affirmed that a backup to a UNC works just fine. But I doubt that I will change my practice of Backing up locally and using xcopy to move the backup file to a network resource -the BACKUP won't fail because of any network issues.

Regards,

- Arnie Rowland