Changes To Cloned Database Are Affecting The Original

Oct 20, 2006

I am trying to use SQL Express to support unit testing of functionality which requires database access.

I created an express database (.mdf) which contains a database snapshot which is the database environment that each test expects to see when it starts. Through the execution of the test the database will be modified arbitrarily and I need to reset the database to the original state before the next test executes.

Here's what I do today:

Before Test:

The original database is copied to a unique location in the temp directory
A unique database name is generated (GUID-based)
I connect to the new database file with:

Server=.SQLEXPRESS;AttachDbFilename="PathToTempFile";Database="GuidDBName";Initial Catalog="GuidDBName";Trusted_Connection=Yes;User Instance=true

During the test all database access is routed to the temporary database GuidDBName

After Test:

Close all active database connections and clear the connection pool
Connect to the master database and detach the database:

Server=.SQLEXPRESS;Database=master;Initial Catalog=master;Trusted_Connection=Yes;User Instance=true - sp_detach_db 'GuidDBName'


Delete the temporary file

When I do this, everything seems to work correctly but when I re-open the original database it has changed unexpectedly and includes the modifications that were made by the test as it ran.

Can anyone explain why this is happening and/or provide a solution?

View 1 Replies


ADVERTISEMENT

How To Copy Database Structure From One Db To Another W/o Affecting Data

Jul 23, 2005

Is there a way to copy the structure from one database to anotherwithout affecting the actual data?For example, I added new fields and stored procedures to a db in mydevelopment environment. There are a lot of them.I now want to make the same changes to my production environment db butdon't want to affect the data. Only the fields, stored procs &constraints and stuff pertaining to the structure of the db should bechanged.Does anyone know of a program that can do this or can this be done inMS SQL Enterprise Manager.Any help would be appreciated.7078895

View 2 Replies View Related

I Want To Revert Back To Original State Of Database Before I Performed Restore Database

Nov 15, 2006

Hello,i am in great trouble. I want to revert back to original state ofdatabase before i performed restore database on my sql server 2KDatabase. Accidently i didn't take backup of my Database and i didrestore, so is there any way to get the original state back of myDatabase?Any suggestion will be highly appriciated.Regards,S. Domadia.

View 2 Replies View Related

Weekly Update Part Of Database With Data From Original Database

Mar 26, 2008

Hi!

I have an original database that I want to copy once to another database. Then I want to update the data weekly with the data of the original database. I don€™t change any tables or columns in that part of the database. Just some tables more in the €˜new€™ database (than the tables from the original database) with some references to the tables that have to be updated weekly.
How can I do this? (if you know what I mean... it's a sort of a datawarehouse where different sources come together.. that part that represents the original database is just a part of the datawarehouse. That part is exactly the same structure as the original database.)

Thanks,

Sandra

View 1 Replies View Related

Cloned SQL 2005 Install

May 11, 2007

I need a little help with a cloned SQL 2005 install. We have a couple of Virtual Machines that SQL 2005 was installed on. The install was orginally completed on <pc1> and then duped over to <pc2>. The problem now is that <pc2> is showing information from <pc1> everywhere. I have reviewd this document: http://msdn2.microsoft.com/en-us/library/ms143799.aspx, and it doesn't seem to help any. I have used the sp_dropserver command with 'droplogins' to try to recreate the logins for <pc2> but it's still showing the logins from <pc1>. Can someone please help me out, I'm not sure what I'm doing wrong here. Thanks!

View 2 Replies View Related

Original Database Size

Dec 7, 2006

Hi All,

How can I find out the original size of the database?

Thanks.

View 5 Replies View Related

How To Getback Original Copy Of Northwind Database?

Apr 15, 2008

Hi,Good morning to All.
While doing practice I did some modifications to some tables in Northwind database.Now, how can I get my original tables back again?
Take Oracle for example:We can modify table data. But when we run demobld.sql script then all tables will replaces with original entries.
Like this I want in SQL Server also. Is there any such facility available in SQL Server?
Thanks in advance,Ashok kumar.

View 2 Replies View Related

Copied Database Maintains Original Name In Backups

Mar 27, 2007

I made a copy of a database "sac_prod" and named the new copy "vgs_prod". Now, when I do a backup of the new database, it still shows the name of the original. Is there any way to change this so it will be the same as the new database name?Here is the BACKUP script:BACKUPdatabase vgs_prod TODISK='\sac-srvr1data$TechnicalSharedProductionSQLBackup LasVegasvgs_prod_CopyOnly.BAK' with COPY_ONLYHere is the messages I received from this BACKUP:Processed 1752 pages for database 'vgs_prod', file 'sac_prod' on file 1.Processed 6 pages for database 'vgs_prod', file 'sac_prod_log' on file 1.BACKUP DATABASE successfully processed 1758 pages in 0.412 seconds (34.955 MB/sec). I would like to change the file 'sac_prod' to be 'vgs_prod' in lines 1 and 2 just above. Thanks,

View 2 Replies View Related

Saving Original SQL Database And My.Settings When Reinstalling Or Updating

Apr 27, 2007



Hello all...



I am working on a project that contains several databases in SQL and many settings. The problem I am encountering is that I want to be able to update the program for all my customers. That is no problem.

The problem I am meeting is where, when the program is updated, all the settings and all the information in the databases reverts to the default values, or the values that were compiled with the new update.

I want to be able to update their program without deleting all the settings they have.



Thanks,

Andreas Renberg

View 1 Replies View Related

Data Access :: Cannot Open Database After Changing Its Name And Change Back To Its Original Name

Sep 3, 2015

I cannot open now my database after changing it name from the folder where it is save and also changed back to its original name.Message recovery pending now is appearing as shown below.Any chance that I could recover my database back?

View 17 Replies View Related

Affecting Performance?

Dec 17, 2005

I have a table with 23 columns.  8 columns are not always filled by users and so valued to default.  Would this affect the overall performance of querying this table?  Should I separate those 8 columns and link with a one-to-one relation?

Thanks

View 3 Replies View Related

Triggers Affecting Multiple Tables

May 4, 2004

I have a table "PageInfo" wich has columns "PageID, Title(has "AboutUs" as one of the values), DateModified, Active". My other table is "AboutUs" and has columns "ID, WhatsNew, Welcome, Active".

My goal here is that if table "AboutUs" is affected as an "INSERT" or an "UPDATE" on any row, I want "PageInfo.DateModified" WHERE "PageInfo.Title = AboutUs" to be updated with "getDate()". Don't know if I'm clear enough but thanks in advance.

Gazzou

View 7 Replies View Related

Insert Statement Not Affecting Any Rows

Feb 4, 2008

I have the following code:



Code Snippet
INSERT INTO [CICC].[dbo].[972createtest]
SELECT
Always81,
AccountNumber,
CAST(SUBSTRING(DateOfPayment,5,2) + SUBSTRING(DateOfPayment,1,2) + SUBSTRING(DateOfPayment,3,2) as datetime), CAST(TotalPmtAmt AS decimal(9,2))/100,
Collector,
PmtCode,
CAST(AmtPdToAgency AS decimal(9,2))/100,
CAST(AmtPdToClient AS decimal(9,2))/100

FROM [CICC].[dbo].[972create]


I'm trying to insert data into the table called 972createtest. It has the following columns and datatypes:


[Always81] [smallint] NULL,

[AccountNumber] [nvarchar](8) NULL,

[DateOfPayment] [nvarchar](6) NULL,

[TotalPmtAmt] [decimal](11, 2) NULL,

[Collector] [nvarchar](3) NULL,

[PmtCode] [smallint] NULL,

[AmtPdToAgency] [decimal](11, 2) NULL,

[AmtPdToClient] [decimal](11, 2) NULL

And here's a sample of the data stored in those columns:



81 01068713 092107 40.00 NJW 31 4000.00 0.00

81 01068713 111207 2000.00 NJW 31 2000.00 0.00

81 01068784 110806 10000.00 KSD 31 10000.00 0.00

81 01068784 121506 10000.00 KSD 31 10000.00 0.00

81 01068784 030507 10000.00 KSD 31 10000.00 0.00

81 01068784 033007 14100.00 KSD 31 14100.00 0.00

81 01068784 051807 7400.00 KSD 34 7400.00 0.00

Everytime I try to run the code, I get a message telling me "0 row(s) affected". What stupid thing am I doing wrong?

View 8 Replies View Related

Affecting SELECT Rows To A Table Variable

Aug 16, 2006

Hi,

I would like to know how to add SELECT row to a table variable. It's not for my SELECT syntax(code following is just an ugly example) that I want help it's for the use of table variable.
Your help will greatly appreciate!!!

ex :
DECLARE @MyTestVar table (
idTest int NOT NULL,
anotherColumn int NOT NULL)

SET @MyTestVar = (SELECT idTest, anotherColumn FROM tTest)-- This cause an error :-- Must declare the variable '@MyTestVar'. ???? What?

View 3 Replies View Related

SQL Server 2008 :: Lock Out Users Without Affecting Replication?

Sep 1, 2015

We are approaching the "go live" date of a big application upgrade, so while the application is being upgraded i was asked to lock out all users and backup all databases and make sure the data isnt changed during a period of time

It turns out, as one of my databases is being replicated to another server, i cant put that database in read_only mode, or restricted_mode, without removing the replication.

Removing the replication means i have to set it up again and that means another 3 hours added to an already cram-packed weekend without sleep!

How I can lock out the users to make sure there are no changes to a database other then read_only/restricted_mode/single_user ?

I really don't want to touch that replication...

View 0 Replies View Related

Factors Affecting Effort Estimate For SSIS Package

Aug 30, 2007

Hi,

I need to estimate the effort required in writing some SSIS packages.
Could anyone provide some pointers to the various factors (E.g. number of tables, source, etc.) which influence the effort estimate for SSIS packages?

Thanks in advance.

Regards,
B@ns

View 4 Replies View Related

SQL Server 2014 :: CASE Condition Not Affecting CAST Output

Jun 10, 2014

I've a variable in my SP that I'd like to use to change the format of my output. Try this!

select case when 1=2 then cast(1 as decimal(10,2)) else cast(2 as decimal(10,0)) end

Then this:

select case when 1=1 then cast(1 as decimal(10,2)) else cast(2 as decimal(10,0)) end

Why in either case, the output is returned as n.nn ? Whilst single select expressions (like these):

select cast(1 as decimal(10,2)) -- = 1.00
select cast(2 as decimal(10,0)) -- = 2

Work fine.

View 8 Replies View Related

Reporting Services :: Select Query - Formatting A Date Affecting MIN

Sep 2, 2015

In my SELECT query I have: MIN(a.orderdue) AS 'Oldest order date'

This works in that it brings through the oldest order date, however it brings through a date format like: 2015-06-11 11:30.000

So I amended the SELECT query to:

MIN (CONVERT(varchar(17),a.orderdue,103)) AS 'Oldest order date'

This brings the date through as 11/06/2015, which is preferable.

But I have noticed that doing this has affected the output: the MIN function no longer returns the first (oldest) date, but a completely different value.

Obviously my changing the formatting for the date has affected the MIN output. Is there any way I can amend the formatting of the date without this happening?

View 3 Replies View Related

How To Customize SSRS 2000 HTML Viewer Without Affecting Other Folders Or Clients?

Apr 17, 2007

Hi all,



Got a good question to ask. At the moment, I do not have any control over the reporting server webserver. This is due to the company's policy. The webhosting is controled by antoher department.



Anyways, the question is the following:- Is there a way to customize the config file for the htmlviewer (css style sheet, rendering and others) for a specific client without affecting the rest ?



There are about 20 clients on a server, and I am responsible for one of them. I had customized my config file to render or allow only two formats for this particular client. Since I don't have any control over the websever, I just can't replace the config file without affecting the others. How do i do this ? I just want th config file to ONLY affect a certain client's HTMLViewer and not the others. I tried to do some research on this, but came up empty handed.



Thanks !



Bernard

View 4 Replies View Related

Installing Sp1 On Cloned DB Server To VM Server

Feb 6, 2007

We have a HP server with windows 2003. MS sql 2005 was installed on it. The third party databases were installed. SP1 was never installed. This server (paahouentsqlp) PROD was cloned and placed on a vm server.

When server came up on vm enviornment the server name was changed to (paahouentsqlt) TEST. Nothing was done to the SQL environment. No registery entries were altered. No sp_dropserver or sp_addserver were ran. TEST server seems to be running ok.

I have attempted to install sp1 on TEST server (paahouentsqlt). The enumeration process takes about 1-2 hrs. When I finally get a screen all product selections are grey out except for SQL Server Native Client, Setup Support File, MSXML 6.0 Parser, SQLXML4, Backward Compatibility, and MS SQL Server VSS Writer. Than I'm prompted with a couple of NEXT screens, than Finish.

When I look at the product version it still shows it as the original 9.0.1399

Any ideas? Log included.

02/03/2007 11:27:23.786 ================================================================================
02/03/2007 11:27:23.801 Hotfix package launched
02/03/2007 11:27:23.801 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:23.801 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:23.817 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:23.817 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:24.239 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.239 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:24.239 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.239 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:24.239 Local Computer:
02/03/2007 11:27:24.255 Target Details: PAAHOUENTSQLT
02/03/2007 11:27:24.255 commonfilesdir = C:Program FilesCommon Files
02/03/2007 11:27:24.255 lcidsupportdir = e:50b73396ce0726e1761033
02/03/2007 11:27:24.255 programfilesdir = C:Program Files
02/03/2007 11:27:24.255 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 11:27:24.255 supportdirlocal = e:50b73396ce0726e176
02/03/2007 11:27:24.255 windir = C:WINDOWS
02/03/2007 11:27:24.255 winsysdir = C:WINDOWSsystem32
02/03/2007 11:27:24.255
02/03/2007 11:27:24.270 Enumerating applicable products for this patch
02/03/2007 11:27:24.395 Found Redist 2005 product definition
02/03/2007 11:27:24.755 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.755 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:24.755 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.755 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:26.411 Attempting to check IA 64 platform
02/03/2007 11:27:26.411 Result of IA64 check: 0
02/03/2007 11:27:26.411 Last error: 0
02/03/2007 11:27:26.426 Found Redist 2005 product definition
02/03/2007 11:27:26.583 Found Redist 2005 product definition
02/03/2007 11:27:26.833 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:26.833 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:26.833 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:26.833 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:28.567 Attempting to check IA 64 platform
02/03/2007 11:27:28.567 Result of IA64 check: 0
02/03/2007 11:27:28.567 Last error: 0
02/03/2007 11:27:28.583 Found SQL 2005 product definition
02/03/2007 11:39:12.833 Found OLAP Server 2005 product definition
02/03/2007 11:50:56.333 Found Notification Services 2005 product definition
02/03/2007 12:02:39.786 Found Report Server 2005 product definition
02/03/2007 12:14:23.051 Found DTS 2005 product definition
02/03/2007 12:26:06.801 Found SQL 2005 Tools product definition
02/03/2007 12:37:50.208 Found Redist 2005 product definition
02/03/2007 12:37:50.848 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:50.848 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:50.848 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:50.848 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:51.255 Attempting to check IA 64 platform
02/03/2007 12:37:51.255 Result of IA64 check: 0
02/03/2007 12:37:51.255 Last error: 0
02/03/2007 12:37:51.270 Found Redist 2005 product definition
02/03/2007 12:37:51.426 Found Redist 2005 product definition
02/03/2007 12:37:51.661 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:51.676 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:51.676 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:51.676 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:52.083 Attempting to check IA 64 platform
02/03/2007 12:37:52.083 Result of IA64 check: 0
02/03/2007 12:37:52.098 Last error: 0
02/03/2007 12:37:52.114 Found Redist 2005 product definition
02/03/2007 12:37:52.333 Found Redist 2005 product definition
02/03/2007 12:37:52.551 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:52.551 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:52.551 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:52.551 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:52.911 Attempting to check IA 64 platform
02/03/2007 12:37:52.926 Result of IA64 check: 0
02/03/2007 12:37:52.926 Last error: 0
02/03/2007 12:37:52.942 Found Redist 2005 product definition
02/03/2007 12:37:53.098 Found Redist 2005 product definition
02/03/2007 12:37:53.364 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:53.364 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:53.364 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:53.364 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:53.676 Attempting to check IA 64 platform
02/03/2007 12:37:53.676 Result of IA64 check: 0
02/03/2007 12:37:53.676 Last error: 0
02/03/2007 12:37:53.692 Found Redist 2005 product definition
02/03/2007 12:37:53.864 Product Details:
02/03/2007 12:37:53.880 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlncli.inf
02/03/2007 12:37:53.880 alwaysinstall = 1
02/03/2007 12:37:53.880 baselinebuild = 1399
02/03/2007 12:37:53.880 build = 2047
02/03/2007 12:37:53.880 description = SQL Server Native Client
02/03/2007 12:37:53.880 details = Service Pack for Microsoft SQL Server Native Client.
02/03/2007 12:37:53.880 kbarticle = KB913090
02/03/2007 12:37:53.880 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:53.880 lcid = 1033
02/03/2007 12:37:53.880 legalproductname = Microsoft SQL Native Client
02/03/2007 12:37:53.880 machinetype = x86
02/03/2007 12:37:53.880 package = HotFixSqlncli
02/03/2007 12:37:53.880 packagetype = Hotfix
02/03/2007 12:37:53.880 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
02/03/2007 12:37:53.880 productname = Redist9
02/03/2007 12:37:53.895 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:53.895 splevel = 0,1
02/03/2007 12:37:53.895 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:53.895 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
02/03/2007 12:37:53.895 version = 9
02/03/2007 12:37:53.895
02/03/2007 12:37:53.895 File Group Details: MSI
02/03/2007 12:37:53.895 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:53.895 File Details: sqlncli.msi
02/03/2007 12:37:53.895
02/03/2007 12:37:53.895 Instance Details: SQL Server Native Client
02/03/2007 12:37:53.895 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
02/03/2007 12:37:53.895
02/03/2007 12:37:53.895 Product Details:
02/03/2007 12:37:53.895 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlncli_x64.inf
02/03/2007 12:37:53.895 alwaysinstall = 1
02/03/2007 12:37:53.895 baselinebuild = 1399
02/03/2007 12:37:53.926 build = 2047
02/03/2007 12:37:53.926 description = SQL Server Native Client (64-bit)
02/03/2007 12:37:53.926 details = Service Pack for Microsoft SQL Server Native Client.
02/03/2007 12:37:53.926 kbarticle = KB913090
02/03/2007 12:37:53.926 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:53.926 lcid = 1033
02/03/2007 12:37:53.926 legalproductname = Microsoft SQL Native Client (64-bit)
02/03/2007 12:37:53.926 machinetype = x64
02/03/2007 12:37:53.926 package = HotFixSqlncli_x64
02/03/2007 12:37:53.926 packagetype = Hotfix
02/03/2007 12:37:53.942 productname = Redist9
02/03/2007 12:37:53.942 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:53.942 splevel = 0,1
02/03/2007 12:37:53.942 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:53.942 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
02/03/2007 12:37:53.942 version = 9
02/03/2007 12:37:53.942
02/03/2007 12:37:53.942 File Group Details: MSI
02/03/2007 12:37:53.942 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:53.942 File Details: sqlncli_x64.msi
02/03/2007 12:37:53.942
02/03/2007 12:37:53.942 Product Details:
02/03/2007 12:37:53.942 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlSupport.inf
02/03/2007 12:37:53.942 alwaysinstall = 1
02/03/2007 12:37:53.942 baselinebuild = 1399
02/03/2007 12:37:53.958 build = 2047
02/03/2007 12:37:53.958 description = Setup Support Files
02/03/2007 12:37:53.958 details = Service Pack for the SQL Server support files.
02/03/2007 12:37:53.958 kbarticle = KB913090
02/03/2007 12:37:53.958 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:53.958 keyqualifier = 1
02/03/2007 12:37:53.958 lcid = 1033
02/03/2007 12:37:53.958 legalproductname = SQL Server 2005 Setup Support Files
02/03/2007 12:37:53.958 machinetype = x86
02/03/2007 12:37:53.958 package = HotFixSqlSupport
02/03/2007 12:37:53.958 packagetype = Hotfix
02/03/2007 12:37:53.958 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
02/03/2007 12:37:53.958 productname = Redist9
02/03/2007 12:37:53.958 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:53.973 splevel = 0,1
02/03/2007 12:37:53.973 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:53.973 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
02/03/2007 12:37:53.973 version = 9
02/03/2007 12:37:53.973
02/03/2007 12:37:53.973 File Group Details: MSP
02/03/2007 12:37:53.973 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:53.973 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:53.989 File Details: SqlSupport.msp
02/03/2007 12:37:53.989
02/03/2007 12:37:53.989 Instance Details: Setup Support Files
02/03/2007 12:37:53.989 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
02/03/2007 12:37:53.989
02/03/2007 12:37:53.989 Product Details:
02/03/2007 12:37:53.989 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSQL.inf
02/03/2007 12:37:53.989 baselinebuild = 1399
02/03/2007 12:37:53.989 baselinebuildmax = 2047
02/03/2007 12:37:53.989 build = 2047
02/03/2007 12:37:53.989 description = Database Services
02/03/2007 12:37:53.989 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
02/03/2007 12:37:53.989 kbarticle = KB913090
02/03/2007 12:37:54.005 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.005 lcid = 1033
02/03/2007 12:37:54.005 legalproductname = SQL Server Database Services 2005
02/03/2007 12:37:54.005 machinetype = x86
02/03/2007 12:37:54.005 package = HotFixSQL
02/03/2007 12:37:54.005 packagetype = Hotfix
02/03/2007 12:37:54.005 productname = SQL9
02/03/2007 12:37:54.005 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.005 splevel = 0,1
02/03/2007 12:37:54.005 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.005 validateauthentication = true
02/03/2007 12:37:54.005 version = 9
02/03/2007 12:37:54.005
02/03/2007 12:37:54.005 File Group Details: MSP
02/03/2007 12:37:54.020 lockedfilecheck = 1
02/03/2007 12:37:54.020 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.020 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.020 File Details: sqlrun_sql.msp
02/03/2007 12:37:54.020
02/03/2007 12:37:54.020 Product Details:
02/03/2007 12:37:54.020 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixAS.inf
02/03/2007 12:37:54.020 baselinebuild = 1399
02/03/2007 12:37:54.020 baselinebuildmax = 2047
02/03/2007 12:37:54.020 build = 2047
02/03/2007 12:37:54.020 description = Analysis Services
02/03/2007 12:37:54.020 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
02/03/2007 12:37:54.020 kbarticle = KB913090
02/03/2007 12:37:54.020 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.036 lcid = 1033
02/03/2007 12:37:54.036 legalproductname = SQL Server Analysis Services 2005
02/03/2007 12:37:54.036 machinetype = x86
02/03/2007 12:37:54.036 package = HotFixAS
02/03/2007 12:37:54.036 packagetype = Hotfix
02/03/2007 12:37:54.036 productname = OLAP9
02/03/2007 12:37:54.036 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.036 splevel = 0,1
02/03/2007 12:37:54.036 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.036 version = 9
02/03/2007 12:37:54.036
02/03/2007 12:37:54.036 File Group Details: MSP
02/03/2007 12:37:54.036 lockedfilecheck = 1
02/03/2007 12:37:54.036 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.051 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.051 File Details: sqlrun_as.msp
02/03/2007 12:37:54.051
02/03/2007 12:37:54.051 Product Details:
02/03/2007 12:37:54.051 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixNS.inf
02/03/2007 12:37:54.051 baselinebuild = 1399
02/03/2007 12:37:54.051 baselinebuildmax = 2047
02/03/2007 12:37:54.051 build = 2047
02/03/2007 12:37:54.051 description = Notification Services
02/03/2007 12:37:54.051 details = Service Pack for Notification Services, a platform for developing and deploying applications that send personalized, timely notifications to a variety of devices or applications.
02/03/2007 12:37:54.051 kbarticle = KB913090
02/03/2007 12:37:54.051 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.051 lcid = 1033
02/03/2007 12:37:54.051 legalproductname = SQL Server Notification Services 2005 instances
02/03/2007 12:37:54.051 machinetype = x86
02/03/2007 12:37:54.067 package = HotFixNS
02/03/2007 12:37:54.067 packagetype = Hotfix
02/03/2007 12:37:54.067 productname = NS9
02/03/2007 12:37:54.067 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.067 splevel = 0,1
02/03/2007 12:37:54.067 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.067 version = 9
02/03/2007 12:37:54.067
02/03/2007 12:37:54.067 File Group Details: MSP
02/03/2007 12:37:54.067 lockedfilecheck = 1
02/03/2007 12:37:54.067 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.067 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.067 File Details: sqlrun_ns.msp
02/03/2007 12:37:54.067
02/03/2007 12:37:54.067 Product Details:
02/03/2007 12:37:54.067 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixRS.inf
02/03/2007 12:37:54.083 baselinebuild = 1399
02/03/2007 12:37:54.083 baselinebuildmax = 2047
02/03/2007 12:37:54.083 build = 2047
02/03/2007 12:37:54.083 description = Reporting Services
02/03/2007 12:37:54.083 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
02/03/2007 12:37:54.083 kbarticle = KB913090
02/03/2007 12:37:54.083 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.098 lcid = 1033
02/03/2007 12:37:54.098 legalproductname = SQL Server Reporting Services 2005
02/03/2007 12:37:54.098 machinetype = x86
02/03/2007 12:37:54.098 package = HotFixRS
02/03/2007 12:37:54.098 packagetype = Hotfix
02/03/2007 12:37:54.098 productname = RS9
02/03/2007 12:37:54.098 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.098 splevel = 0,1
02/03/2007 12:37:54.098 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.098 validateauthentication = 1
02/03/2007 12:37:54.098 version = 9
02/03/2007 12:37:54.098
02/03/2007 12:37:54.098 File Group Details: MSP
02/03/2007 12:37:54.098 lockedfilecheck = 1
02/03/2007 12:37:54.114 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.114 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.114 File Details: sqlrun_rs.msp
02/03/2007 12:37:54.114
02/03/2007 12:37:54.114 Product Details:
02/03/2007 12:37:54.114 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixDTS.inf
02/03/2007 12:37:54.114 baselinebuild = 1399
02/03/2007 12:37:54.114 baselinebuildmax = 2047
02/03/2007 12:37:54.114 build = 2047
02/03/2007 12:37:54.114 description = Integration Services
02/03/2007 12:37:54.114 details = Service Pack for Integration Services, a set of tools and programmable objects used to create and manage packages that extract, transform, and load data, as well as perform tasks.
02/03/2007 12:37:54.114 kbarticle = KB913090
02/03/2007 12:37:54.114 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.114 lcid = 1033
02/03/2007 12:37:54.114 legalproductname = SQL Server Integration Services 2005
02/03/2007 12:37:54.114 machinetype = x86
02/03/2007 12:37:54.114 package = HotFixDTS
02/03/2007 12:37:54.130 packagetype = Hotfix
02/03/2007 12:37:54.130 productname = DTS9
02/03/2007 12:37:54.130 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.130 splevel = 0,1
02/03/2007 12:37:54.130 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.130 version = 9
02/03/2007 12:37:54.130
02/03/2007 12:37:54.130 File Group Details: MSP
02/03/2007 12:37:54.130 lockedfilecheck = 1
02/03/2007 12:37:54.130 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.130 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.130 File Details: sqlrun_dts.msp
02/03/2007 12:37:54.130
02/03/2007 12:37:54.130 Product Details:
02/03/2007 12:37:54.130 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixTools.inf
02/03/2007 12:37:54.130 baselinebuild = 1399
02/03/2007 12:37:54.130 baselinebuildmax = 2047
02/03/2007 12:37:54.145 build = 2047
02/03/2007 12:37:54.145 description = Client Components
02/03/2007 12:37:54.145 details = Service Pack for the interactive management tools for running SQL Server, including SQL Server Configuration Manager, SQL Server Management Studio, SQL Profiler, and Replication Monitor.
02/03/2007 12:37:54.145 kbarticle = KB913090
02/03/2007 12:37:54.145 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.145 lcid = 1033
02/03/2007 12:37:54.145 legalproductname = SQL Server Tools and Workstation Components 2005
02/03/2007 12:37:54.145 machinetype = x86
02/03/2007 12:37:54.145 package = HotFixTools
02/03/2007 12:37:54.145 packagetype = Hotfix
02/03/2007 12:37:54.145 productname = SQLTools9
02/03/2007 12:37:54.145 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.145 splevel = 0,1
02/03/2007 12:37:54.145 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.145 version = 9
02/03/2007 12:37:54.145
02/03/2007 12:37:54.161 File Group Details: MSP
02/03/2007 12:37:54.161 lockedfilecheck = 1
02/03/2007 12:37:54.161 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.161 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.161 File Details: sqlrun_tools.msp
02/03/2007 12:37:54.161
02/03/2007 12:37:54.161 Product Details:
02/03/2007 12:37:54.161 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixMsxml6.inf
02/03/2007 12:37:54.161 baselinebuild = 1399
02/03/2007 12:37:54.161 build = 2047
02/03/2007 12:37:54.161 description = MSXML 6.0 Parser
02/03/2007 12:37:54.161 details = Service Pack for Microsoft XML 6.0 Parser.
02/03/2007 12:37:54.161 kbarticle = KB913090
02/03/2007 12:37:54.161 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.161 lcid = 1033
02/03/2007 12:37:54.161 legalproductname = MSXML 6.0 Parser
02/03/2007 12:37:54.161 machinetype = x86
02/03/2007 12:37:54.176 package = HotFixMsxml6
02/03/2007 12:37:54.176 packagetype = Hotfix
02/03/2007 12:37:54.176 productcode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
02/03/2007 12:37:54.176 productname = Redist9
02/03/2007 12:37:54.176 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.176 splevel = 0,1
02/03/2007 12:37:54.176 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.176 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
02/03/2007 12:37:54.176 version = 9
02/03/2007 12:37:54.176
02/03/2007 12:37:54.176 File Group Details: MSI
02/03/2007 12:37:54.176 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.176 File Details: msxml6.msi
02/03/2007 12:37:54.176
02/03/2007 12:37:54.176 Instance Details: MSXML 6.0 Parser
02/03/2007 12:37:54.176 productcode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
02/03/2007 12:37:54.176
02/03/2007 12:37:54.192 Product Details:
02/03/2007 12:37:54.192 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixMsxml6_x64.inf
02/03/2007 12:37:54.192 baselinebuild = 1399
02/03/2007 12:37:54.192 build = 2047
02/03/2007 12:37:54.192 description = MSXML 6.0 Parser (64-bit)
02/03/2007 12:37:54.192 details = Service Pack for Microsoft XML 6.0 Parser.
02/03/2007 12:37:54.192 kbarticle = KB913090
02/03/2007 12:37:54.192 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.192 lcid = 1033
02/03/2007 12:37:54.192 legalproductname = MSXML 6.0 Parser (64-bit)
02/03/2007 12:37:54.192 machinetype = x64
02/03/2007 12:37:54.192 package = HotFixMsxml6_x64
02/03/2007 12:37:54.192 packagetype = Hotfix
02/03/2007 12:37:54.192 productname = Redist9
02/03/2007 12:37:54.208 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.208 splevel = 0,1
02/03/2007 12:37:54.208 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.208 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
02/03/2007 12:37:54.208 version = 9
02/03/2007 12:37:54.208
02/03/2007 12:37:54.208 File Group Details: MSI
02/03/2007 12:37:54.208 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.208 File Details: msxml6_x64.msi
02/03/2007 12:37:54.208
02/03/2007 12:37:54.208 Product Details:
02/03/2007 12:37:54.208 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlxml4.inf
02/03/2007 12:37:54.208 baselinebuild = 1399
02/03/2007 12:37:54.208 build = 2047
02/03/2007 12:37:54.208 description = SQLXML4
02/03/2007 12:37:54.208 details = Service Pack for Microsoft SQLXML 4.0.
02/03/2007 12:37:54.223 kbarticle = KB913090
02/03/2007 12:37:54.223 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.223 lcid = 1033
02/03/2007 12:37:54.223 legalproductname = SQLXML4
02/03/2007 12:37:54.223 machinetype = x86
02/03/2007 12:37:54.223 package = HotFixSqlxml4
02/03/2007 12:37:54.223 packagetype = Hotfix
02/03/2007 12:37:54.223 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
02/03/2007 12:37:54.223 productname = Redist9
02/03/2007 12:37:54.223 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.223 splevel = 0,1
02/03/2007 12:37:54.223 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.223 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
02/03/2007 12:37:54.223 version = 9
02/03/2007 12:37:54.223
02/03/2007 12:37:54.223 File Group Details: MSI
02/03/2007 12:37:54.239 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.239 File Details: sqlxml4.msi
02/03/2007 12:37:54.239
02/03/2007 12:37:54.239 Instance Details: SQLXML4
02/03/2007 12:37:54.239 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
02/03/2007 12:37:54.239
02/03/2007 12:37:54.239 Product Details:
02/03/2007 12:37:54.239 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlxml4_x64.inf
02/03/2007 12:37:54.239 baselinebuild = 1399
02/03/2007 12:37:54.239 build = 2047
02/03/2007 12:37:54.239 description = SQLXML4 (64-bit)
02/03/2007 12:37:54.239 details = Service Pack for Microsoft SQLXML 4.0.
02/03/2007 12:37:54.239 kbarticle = KB913090
02/03/2007 12:37:54.239 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.239 lcid = 1033
02/03/2007 12:37:54.255 legalproductname = SQLXML4 (64-bit)
02/03/2007 12:37:54.255 machinetype = x64
02/03/2007 12:37:54.255 package = HotFixSqlxml4_x64
02/03/2007 12:37:54.255 packagetype = Hotfix
02/03/2007 12:37:54.255 productname = Redist9
02/03/2007 12:37:54.255 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.255 splevel = 0,1
02/03/2007 12:37:54.255 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.255 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
02/03/2007 12:37:54.255 version = 9
02/03/2007 12:37:54.255
02/03/2007 12:37:54.255 File Group Details: MSI
02/03/2007 12:37:54.255 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.255 File Details: sqlxml4_x64.msi
02/03/2007 12:37:54.270
02/03/2007 12:37:54.270 Product Details:
02/03/2007 12:37:54.270 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSQLServer2005_BC.inf
02/03/2007 12:37:54.270 baselinebuild = 1399
02/03/2007 12:37:54.270 build = 2047
02/03/2007 12:37:54.270 description = Backward Compatibility
02/03/2007 12:37:54.270 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
02/03/2007 12:37:54.270 kbarticle = KB913090
02/03/2007 12:37:54.270 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.270 lcid = 1033
02/03/2007 12:37:54.270 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
02/03/2007 12:37:54.270 machinetype = x86
02/03/2007 12:37:54.270 package = HotFixSQLServer2005_BC
02/03/2007 12:37:54.270 packagetype = Hotfix
02/03/2007 12:37:54.270 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
02/03/2007 12:37:54.286 productname = Redist9
02/03/2007 12:37:54.286 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.286 splevel = 0,1
02/03/2007 12:37:54.286 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.286 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
02/03/2007 12:37:54.286 version = 9
02/03/2007 12:37:54.286
02/03/2007 12:37:54.286 File Group Details: MSI
02/03/2007 12:37:54.286 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.286 File Details: SQLServer2005_BC.msi
02/03/2007 12:37:54.286
02/03/2007 12:37:54.286 Instance Details: Backward Compatibility
02/03/2007 12:37:54.286 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
02/03/2007 12:37:54.301
02/03/2007 12:37:54.301 Product Details:
02/03/2007 12:37:54.301 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSQLServer2005_BC_x64.inf
02/03/2007 12:37:54.301 baselinebuild = 1399
02/03/2007 12:37:54.301 build = 2047
02/03/2007 12:37:54.301 description = Backward Compatibility (64-bit)
02/03/2007 12:37:54.301 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
02/03/2007 12:37:54.301 kbarticle = KB913090
02/03/2007 12:37:54.301 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.301 lcid = 1033
02/03/2007 12:37:54.301 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
02/03/2007 12:37:54.301 machinetype = x64
02/03/2007 12:37:54.301 package = HotFixSQLServer2005_BC_x64
02/03/2007 12:37:54.301 packagetype = Hotfix
02/03/2007 12:37:54.301 productname = Redist9
02/03/2007 12:37:54.317 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.317 splevel = 0,1
02/03/2007 12:37:54.317 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.317 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
02/03/2007 12:37:54.317 version = 9
02/03/2007 12:37:54.317
02/03/2007 12:37:54.317 File Group Details: MSI
02/03/2007 12:37:54.317 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.317 File Details: SQLServer2005_BC_x64.msi
02/03/2007 12:37:54.317
02/03/2007 12:37:54.317 Product Details:
02/03/2007 12:37:54.317 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlWriter.inf
02/03/2007 12:37:54.317 baselinebuild = 1399
02/03/2007 12:37:54.317 build = 2047
02/03/2007 12:37:54.333 description = Microsoft SQL Server VSS Writer
02/03/2007 12:37:54.333 details = Service Pack for Microsoft SQL Server VSS Writer.
02/03/2007 12:37:54.333 kbarticle = KB913090
02/03/2007 12:37:54.333 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.333 lcid = 1033
02/03/2007 12:37:54.333 legalproductname = Microsoft SQL Server VSS Writer
02/03/2007 12:37:54.333 machinetype = x86
02/03/2007 12:37:54.333 package = HotFixSqlWriter
02/03/2007 12:37:54.333 packagetype = Hotfix
02/03/2007 12:37:54.333 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
02/03/2007 12:37:54.333 productname = Redist9
02/03/2007 12:37:54.333 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.333 splevel = 0,1
02/03/2007 12:37:54.333 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.333 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
02/03/2007 12:37:54.333 version = 9
02/03/2007 12:37:54.348
02/03/2007 12:37:54.348 File Group Details: MSI
02/03/2007 12:37:54.348 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.348 File Details: SqlWriter.msi
02/03/2007 12:37:54.348
02/03/2007 12:37:54.348 Instance Details: Microsoft SQL Server VSS Writer
02/03/2007 12:37:54.348 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
02/03/2007 12:37:54.348
02/03/2007 12:37:54.348 Product Details:
02/03/2007 12:37:54.348 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlWriter_x64.inf
02/03/2007 12:37:54.348 baselinebuild = 1399
02/03/2007 12:37:54.348 build = 2047
02/03/2007 12:37:54.348 description = Microsoft SQL Server VSS Writer (64-bit)
02/03/2007 12:37:54.348 details = Service Pack for Microsoft SQL Server VSS Writer.
02/03/2007 12:37:54.348 kbarticle = KB913090
02/03/2007 12:37:54.348 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.348 lcid = 1033
02/03/2007 12:37:54.348 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
02/03/2007 12:37:54.364 machinetype = x64
02/03/2007 12:37:54.364 package = HotFixSqlWriter_x64
02/03/2007 12:37:54.364 packagetype = Hotfix
02/03/2007 12:37:54.364 productname = Redist9
02/03/2007 12:37:54.364 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.364 splevel = 0,1
02/03/2007 12:37:54.364 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.364 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
02/03/2007 12:37:54.364 version = 9
02/03/2007 12:37:54.364
02/03/2007 12:37:54.364 File Group Details: MSI
02/03/2007 12:37:54.364 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.364 File Details: SqlWriter_x64.msi
02/03/2007 12:37:54.364
02/03/2007 15:33:40.192 Attempting to install product: Redist9
02/03/2007 15:33:45.817 Successfully installed product: Redist9
02/03/2007 15:33:45.817 Attempting to install product: Redist9
02/03/2007 15:33:58.051 Successfully installed product: Redist9
02/03/2007 15:33:58.083 Attempting to install product: Redist9
02/03/2007 15:34:00.020 Successfully installed product: Redist9
02/03/2007 15:34:00.051 Attempting to install product: Redist9
02/03/2007 15:34:03.130 Successfully installed product: Redist9
02/03/2007 15:34:03.192 Attempting to install product: Redist9
02/03/2007 15:34:05.770 Successfully installed product: Redist9
02/03/2007 15:34:05.801 Attempting to install product: Redist9
02/03/2007 15:34:08.489 Successfully installed product: Redist9
02/03/2007 15:34:08.520
02/03/2007 15:34:08.520 Product Status Summary:
02/03/2007 15:34:08.520 Product: SQL Server Native Client
02/03/2007 15:34:08.520 SQL Server Native Client (RTM ) - Success
02/03/2007 15:34:08.520
02/03/2007 15:34:08.520 Product: Setup Support Files
02/03/2007 15:34:08.520 Setup Support Files (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: MSXML 6.0 Parser
02/03/2007 15:34:08.536 MSXML 6.0 Parser (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: SQLXML4
02/03/2007 15:34:08.536 SQLXML4 (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: Backward Compatibility
02/03/2007 15:34:08.536 Backward Compatibility (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: Microsoft SQL Server VSS Writer
02/03/2007 15:34:08.536 Microsoft SQL Server VSS Writer (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.551 Hotfix package completed
02/03/2007 16:08:49.614 Hotfix package closed

View 2 Replies View Related

ORIGINAL SIN IN SQL 2005!

Jul 23, 2005

from the December 2004 _Redmond Magazine_, "Finding Gold in Yukon":http://redmondmag.com/columns/artic...ditorialsID=838"Developers will also pick up the usual new-version enhancements to T-SQL,including error handling, recursive queries, a ROW_NUMBER function, a PIVOTrelational operator and more."ROW_NUMBER???? What possible purpose could that have???

View 5 Replies View Related

Decrypted Value Is Different From The Original One

Mar 29, 2007

Hi,

I got an issue with encrypt and decrypt. I encrypted a data, say 'ok', then I decrypt the encrypted data, but what I got is not 'ok'. but if I encrypt a column, then after decryption, those data asr same with the original data in that column.



In my case,



...

create table mytable ( column Password varbinay(128) )

...

create symmetric key with certificate

...

OPEN SYMMETRIC KEY Sym_Key_01

DECRYPTION BY CERTIFICATE Cert;



UPDATE mytable

SET Password = EncryptByKey(Key_GUID('Password_01'),'ok')



select CONVERT(nvarchar, DecryptByKey(Password)) AS "Decrypted Password" from mytable



here, I didn't get the value 'ok' but a another wierd word (like a chinese word).



does someone know the reason?



Thanks,



Jone

View 1 Replies View Related

@original And Stored Procedures

Apr 24, 2006

When using @original_{0}, how does this work if you are using a stored procedure instead of inline SQL?  For example, if my update parameters are like this :
<UpdateParameters>
<asp:Parameter Type="String" Name="ProductType" />
<asp:Parameter Type="String" Name="OpportunityType" />
<asp:Parameter Type="Double" Name="Value" />
<asp:Parameter Type="String" Name="Probability" />
<asp:Parameter Type="Int32" Name="OpportunityID" />
</UpdateParameters>
 
And my stored procedure like this :
CREATE procedure dbo.UpdateOpportunity
( @ProductType int, @OpportunityType int, @Value money, @Probability int, @OpportunityID int)
as
update Opportunity set ProductType = @ProductType, OpportunityType = @OpportunityType,[Value] = @Value, Probability = @Probabilitywhere OpportunityID = @OpportunityID
Do I need to change both cases of @OpportunityID in my stored procedure to @original_OpportunityID for it to work?

View 1 Replies View Related

Original Data And Log Size

Sep 21, 2005

How can I find out the original size of the Data and Log files?TIARob

View 2 Replies View Related

Fuzzy Grouping Using Original Key

Nov 14, 2007

I managed to get fuzzy grouping working. The relevant output (_key_in and _key_out) are stored in a new table that is a copy of the old table + fuzzy grouping columns.

How do i get SSIS to store the _key_in and _key_out in the original table?
The new matching column _key_out refers to the new key: _key_in. How could i get SSIS translate that to a matching column that refers to my original key?

View 1 Replies View Related

Shrink Tempdb Below Original Size.

Feb 11, 2002

I have a tempdb that was created at 1Gig. I don't know why but I want to shrink it below the original creation size. Is there a way to shrink this file or create a new file and delete the old?

I have tried shinkfile and shrink database with no luck.

Thanks Jeff

View 6 Replies View Related

How To Keep Original Order When Querying A Table?

Sep 10, 2004

Hello, everyone:

I have a table like:

ColName
b
b
b
d
d
d
a
a
c
c
c

I use DISTINCT to filter duplicated row. I want to get the return by original order like:
b
d
a
c

However, SQL Server re-order it if using DISTINCT and return like:
a
b
c
d

Can any one have the idea to handle that? Thanks

ZYT

View 4 Replies View Related

Different Results Same Query Between Original And Copied Db

Sep 29, 2005

Hi all,

I restored a backup of a database running SQL Server in W2K to my own laptop (Windows XP) for report testing pourposes. The restore worked perfectly, but when I ran the store procedure that returns my "report" set I noticed that several of the fields within the result set are different, the number of rows and customers are a perfect match to the production report. The fields that are different are calculated fields that invoque a user defined function, which again are exactly the same on both databases. I tried dropping the stored procedure and the 4 functions and recreating them again but I get the same results, the number of rows, the customers and all "non" function calculated fields are perfect, only the fields calculated with the functions are wrong.

Has anybody seen this behavior?

Thanks for your help

Luis Torres

View 4 Replies View Related

Get Original Login Name After Context Switch

Jan 22, 2008

Does anyone know how to get the original Login name, while a context switch is in effect.. For example during the use of Original login to SQL is Wayne
Then Execute as Test

Now I need to know that Wayne is the Login and not Test

none of the standard things work, they all use the current context (suser_sname, etc)... Books online includes the following text

SYSTEM_USER returns the name of the currently executing context. If the EXECUTE AS statement has been used to switch context, SYSTEM_USER will return the name of the impersonated context. Use the LOGIN() function to return the name of the original login during impersonation.


But I cannot find any function called LOGIN() anywhere?

Suggestions>?

View 4 Replies View Related

How Can I Use SELECT DISTINCT And Maintain The Original Order

Apr 26, 2007

Say I have a result set with two fields numbers and letters.

1 A3 A1 B2 B


 The result set is ordered by the letters column. How can I select the distinct numbers from the result set but maintain the current order? When I tryselect distinct Number from MyResultSet

it will reorder the new result set by the Number field and return

123

 However, I'd like maintain the Letter order and return

132

View 1 Replies View Related

Copying A Request From Draft To Original Tables

Jan 6, 2014

I have been using the below query to copy a record of data that exists in several draft tables to the original tables. how do i change this query such that i can input multiple records at one time so multiple records get copied to original tables from the draft tables

At this time when i feed mutiple requestids to my query it simply errors out

SET NOCOUNT ON
GO
DECLARE @oldrequestid varchar(50),@newrequestid varchar(50)
DECLARE db_cursor CURSOR FOR
SELECT RequestId from report_request_draft where requestid in (320762)

[Code] ....

View 6 Replies View Related

Altering Views Will It Reflect The Original Tables.....

Aug 17, 2005

phanindra writes "Hello all,

I am phanindra....

I have a question sir/madam,

suppose we have an view named "VIEW" for a table named "TABLE"

will the values in the TABLE alter if we change it in VIEW

thanks in advance
phanindra"

View 1 Replies View Related

Linked Reports Lose Original Layout

Nov 16, 2005

I created a linked report and I see that the original height and width settings which were set for landscape have changed into portrait:

View 7 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved