Fulldatabase backup query

SQL Server full backup displays the following message on successful
completion of the full database backup.
Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
MB/sec).
I understand SQL Server manages data files in the form of pages and thats
the reason on completion of backup it display message "Processed 1136 pages
for database 'MyDB', file 'MyDB' on file 1". But why does it display message
"Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when the
transaction log files are not managed in the form of pages.Hi
When BACKUP started , it reads (backups) all data pages and last step it
goes to LOG file and reads/backups all the data in the LOG from the point
the BACKUP was started
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136
> pages
> for database 'MyDB', file 'MyDB' on file 1". But why does it display
> message
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when
> the
> transaction log files are not managed in the form of pages.
>|||The backup database process includes the log records produced while the backup was running. When you
do RESTORE, the log records are used to give you a consistent view of the data (by doing REDO and
UNDO of those log records, just as each time the database is started),.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Balaji" <Balaji@.discussions.microsoft.com> wrote in message
news:CA26E224-37C4-4C61-8F37-579C7A357DE7@.microsoft.com...
> SQL Server full backup displays the following message on successful
> completion of the full database backup.
> Processed 1136 pages for database 'MyDB', file 'MyDB' on file 1.
> Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1.
> BACKUP DATABASE successfully processed 1139 pages in 0.902 seconds (10.336
> MB/sec).
> I understand SQL Server manages data files in the form of pages and thats
> the reason on completion of backup it display message "Processed 1136 pages
> for database 'MyDB', file 'MyDB' on file 1". But why does it display message
> "Processed 3 pages for database 'MyDB', file 'MyDB_log' on file 1" when the
> transaction log files are not managed in the form of pages.
>

full, differential, transaction hwo to rotate the differential?

Being of the "point and click"-generation I managed to create some sort of a fairly simple backup plan for our databases. There are hourly transactional backups and daily full backups, which were set up with a database maintenance plan. As the databases store event records they are ever increasing around the hour. The daily backups are now of a size that holding them is not feasable anymore and I want to move to a differential backup scheme:

Weekly full backups

Daily differential backups

Hourly transactional log backups

The problem I have is that the database maintenance plans allow me to rotate backup files automatically as they included the date and time of the backup. For differential backups there is no option in the Database Maintenance plan so I want to create them manually. The problem now is that I can create one device, append the differential backup to it. But how do I rotate the differential backup device name, let's say bi-weekly?

(untested):

1. script out the diff backup plan.
2. create a sql job that runs every 2 week that drops the diff plan, creates a new one with the desired device name.|||

Do you mean with the SQL-DMO? Or is there another way

oj wrote:

(untested):

1. script out the diff backup plan.
2. create a sql job that runs every 2 week that drops the diff plan, creates a new one with the desired device name.

|||

So basically I have no clue

1) how to script out a diff backup plan

2) how to create a sql job that drops the diff plan, creates a new one with the desired device name.

|||

I am not in front of a sqlserver so can't verify. but if:

1. create a differential backup job just as you would normally.

2. go to sql jobs under sqlagent, right click on the job and script it out. This is where you get the definition for the diff job (i.e. job id, name, steps, etc.).

3. take note of the step id and steps definition.

4. create a new sql job that runs every 4 week. In the jobstep definition for this new job (say, switchdevice), you'd want to execute

sp_update_jobstep @.jobname='the_diff_jobname',@.stepid=<the stepid of the diff job>,@.command='new_backup_command_pointing_to_a_desired_device'

5. create another job that does the same thing as the #4 but with a different device name. Be sure to schedule 2 weeks before or after the job in #4.

With the combo of #4 and #5, you essentially have a device name changed every 2 week.

|||thanks for your elaborat answer oj. one thing is still puzzling me. If I create the diff backup to append to the device it will append even after switching. So the device will be ever growing. We can live with a device per week and manually cleanup old one's. Would you know a way to automatically generate these devices? Or should I stop trying and just create them by hand?|||

You can take a look at sp_addumpdevice and sp_dropdevice in sql book online.

Cheers,

|||

Ok, Thanks for the support here. What we end up doing is the following:

We've created two backup devices per database

Two bi-weekly (every odd/even week) scheduled job performs a full back with INIT
BACKUP DATABASE base
TO base_wk<n>
WITH INIT

A daily job backs up a differential
BACKUP DATABASE base
TO base_wk<n>
WITH DIFFERENTIAL

Every half hour a transaction log back is performed
BACKUP LOG base
TO base_wk<n>

In each case <n> is either 1 or 0 for odd and even weeks. Numerous links I've found on backups seem to fail to see the real possibility that during a full backup due to a hardware failure both database and backup are lost, not really disastor save, which backing up is all about.

So there are in total three scheduled jobs: one weekly, one daily and one every half hour. schedule in bi-weekly intervals writing to base_wk0 and base_wk1 alternatively. Furthermore for historic reasons a monthly full backup is scheduled using the wizard which stores a unique backup file for every month.

Let the disastors happen...

full, differential, transaction hwo to rotate the differential?

Being of the "point and click"-generation I managed to create some sort of a fairly simple backup plan for our databases. There are hourly transactional backups and daily full backups, which were set up with a database maintenance plan. As the databases store event records they are ever increasing around the hour. The daily backups are now of a size that holding them is not feasable anymore and I want to move to a differential backup scheme:

Weekly full backups

Daily differential backups

Hourly transactional log backups

The problem I have is that the database maintenance plans allow me to rotate backup files automatically as they included the date and time of the backup. For differential backups there is no option in the Database Maintenance plan so I want to create them manually. The problem now is that I can create one device, append the differential backup to it. But how do I rotate the differential backup device name, let's say bi-weekly?

(untested):

1. script out the diff backup plan.
2. create a sql job that runs every 2 week that drops the diff plan, creates a new one with the desired device name.|||

Do you mean with the SQL-DMO? Or is there another way

oj wrote:

(untested):

1. script out the diff backup plan.
2. create a sql job that runs every 2 week that drops the diff plan, creates a new one with the desired device name.

|||

So basically I have no clue

1) how to script out a diff backup plan

2) how to create a sql job that drops the diff plan, creates a new one with the desired device name.

|||

I am not in front of a sqlserver so can't verify. but if:

1. create a differential backup job just as you would normally.

2. go to sql jobs under sqlagent, right click on the job and script it out. This is where you get the definition for the diff job (i.e. job id, name, steps, etc.).

3. take note of the step id and steps definition.

4. create a new sql job that runs every 4 week. In the jobstep definition for this new job (say, switchdevice), you'd want to execute

sp_update_jobstep @.jobname='the_diff_jobname',@.stepid=<the stepid of the diff job>,@.command='new_backup_command_pointing_to_a_desired_device'

5. create another job that does the same thing as the #4 but with a different device name. Be sure to schedule 2 weeks before or after the job in #4.

With the combo of #4 and #5, you essentially have a device name changed every 2 week.

|||thanks for your elaborat answer oj. one thing is still puzzling me. If I create the diff backup to append to the device it will append even after switching. So the device will be ever growing. We can live with a device per week and manually cleanup old one's. Would you know a way to automatically generate these devices? Or should I stop trying and just create them by hand?|||

You can take a look at sp_addumpdevice and sp_dropdevice in sql book online.

Cheers,

|||

Ok, Thanks for the support here. What we end up doing is the following:

We've created two backup devices per database

Two bi-weekly (every odd/even week) scheduled job performs a full back with INIT
BACKUP DATABASE base
TO base_wk<n>
WITH INIT

A daily job backs up a differential
BACKUP DATABASE base
TO base_wk<n>
WITH DIFFERENTIAL

Every half hour a transaction log back is performed
BACKUP LOG base
TO base_wk<n>

In each case <n> is either 1 or 0 for odd and even weeks. Numerous links I've found on backups seem to fail to see the real possibility that during a full backup due to a hardware failure both database and backup are lost, not really disastor save, which backing up is all about.

So there are in total three scheduled jobs: one weekly, one daily and one every half hour. schedule in bi-weekly intervals writing to base_wk0 and base_wk1 alternatively. Furthermore for historic reasons a monthly full backup is scheduled using the wizard which stores a unique backup file for every month.

Let the disastors happen...

full, differential, transaction hwo to rotate the differential?

Being of the "point and click"-generation I managed to create some sort of a fairly simple backup plan for our databases. There are hourly transactional backups and daily full backups, which were set up with a database maintenance plan. As the databases store event records they are ever increasing around the hour. The daily backups are now of a size that holding them is not feasable anymore and I want to move to a differential backup scheme:

Weekly full backups

Daily differential backups

Hourly transactional log backups

The problem I have is that the database maintenance plans allow me to rotate backup files automatically as they included the date and time of the backup. For differential backups there is no option in the Database Maintenance plan so I want to create them manually. The problem now is that I can create one device, append the differential backup to it. But how do I rotate the differential backup device name, let's say bi-weekly?

(untested):

1. script out the diff backup plan.
2. create a sql job that runs every 2 week that drops the diff plan, creates a new one with the desired device name.|||

Do you mean with the SQL-DMO? Or is there another way

oj wrote:

(untested):

1. script out the diff backup plan.
2. create a sql job that runs every 2 week that drops the diff plan, creates a new one with the desired device name.

|||

So basically I have no clue

1) how to script out a diff backup plan

2) how to create a sql job that drops the diff plan, creates a new one with the desired device name.

|||

I am not in front of a sqlserver so can't verify. but if:

1. create a differential backup job just as you would normally.

2. go to sql jobs under sqlagent, right click on the job and script it out. This is where you get the definition for the diff job (i.e. job id, name, steps, etc.).

3. take note of the step id and steps definition.

4. create a new sql job that runs every 4 week. In the jobstep definition for this new job (say, switchdevice), you'd want to execute

sp_update_jobstep @.jobname='the_diff_jobname',@.stepid=<the stepid of the diff job>,@.command='new_backup_command_pointing_to_a_desired_device'

5. create another job that does the same thing as the #4 but with a different device name. Be sure to schedule 2 weeks before or after the job in #4.

With the combo of #4 and #5, you essentially have a device name changed every 2 week.

|||thanks for your elaborat answer oj. one thing is still puzzling me. If I create the diff backup to append to the device it will append even after switching. So the device will be ever growing. We can live with a device per week and manually cleanup old one's. Would you know a way to automatically generate these devices? Or should I stop trying and just create them by hand?|||

You can take a look at sp_addumpdevice and sp_dropdevice in sql book online.

Cheers,

|||

Ok, Thanks for the support here. What we end up doing is the following:

We've created two backup devices per database

Two bi-weekly (every odd/even week) scheduled job performs a full back with INIT
BACKUP DATABASE base
TO base_wk<n>
WITH INIT

A daily job backs up a differential
BACKUP DATABASE base
TO base_wk<n>
WITH DIFFERENTIAL

Every half hour a transaction log back is performed
BACKUP LOG base
TO base_wk<n>

In each case <n> is either 1 or 0 for odd and even weeks. Numerous links I've found on backups seem to fail to see the real possibility that during a full backup due to a hardware failure both database and backup are lost, not really disastor save, which backing up is all about.

So there are in total three scheduled jobs: one weekly, one daily and one every half hour. schedule in bi-weekly intervals writing to base_wk0 and base_wk1 alternatively. Furthermore for historic reasons a monthly full backup is scheduled using the wizard which stores a unique backup file for every month.

Let the disastors happen...

sql

full uninstall of MSSQL 2005 Ent SP1

Hi,

I am facing a serious problem with the unproper uninstall. I have installed MSSQL 2005 Enterprise and created an Active Directory at the server. I have removed the AD and wanted to uninstall SQL 2005.

I was not able to uninstall it fully. I have reinstalled it several times, just to tryying to remove the registry entries.

Is there a solution / tool or a document describing, how I can fully manually remove MS SQL 2005 from a server?

I have already installed SP1.

Dejan

What isn't being uninstalled? Is the uninstall completing, but leaving behind files/registry keys? Or does the uninstall fail somewhere along the way?

Thanks,
Sam Lester (MSFT)

|||

Hi Dejan,

here is an article for removal of SQL Server 2005 which would be helpful to you but in order to get a good answer please re-phrase your question is that only registry which won't removes or some files are their ?

http://msdn2.microsoft.com/en-us/library/aa337087.aspx

Regards

|||

Hi Sam,

I am sorry for my late reply. The uninstall is successful, but the install already reports some errors. It leaves files and registry entries behind.

\Program Files (x86)\Microsoft SQL Server\90\COM

REPLAGNT.dll

REPLDP.dll

snapshot.exe

sqlwep.dll

sqlresld90.dll

\Program Files (x86)\Microsoft SQL Server\90\EULA

\Program Files (x86)\Microsoft SQL Server\90\Shared

D:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn

Here is a portion of the MSSQL 2005 registry entries left behind in the registry after uninstall. Although I delete it manually from the registry (via regedit), it does not help me when I try reinstalling MS SQL 2005 Ent. (64-bit).

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
Class Name: <NO CLASS>
Last Write Time: 12/3/2006 - 12:13 PM

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: CurrentVersion
Type: REG_SZ
Data: 9.00.2047.00

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: ProtocolList
Type: REG_MULTI_SZ
Data: np

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Np
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: PipeName
Type: REG_SZ
Data: \\.\pipe\sql\query

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: TcpPort
Type: REG_SZ
Data: 1433

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: SQLPath
Type: REG_SZ
Data: D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL

|||

Hi,

after uninstall, I noticed on many places that registry entries have not been removed (several hundred places). I do not have a complete list (too many entries).

After uninstall, I try to install MSSQL 2005 Ent. (64-bit) once again. System Configuration Check goes fine (all are with status = Success). See the attached report at the end (att 1).

At the selection of components, I check all options (I can not select SQL Server failover cluster).

I select "Default instance". For service account, I choose "Use built-in System account" and select "Local system". By default, the following are selected to start and the end of the setup (SQL server, Analysis Service, Reporting Service). SQL Server agent is unchecked. Also, "Customize for each service account is unchecked".

For the Authentication Model, I select Mixed model (I have entered a password).

SQL Collation is set to "Slovenian dictionary order, case-sensitive, for use with 1250 (Central European).

Report Server is set to default configuration.

Overview of the installing components (see att 2). I click "Install" to start the installation.

I get an error message : An instance with the same name already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name. (Error at SQL Server Database Service). See att 3 for more details from the log file.

I get also an error message with the Reporting services : "There was un unexpected failure during the setup wizard. You may review the setup logs ... Event ID: 50000. I have my content of the 2 installation CDs copied to a hard disk.

__

Att 1:

System Configuration Check

- WMI Service Requirement (Success)

Messages

WMI Service Requirement

Check Passed

- MSXML Requirement (Success)

Messages

MSXML Requirement

Check Passed

- Operating System Minimum Level Requirement (Success)

Messages

Operating System Minimum Level Requirement

Check Passed

- Operating System Service Pack Level Requirement. (Success)

Messages

Operating System Service Pack Level Requirement.

Check Passed

- SQL Server Edition Operating System Compatibility (Success)

Messages

SQL Server Edition Operating System Compatibility

Check Passed

- Minimum Hardware Requirement (Success)

Messages

Minimum Hardware Requirement

Check Passed

- IIS Feature Requirement (Success)

Messages

IIS Feature Requirement

Check Passed

- Pending Reboot Requirement (Success)

Messages

Pending Reboot Requirement

Check Passed

- Performance Monitor Counter Requirement (Success)

Messages

Performance Monitor Counter Requirement

Check Passed

- Default Installation Path Permission Requirement (Success)

Messages

Default Installation Path Permission Requirement

Check Passed

- Internet Explorer Requirement (Success)

Messages

Internet Explorer Requirement

Check Passed

- COM Plus Catalog Requirement (Success)

Messages

COM Plus Catalog Requirement

Check Passed

- ASP.Net Version Registration Requirement (Success)

Messages

ASP.Net Version Registration Requirement

Check Passed

- Minimum MDAC Version Requirement (Success)

Messages

Minimum MDAC Version Requirement

Check Passed

Att 2

The following components will be installed:SQL Server Database Services

(Database Services, Replication, Full-Text Search)Analysis Services

Reporting Services(Reporting Services, Report Manager)Notification Services

Integration Services

Client Components(Connectivity Components, Management Tools, Business Intelligence Development Studio, SQL Server Books Online)

Att 3

<Func Name='ValidateInstanceName'>
Error Code: 0x80076db6 (28086)
Windows Error Text: Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Wed Sep 21 01:10:12 2005
Function Name: ValidateInstanceName
Source Line Number: 445

Error Code: 28086
MSI (s) (E8!D4) [12:45:13:054]: Product: Microsoft SQL Server 2005 (64-bit) -- Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
<EndFunc Name='LaunchFunction' Return='28086' GetLastError='0'>

|||

Hi,

here are steps to perform Manuall uninstalltion of SQL Express Edition

http://support.microsoft.com/kb/909967

http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

thank you for your reply. Is the uninstall the same for the SQL 2005 64-bit Dev Edition?

Thanks!

Dejan

|||

Hi Dejan,

AFAIK it is the same process to be follow while uninstalling 64-bit edition.

HTH

Hemantgiri S. Goswami

full uninstall of MSSQL 2005 Ent SP1

Hi,

I am facing a serious problem with the unproper uninstall. I have installed MSSQL 2005 Enterprise and created an Active Directory at the server. I have removed the AD and wanted to uninstall SQL 2005.

I was not able to uninstall it fully. I have reinstalled it several times, just to tryying to remove the registry entries.

Is there a solution / tool or a document describing, how I can fully manually remove MS SQL 2005 from a server?

I have already installed SP1.

Dejan

What isn't being uninstalled? Is the uninstall completing, but leaving behind files/registry keys? Or does the uninstall fail somewhere along the way?

Thanks,
Sam Lester (MSFT)

|||

Hi Dejan,

here is an article for removal of SQL Server 2005 which would be helpful to you but in order to get a good answer please re-phrase your question is that only registry which won't removes or some files are their ?

http://msdn2.microsoft.com/en-us/library/aa337087.aspx

Regards

|||

Hi Sam,

I am sorry for my late reply. The uninstall is successful, but the install already reports some errors. It leaves files and registry entries behind.

\Program Files (x86)\Microsoft SQL Server\90\COM

REPLAGNT.dll

REPLDP.dll

snapshot.exe

sqlwep.dll

sqlresld90.dll

\Program Files (x86)\Microsoft SQL Server\90\EULA

\Program Files (x86)\Microsoft SQL Server\90\Shared

D:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn

Here is a portion of the MSSQL 2005 registry entries left behind in the registry after uninstall. Although I delete it manually from the registry (via regedit), it does not help me when I try reinstalling MS SQL 2005 Ent. (64-bit).

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
Class Name: <NO CLASS>
Last Write Time: 12/3/2006 - 12:13 PM

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: CurrentVersion
Type: REG_SZ
Data: 9.00.2047.00

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: ProtocolList
Type: REG_MULTI_SZ
Data: np

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Np
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: PipeName
Type: REG_SZ
Data: \\.\pipe\sql\query

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: TcpPort
Type: REG_SZ
Data: 1433

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup
Class Name: <NO CLASS>
Last Write Time: 11/18/2006 - 8:39 AM
Value 0
Name: SQLPath
Type: REG_SZ
Data: D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL

|||

Hi,

after uninstall, I noticed on many places that registry entries have not been removed (several hundred places). I do not have a complete list (too many entries).

After uninstall, I try to install MSSQL 2005 Ent. (64-bit) once again. System Configuration Check goes fine (all are with status = Success). See the attached report at the end (att 1).

At the selection of components, I check all options (I can not select SQL Server failover cluster).

I select "Default instance". For service account, I choose "Use built-in System account" and select "Local system". By default, the following are selected to start and the end of the setup (SQL server, Analysis Service, Reporting Service). SQL Server agent is unchecked. Also, "Customize for each service account is unchecked".

For the Authentication Model, I select Mixed model (I have entered a password).

SQL Collation is set to "Slovenian dictionary order, case-sensitive, for use with 1250 (Central European).

Report Server is set to default configuration.

Overview of the installing components (see att 2). I click "Install" to start the installation.

I get an error message : An instance with the same name already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name. (Error at SQL Server Database Service). See att 3 for more details from the log file.

I get also an error message with the Reporting services : "There was un unexpected failure during the setup wizard. You may review the setup logs ... Event ID: 50000. I have my content of the 2 installation CDs copied to a hard disk.

__

Att 1:

System Configuration Check

- WMI Service Requirement (Success)

Messages

WMI Service Requirement

Check Passed

- MSXML Requirement (Success)

Messages

MSXML Requirement

Check Passed

- Operating System Minimum Level Requirement (Success)

Messages

Operating System Minimum Level Requirement

Check Passed

- Operating System Service Pack Level Requirement. (Success)

Messages

Operating System Service Pack Level Requirement.

Check Passed

- SQL Server Edition Operating System Compatibility (Success)

Messages

SQL Server Edition Operating System Compatibility

Check Passed

- Minimum Hardware Requirement (Success)

Messages

Minimum Hardware Requirement

Check Passed

- IIS Feature Requirement (Success)

Messages

IIS Feature Requirement

Check Passed

- Pending Reboot Requirement (Success)

Messages

Pending Reboot Requirement

Check Passed

- Performance Monitor Counter Requirement (Success)

Messages

Performance Monitor Counter Requirement

Check Passed

- Default Installation Path Permission Requirement (Success)

Messages

Default Installation Path Permission Requirement

Check Passed

- Internet Explorer Requirement (Success)

Messages

Internet Explorer Requirement

Check Passed

- COM Plus Catalog Requirement (Success)

Messages

COM Plus Catalog Requirement

Check Passed

- ASP.Net Version Registration Requirement (Success)

Messages

ASP.Net Version Registration Requirement

Check Passed

- Minimum MDAC Version Requirement (Success)

Messages

Minimum MDAC Version Requirement

Check Passed

Att 2

The following components will be installed:SQL Server Database Services

(Database Services, Replication, Full-Text Search)Analysis Services

Reporting Services(Reporting Services, Report Manager)Notification Services

Integration Services

Client Components(Connectivity Components, Management Tools, Business Intelligence Development Studio, SQL Server Books Online)

Att 3

<Func Name='ValidateInstanceName'>
Error Code: 0x80076db6 (28086)
Windows Error Text: Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Wed Sep 21 01:10:12 2005
Function Name: ValidateInstanceName
Source Line Number: 445

Error Code: 28086
MSI (s) (E8!D4) [12:45:13:054]: Product: Microsoft SQL Server 2005 (64-bit) -- Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
<EndFunc Name='LaunchFunction' Return='28086' GetLastError='0'>

|||

Hi,

here are steps to perform Manuall uninstalltion of SQL Express Edition

http://support.microsoft.com/kb/909967

http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

thank you for your reply. Is the uninstall the same for the SQL 2005 64-bit Dev Edition?

Thanks!

Dejan

|||

Hi Dejan,

AFAIK it is the same process to be follow while uninstalling 64-bit edition.

HTH

Hemantgiri S. Goswami

Full T-Log: options?

An automatic monthly delete has recently grown from 15 to 20 million rows. It is now filling my 70GB T-Log completly. I don't have any space to expand the T-Log. Do I have any options other than reducing the number of rows in the delete?Is the database in full or simple recovery mode?

In either case, batch your deletes in small chunks instead of trying to do them all at once (say 1M or 100K or 10K at a time).

If you are in simple mode, when the batch finishes, a database checkpoint will occur and the log will be truncated and the space allocated for reuse.

If you are in full recovery mode, perform a tran log backup before starting the next batch and the log will be truncated and the space allocated for reuse.|||In either case, batch your deletes in small chunks instead of trying to do them all at once (say 1M or 100K or 10K at a time).


x2.

Also, you should set a performance alert on you transaction log to kick off when the log reaches xx% full. Have the action of the alert set to kick off a transaction log backup. This will NOT work unless you batch your deletes into smaller quantities, but it should work well in conjunction with batching.

For example, my db is set to do a custom defrag Sunday nights. The defrag is broken up into about 50 steps and takes about 45 minutes. During the process, about 50 GB of data is written to the t-log (which is 35 GB in size). I have the performance alert set to trigger when the t-log is 60% full with a ten minute interval set between responses.

This way, when the log file gets to about 60% full, the transaction log backup kicks off automatically. The process repeats itself until the defrags are complete.

Be SURE to set the response interval to something realistic; I once forgot and watched as the response kicked off every second (for something different) and there was nothing I could do to stop it.

Regards,

hmscott