How can I convert datetime to number of minutes

I have a column in a table that stores the number of hours a task took to do. The column TaskDuration is a datetime datatype. I need to convert the hours to something that can be summed. Does anyone how this can be done? I tried CONVERT(nvarchar(5), tblTasks.TaskDuration, 108) but of course the nvarchar(5) cannot be summed. Maybe there is a way to convert the time portion to minutes and divide it by 60, anyway if someone can offer some help I appreciate it.

Try something like this

(datepart(hh, tblTasks.TaskDuration) * 60) + datepart(mm, tblTasks.TaskDuration)

|||

I tried this and it will return the number of minutes for the hours; however, the Parenthesis will not stay around the (datepart(hh, tblTasks.TaskDuration) * 60) in the view. So the (mm) are not being added.

Well it is adding time for the minutes but 30 is calculating to 10, so 03:30 is returning 190 minutes and it should be 210.

Any ideas?

|||I gave you the wrong datepart signifier, try datepart(n, tblTasks.TaskDuration)|||

Ok, so now that I have the number of minutes, can I convert this to hours and minutes. What I mean is the reporting tool needs a numeric column to sum on, so 03:15 needs to be 3.25.

Is this possible?

|||

I tried and it looks to be returning the correct format. If you have any comments, I appreciate them.

CONVERT (FLOAT, DATEPART(hh, dbo.tblVolunteerTasks.VTaskDuration) * 60 + DATEPART(n, dbo.tblVolunteerTasks.VTaskDuration)) / 60

How can i check file size equal zero or not with scrip task ?

Dear all,

Could you tell me which code of vb scrip that i can check file size as follow ?

Dim FSO, Fyl
Set FSO = CreateObject("Scripting.FileSystemObject")
Set Fyl = CreateObject("File")

If FSO.FileExists("C:\temp\lcbseg.log") Then
Set Fyl = FSO.GetFile("C:\temp\lcbseg.log")
If Fyl.Size > 0 Then
Main = DTSStepScriptResult_ExecuteTask
Else
Main = DTSStepScriptResult_DontExecuteTask
End If
End if

Thanks

Best regards,

Kusuma

You need to do this in two stages, since there is no workflow script anymore.

Here is a sample for nthe Script Task. It uses a variable called FileSize, into which it stores the file size, surpirse!

Public Sub Main()

Dim info As System.IO.FileInfo = New System.IO.FileInfo("C:\File.txt")

Dim variables As New Variables

Dts.VariableDispenser.LockOneForWrite("FileSize", variables)

variables(0).Value = info.Length

variables.Unlock()

Dts.TaskResult = Dts.Results.Success

End Sub

Now you would use a precedenc constraint from the sript task to the next task, but be sure to include an expression. Double-click to get the UI, and try and expression like this-

@.[Use::FileSize] > 0

|||

I've tried to follow your code DarrenSQLIS, but it has the error "FileSize" for read/write access with error 0xC0010001 "The variable cannot be found. how can i fix this problem?

So i've some questions where can i declare FileSize variable. It's on SSIS menu=> varible,isn't it? and what's type of FileSize variable. For next what's property of expresstion to use @.[Use::FileSize] > 0.

Many thanks.

Best Regards,

Kusuma

|||I know you asked how do check for a file size equal to non zero in a script task, which can certainly be done with a script task as Darren illustrates.

Another technique for checking file existence and size simultaneously is use of "WMI Data Reader Task" with WQL. Use of the WMI data reader task will require a WMI connection manager, which is quick simple to configure, and available through the task's UI.

For example, the following WQL query checks for the existence and size of c:\boot.ini. simultaneously.

Select FileSize From CIM_Datafile Where Name = 'C:\\boot.ini'

After the WMI task, a downstream task can constrained by the following expression, which evaluates to true only for an existent, non zero byte file.

@.FileLength > "0\r\n"

NOTE, in this case, @.FileLength is a string variable, unlike the script task case. The reason the variable for file size is a string rather than a uint64 is that the WMI Data Reader task writes string and/or object variable types. The backslash is a special character to WMI, and as such is doubled up (escaped) in the WQL query.|||

KUS wrote:

Dear all,

Could you tell me which code of vb scrip that i can check file size as follow ?

Dim FSO, Fyl
Set FSO = CreateObject("Scripting.FileSystemObject")
Set Fyl = CreateObject("File")

If FSO.FileExists("C:\temp\lcbseg.log") Then
Set Fyl = FSO.GetFile("C:\temp\lcbseg.log")
If Fyl.Size > 0 Then
Main = DTSStepScriptResult_ExecuteTask
Else
Main = DTSStepScriptResult_DontExecuteTask
End If
End if

Thanks

Best regards,

Kusuma

|||Hey hi . Could you tell me a VB code so that I can check a file size in a folder and mail to abc@.xyz.com if the file size is less than 10MB?|||First of all read the code above, it shows you how to get the file size into a variable. Then use an SMTP Send Mail Task to send the mail. To restrict the email to only files < 10MB, add an expression on the precendence constraint between the Script Task and Mail Task, @.Var < 10000

How can i check file size equal zero or not with scrip task ?

Dear all,

Could you tell me which code of vb scrip that i can check file size as follow ?

Dim FSO, Fyl
Set FSO = CreateObject("Scripting.FileSystemObject")
Set Fyl = CreateObject("File")

If FSO.FileExists("C:\temp\lcbseg.log") Then
Set Fyl = FSO.GetFile("C:\temp\lcbseg.log")
If Fyl.Size > 0 Then
Main = DTSStepScriptResult_ExecuteTask
Else
Main = DTSStepScriptResult_DontExecuteTask
End If
End if

Thanks

Best regards,

Kusuma

You need to do this in two stages, since there is no workflow script anymore.

Here is a sample for nthe Script Task. It uses a variable called FileSize, into which it stores the file size, surpirse!

Public Sub Main()

Dim info As System.IO.FileInfo = New System.IO.FileInfo("C:\File.txt")

Dim variables As New Variables

Dts.VariableDispenser.LockOneForWrite("FileSize", variables)

variables(0).Value = info.Length

variables.Unlock()

Dts.TaskResult = Dts.Results.Success

End Sub

Now you would use a precedenc constraint from the sript task to the next task, but be sure to include an expression. Double-click to get the UI, and try and expression like this-

@.[Use::FileSize] > 0

|||

I've tried to follow your code DarrenSQLIS, but it has the error "FileSize" for read/write access with error 0xC0010001 "The variable cannot be found. how can i fix this problem?

So i've some questions where can i declare FileSize variable. It's on SSIS menu=> varible,isn't it? and what's type of FileSize variable. For next what's property of expresstion to use @.[Use::FileSize] > 0.

Many thanks.

Best Regards,

Kusuma

|||I know you asked how do check for a file size equal to non zero in a script task, which can certainly be done with a script task as Darren illustrates.

Another technique for checking file existence and size simultaneously is use of "WMI Data Reader Task" with WQL. Use of the WMI data reader task will require a WMI connection manager, which is quick simple to configure, and available through the task's UI.

For example, the following WQL query checks for the existence and size of c:\boot.ini. simultaneously.

Select FileSize From CIM_Datafile Where Name = 'C:\\boot.ini'

After the WMI task, a downstream task can constrained by the following expression, which evaluates to true only for an existent, non zero byte file.

@.FileLength > "0\r\n"

NOTE, in this case, @.FileLength is a string variable, unlike the script task case. The reason the variable for file size is a string rather than a uint64 is that the WMI Data Reader task writes string and/or object variable types. The backslash is a special character to WMI, and as such is doubled up (escaped) in the WQL query.
|||

KUS wrote:

Dear all,

Could you tell me which code of vb scrip that i can check file size as follow ?

Dim FSO, Fyl
Set FSO = CreateObject("Scripting.FileSystemObject")
Set Fyl = CreateObject("File")

If FSO.FileExists("C:\temp\lcbseg.log") Then
Set Fyl = FSO.GetFile("C:\temp\lcbseg.log")
If Fyl.Size > 0 Then
Main = DTSStepScriptResult_ExecuteTask
Else
Main = DTSStepScriptResult_DontExecuteTask
End If
End if

Thanks

Best regards,

Kusuma

|||Hey hi . Could you tell me a VB code so that I can check a file size in a folder and mail to abc@.xyz.com if the file size is less than 10MB?|||First of all read the code above, it shows you how to get the file size into a variable. Then use an SMTP Send Mail Task to send the mail. To restrict the email to only files < 10MB, add an expression on the precendence constraint between the Script Task and Mail Task, @.Var < 10000

How can I append children to parents in a SSIS data flow task?

I need to extract data to send to an external agency in their supplied format. The data is normalised in our system in a one to many relationship. The external agency needs it denormalised.

In our system, the parent p has p_id, p_attribute_1, p_attribute_2, p_attribute_3 and the child has c_id, c_attribute_a, c_attribute_b, c_parent_id_fk

The external agency can only use a delimited file looking like

p_id, p_attribute_1, p_attribute_2, p_attribute_3, c1_attribute_a, c1_attribute_b, c2_attribute_a, c2_attribute_b, ...., cn_attribute_a, cn_attribute_b

where n is the number of children a parent may have. Each parent can have 0 or more children - typically between 1 and 20.

How can I achieve this using SSIS? In the past I have used custom built VB apps with the ADO SHAPE command but this is not ideal as I have to rebuild each time to alter the selection criteria and and VB is not a good SQL tool.

You can use the pivot transform to move rows to columns, but it doesn't handle a variable number of columns very well. I'd try creating a script component that outputs the set of children for a parent as one long string. Then you can append it to the parent value.|||

jwelch wrote:

You can use the pivot transform to move rows to columns, but it doesn't handle a variable number of columns very well. I'd try creating a script component that outputs the set of children for a parent as one long string. Then you can append it to the parent value.

I agree with John.

The way I would approach this is to join the parent and child records together in a SQL statement so you have a row for each parent/child combination. Use this statement in the Source of a Data Flow and run the rows into an asynchronous script transformation component. You'll write code in the script to denormalize the incoming rows into a single output row for each parent. SSIS won't adapt to having an arbitrary number of child columns and I don't think there is a need for it. The output of the script should be a single column (string if it can fit, otherwise text) that is already delimited and can go directly into a flat file destination.

So the script is the only tricky part. It will look at the p_id on each row it receives to determine if this is the same parent as the last input row. If it isn't, then it will write the output row it was working on for the previous p_id to the output and start a new one by appending the p_id and parent and child attributes to a string. If it is the same p_id, it will continue to append the child attributes until it sees the next p_id or the last row.

Something like this oughta do it:

Code Snippet

Public Class ScriptMain
Inherits UserComponent

Dim last_pid As Integer = -1
Dim current_row As StringBuilder = Nothing

Public Overrides Sub FinishOutputs()
' the input is finished, flush the current row
WriteRow()
End Sub

Public Sub WriteRow()
If Not current_row Is Nothing Then
With Output0Buffer
.AddRow()
.OutputLine = current_row.ToString()
' if we use a dt_text column
'.OutputLine.AddBlobData(ASCIIEncoding.ASCII.GetBytes(current_row.ToString()))
End With
End If

End Sub

Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)
'
' Add your code here
'
If Row.pid <> last_pid Then

' this is a new p_id starting, write the previous one to the output
WriteRow()

' remember this pid for future rows
last_pid = Row.pid

' create new buffer
current_row = New StringBuilder()
' append parent attributes
With current_row
.Append(Row.pid.ToString())
.Append(",")
.Append(Row.pattribute1)
.Append(",")
.Append(Row.pattribute2)
.Append(",")
.Append(Row.pattribute3)
End With
End If

' append child attributes
With current_row
.Append(",")
.Append(Row.cattributea)
.Append(",")
.Append(Row.cattributeb)
End With
End Sub

End Class

Note: The JOIN should group all of the parents together, but just in case you should probably throw an ORDER BY p_id in for that SQL statement.

|||

Phew. I went out 2 hours ago with the express purpose of coming back and answering this but John and Jay have beaten me to it

I was going to suggest exactly what Jay has said. Its kind of hobson's choice on this one - the metadata is unknown at design-time therefore you HAVE to have a single column with all the values concatenated. The fact that you are outputting to a file means that it really doesn't matter anyway.

I would add that this would be a great candidate for a custom component if you can be bothered to build it.

-Jamie

How automatically process a Cube periodically

Good morning,

I have create a solution with two cubes, but I want that these cubes process automatically, with a batch or a windows task.

But I don't find how to do this. Do I need to create a script or something like that.

I'm totally lost.

Thanks for your help,

You can use SQL Server Integration Services (search for Processing Objects Using Integration Services in BOL), or you could also Analysis Managment Objects (AMO).
|||

I see this in another article, but I don't found Analysis Services Processing Task.

Is it install with sql server 2005 or not?

Do you have an example that I can see, please or some indications?

Thanks,

|||

Titou wrote:

I see this in another article, but I don't found Analysis Services Processing Task.

Is it install with sql server 2005 or not?

Do you have an example that I can see, please or some indications?

Thanks,

I forgot to note that i work with sql server and analysis services 2005

|||In BI Development Studio, create a new SSIS task. In the Control Flow tab, first add a connection manager for your Analysis Services database (bottom tab, right-click), then drag an Analysis Services Processing Task from the toolbar on the left (the tab may be minimized). In the task, set which objects you want processed.

Save locally, and then go to the file menu and do a Save a copy of... And save it to your SQL Server database that Analysis Services is sitting on.

Go to Management studio and connect to the database (not Analysis Services). Go to the SQL Server Agent and right-click on jobs. Add a new job. In the job type, select SSIS job, select the SSIS package that you just created, and voila! You have a job on the database that you can now set to occur periodically.

It's a little confusing at first, but once it gets going, it's pretty simple. After your first one, you'll probably want to go back and add logging, too...

-Doug
|||

I success in the creation of the SSIS task, but when i go to Sql Server, I can't find my file an I can't had or browse to find it, could you help me?

Thanks

|||

Many options are available. Two immediately come to mind. Both involve scripting. When you have the processing dialog box open (just before you process) you will notice a box at the top that says "Script". It will take whatever you are about to do for processing and create an XMLA script a background window.

Once you have the script then:

1) Create a SQL Agent job and a step within it. There is a new option in the step that allows it to run an Analysis Services Command -- this is the XMLA script that you created above. Simply paste it into the step and then schedule the SQL Agent job as needed.

2) Create an SSIS package and select an Analysis Services Execute DDL task. Insert the XMLA script into it and it will execute it as a step in the SSIS package.

Alternatively, you could create an SSIS package and use the Analsyis Services Processing task and specify what object you wish to process. That works well also.

Finally, coming in WR2 of the Samples MSI in April will be a new utility called ascmd (which is patterened after sqlcmd) that allows you to execute XMLA scripts (and MDX queries) from the command line. If you are interested in getting a pre-release version of it, contact me (dwickert@.microsoft.com) and I will point you to the right folks.

Hope that helps.

_-_-_ Dave

|||

Hi.

Thanks, DWBI_Doug! Worked perfectly!

Regards

Kjetil

|||Thank You DWBI_Doug, You saved my day. i ow you one.

How automatically process a Cube periodically

Good morning,

I have create a solution with two cubes, but I want that these cubes process automatically, with a batch or a windows task.

But I don't find how to do this. Do I need to create a script or something like that.

I'm totally lost.

Thanks for your help,

You can use SQL Server Integration Services (search for Processing

Objects Using Integration Services in BOL), or you could also Analysis

Managment Objects (AMO).|||

I see this in another article, but I don't found Analysis Services Processing Task.

Is it install with sql server 2005 or not?

Do you have an example that I can see, please or some indications?

Thanks,

|||

Titou wrote:

I see this in another article, but I don't found Analysis Services Processing Task.

Is it install with sql server 2005 or not?

Do you have an example that I can see, please or some indications?

Thanks,

I forgot to note that i work with sql server and analysis services 2005

|||In BI Development Studio, create a new SSIS task. In the Control Flow tab, first add a connection manager for your Analysis Services database (bottom tab, right-click), then drag an Analysis Services Processing Task from the toolbar on the left (the tab may be minimized). In the task, set which objects you want processed.

Save locally, and then go to the file menu and do a Save a copy of... And save it to your SQL Server database that Analysis Services is sitting on.

Go to Management studio and connect to the database (not Analysis Services). Go to the SQL Server Agent and right-click on jobs. Add a new job. In the job type, select SSIS job, select the SSIS package that you just created, and voila! You have a job on the database that you can now set to occur periodically.

It's a little confusing at first, but once it gets going, it's pretty simple. After your first one, you'll probably want to go back and add logging, too...

-Doug|||

I success in the creation of the SSIS task, but when i go to Sql Server, I can't find my file an I can't had or browse to find it, could you help me?

Thanks

|||

Many options are available. Two immediately come to mind. Both involve scripting. When you have the processing dialog box open (just before you process) you will notice a box at the top that says "Script". It will take whatever you are about to do for processing and create an XMLA script a background window.

Once you have the script then:

1) Create a SQL Agent job and a step within it. There is a new option in the step that allows it to run an Analysis Services Command -- this is the XMLA script that you created above. Simply paste it into the step and then schedule the SQL Agent job as needed.

2) Create an SSIS package and select an Analysis Services Execute DDL task. Insert the XMLA script into it and it will execute it as a step in the SSIS package.

Alternatively, you could create an SSIS package and use the Analsyis Services Processing task and specify what object you wish to process. That works well also.

Finally, coming in WR2 of the Samples MSI in April will be a new utility called ascmd (which is patterened after sqlcmd) that allows you to execute XMLA scripts (and MDX queries) from the command line. If you are interested in getting a pre-release version of it, contact me (dwickert@.microsoft.com) and I will point you to the right folks.

Hope that helps.

_-_-_ Dave

|||

Hi.

Thanks, DWBI_Doug! Worked perfectly!

Regards

Kjetil

How automatically process a Cube periodically

Good morning,

I have create a solution with two cubes, but I want that these cubes process automatically, with a batch or a windows task.

But I don't find how to do this. Do I need to create a script or something like that.

I'm totally lost.

Thanks for your help,

You can use SQL Server Integration Services (search for Processing Objects Using Integration Services in BOL), or you could also Analysis Managment Objects (AMO).
|||

I see this in another article, but I don't found Analysis Services Processing Task.

Is it install with sql server 2005 or not?

Do you have an example that I can see, please or some indications?

Thanks,

|||

Titou wrote:

I see this in another article, but I don't found Analysis Services Processing Task.

Is it install with sql server 2005 or not?

Do you have an example that I can see, please or some indications?

Thanks,

I forgot to note that i work with sql server and analysis services 2005

|||In BI Development Studio, create a new SSIS task. In the Control Flow tab, first add a connection manager for your Analysis Services database (bottom tab, right-click), then drag an Analysis Services Processing Task from the toolbar on the left (the tab may be minimized). In the task, set which objects you want processed.

Save locally, and then go to the file menu and do a Save a copy of... And save it to your SQL Server database that Analysis Services is sitting on.

Go to Management studio and connect to the database (not Analysis Services). Go to the SQL Server Agent and right-click on jobs. Add a new job. In the job type, select SSIS job, select the SSIS package that you just created, and voila! You have a job on the database that you can now set to occur periodically.

It's a little confusing at first, but once it gets going, it's pretty simple. After your first one, you'll probably want to go back and add logging, too...

-Doug
|||

I success in the creation of the SSIS task, but when i go to Sql Server, I can't find my file an I can't had or browse to find it, could you help me?

Thanks

|||

Many options are available. Two immediately come to mind. Both involve scripting. When you have the processing dialog box open (just before you process) you will notice a box at the top that says "Script". It will take whatever you are about to do for processing and create an XMLA script a background window.

Once you have the script then:

1) Create a SQL Agent job and a step within it. There is a new option in the step that allows it to run an Analysis Services Command -- this is the XMLA script that you created above. Simply paste it into the step and then schedule the SQL Agent job as needed.

2) Create an SSIS package and select an Analysis Services Execute DDL task. Insert the XMLA script into it and it will execute it as a step in the SSIS package.

Alternatively, you could create an SSIS package and use the Analsyis Services Processing task and specify what object you wish to process. That works well also.

Finally, coming in WR2 of the Samples MSI in April will be a new utility called ascmd (which is patterened after sqlcmd) that allows you to execute XMLA scripts (and MDX queries) from the command line. If you are interested in getting a pre-release version of it, contact me (dwickert@.microsoft.com) and I will point you to the right folks.

Hope that helps.

_-_-_ Dave

|||

Hi.

Thanks, DWBI_Doug! Worked perfectly!

Regards

Kjetil

|||Thank You DWBI_Doug, You saved my day. i ow you one.

Hotfix 934459.

Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
Now I have the error described in Fix 934459 (The Check Database Integrity
task and the Execute T-SQL Statement task in a maintenance plan may lose
database context in certain circumstances ), but my build 9.0.3054 doesn't
seem to be in the affected ones..
Should I install the hotfix' Which one'
This are the two available
If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
http://support.microsoft.com/kb/934459/
If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
http://support.microsoft.com/kb/934458/
Thanks.You should get 3200 or, better yet, 3215 instead.
9.0.3200:
http://support.microsoft.com/kb/941450
9.0.3215:
http://support.microsoft.com/kb/943656
"averied" <averied@.discussions.microsoft.com> wrote in message
news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> Now I have the error described in Fix 934459 (The Check Database Integrity
> task and the Execute T-SQL Statement task in a maintenance plan may lose
> database context in certain circumstances ), but my build 9.0.3054 doesn't
> seem to be in the affected ones..
> Should I install the hotfix' Which one'
> This are the two available
> If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> http://support.microsoft.com/kb/934459/
> If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> http://support.microsoft.com/kb/934458/
>
> Thanks.
>|||I installed the Cumulative update package 4 for SQL Server 2005 Service Pack
2 and rebooted my machine, yet my version still shows 9.00.3042. The
installation appeared to function properly w/ no errors. How can I tell that
this hot fix did indeed install?
Cordially,
Mark Boettcher
PS, I have just now requested the hotfix for 3215 and should get it tomorrow.
"Aaron Bertrand [SQL Server MVP]" wrote:
> You should get 3200 or, better yet, 3215 instead.
> 9.0.3200:
> http://support.microsoft.com/kb/941450
> 9.0.3215:
> http://support.microsoft.com/kb/943656
>
>
> "averied" <averied@.discussions.microsoft.com> wrote in message
> news:BE40CE77-C3A5-4FF3-AEFA-477950543802@.microsoft.com...
> > Hi, I have a sql 2005 with Sp2 applied. My Build is 9.0.3054
> >
> > Now I have the error described in Fix 934459 (The Check Database Integrity
> > task and the Execute T-SQL Statement task in a maintenance plan may lose
> > database context in certain circumstances ), but my build 9.0.3054 doesn't
> > seem to be in the affected ones..
> >
> > Should I install the hotfix' Which one'
> >
> > This are the two available
> >
> > If you are running a build of SQL Server 2005 SP2 between 3150 and 3158
> > http://support.microsoft.com/kb/934459/
> >
> > If you are running any build of SQL Server 2005 SP2 between 3042 and 3053
> > http://support.microsoft.com/kb/934458/
> >
> >
> > Thanks.
> >
>
>|||>I installed the Cumulative update package 4 for SQL Server 2005 Service
>Pack
> 2 and rebooted my machine, yet my version still shows 9.00.3042.
Where/how are you checking "my version"?
A|||In server management studio, I right-clicked on registered server and found
it under properties. If not there, how should I display the sql version?
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I installed the Cumulative update package 4 for SQL Server 2005 Service
> >Pack
> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
> Where/how are you checking "my version"?
> A
>|||That is the version for the tools (Management Studio). Open a query window
connected to the server you updated, and then run:
SELECT @.@.VERSION;
"Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
> In server management studio, I right-clicked on registered server and
> found
> it under properties. If not there, how should I display the sql version?
> Mark
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> >I installed the Cumulative update package 4 for SQL Server 2005 Service
>> >Pack
>> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
>> Where/how are you checking "my version"?
>> A|||Since I installed Cumulative update package 4, I requested, received, and
installed Cumulative update package 5. Using the Select @.@.Version command
returns 9.00.3215 now. I assume Cumulative update package 5 includes the
changes in Cumulative update package 4 - correct? After I installed package
4, I did do a select @.@.version and received 9.00.3042 which is why I
questioned whether the package really did install.
Mark
"Aaron Bertrand [SQL Server MVP]" wrote:
> That is the version for the tools (Management Studio). Open a query window
> connected to the server you updated, and then run:
> SELECT @.@.VERSION;
>
> "Mark Boettcher" <MarkBoettcher@.discussions.microsoft.com> wrote in message
> news:71D22B9E-5D0B-4B79-8E59-B9067A58EC2C@.microsoft.com...
> > In server management studio, I right-clicked on registered server and
> > found
> > it under properties. If not there, how should I display the sql version?
> >
> > Mark
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> >I installed the Cumulative update package 4 for SQL Server 2005 Service
> >> >Pack
> >> > 2 and rebooted my machine, yet my version still shows 9.00.3042.
> >>
> >> Where/how are you checking "my version"?
> >>
> >> A
> >>
>|||> returns 9.00.3215 now. I assume Cumulative update package 5 includes the
> changes in Cumulative update package 4 - correct?
Yes, each cumulative update page states that cumulative updates are
cumulative -- that's why they're named as such. :-)
> After I installed package
> 4, I did do a select @.@.version and received 9.00.3042
Then the install didn't succeed, or you ran SELECT @.@.VERSION against the
wrong server.
A