Showing posts with label posting. Show all posts
Showing posts with label posting. Show all posts

Tuesday, March 20, 2012

BUG: 3rd Request: Series style function BUG in SP1

I'll try posting this again, since it garnered no reply either of the
times that I posted it. Is my post being ignored for some reason?
Greetings.
I found an odd issue when working with a series style in a line chart
in SP1. I was using my own function to determine the color of the
series. So I entered =Code.PickColor(Fields!ResultSort.Value) for the
formula. My code is this:
Public Function PickColor(iResultSort As Integer) As String
Dim sColor As String
Select Case iResultSort
Case 0: sColor = "#000000" ' Black, Full
Case 3: sColor = "#800000" ' Brown, Avg
End Select
PickColor = sColor
End Function
The ResultSort field is defined in SQL as an integer. What happened
on the chart is that the data line was drawn in the color expected,
but from the end of the line to the x axis, a black line was drawn.
If I change the code to use a String instead:
Public Function PickColor(sResultSort As String) As String
Dim sColor As String
Select Case sResultSort
Case "0": sColor = "#000000" ' Black, Full
Case "3": sColor = "#800000" ' Brown, Avg
End Select
PickColor = sColor
End Function
then it draws as expected.
I would sort of like to know if there is something that I am missing
here that causes it to behave like this or if there is an issue with
the functionality.
I have the rdl and sample data as xml attached here, and can email
screenshots or whatever if desired.
Thanks.
Dale.
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Chart Name="chart1">
<ThreeDProperties>
<Rotation>30</Rotation>
<Inclination>30</Inclination>
<Shading>Simple</Shading>
<WallThickness>50</WallThickness>
</ThreeDProperties>
<Style>
<BackgroundColor>White</BackgroundColor>
</Style>
<Legend>
<Visible>true</Visible>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
<Position>RightCenter</Position>
</Legend>
<Palette>Default</Palette>
<ChartData>
<ChartSeries>
<DataPoints>
<DataPoint>
<DataValues>
<DataValue>
<Value>=Fields!DPC.Value</Value>
</DataValue>
</DataValues>
<DataLabel />
<Style>
<BorderColor>
<Default>=Code.PickColor( Fields!ResultSort.Value
)</Default>
</BorderColor>
</Style>
<Marker>
<Type>Auto</Type>
<Size>6pt</Size>
</Marker>
</DataPoint>
</DataPoints>
</ChartSeries>
</ChartData>
<CategoryAxis>
<Axis>
<Title />
<MajorGridLines>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
</MajorGridLines>
<MinorGridLines>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
</MinorGridLines>
<MajorTickMarks>Outside</MajorTickMarks>
<Min>0</Min>
<Visible>true</Visible>
</Axis>
</CategoryAxis>
<DataSetName>DataSet1</DataSetName>
<PointWidth>0</PointWidth>
<Type>Line</Type>
<Title />
<CategoryGroupings>
<CategoryGrouping>
<DynamicCategories>
<Grouping Name="chart1_CategoryGroup1">
<GroupExpressions>
<GroupExpression>=Fields!DaysAfter.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Label>=Fields!DaysAfter.Value</Label>
</DynamicCategories>
</CategoryGrouping>
</CategoryGroupings>
<SeriesGroupings>
<SeriesGrouping>
<DynamicSeries>
<Grouping Name="chart1_SeriesGroup1">
<GroupExpressions>
<GroupExpression>=Fields!ResultSort.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Label>=Fields!ResultSort.Value</Label>
</DynamicSeries>
</SeriesGrouping>
</SeriesGroupings>
<Subtype>Plain</Subtype>
<PlotArea>
<Style>
<BackgroundColor>White</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
</PlotArea>
<ValueAxis>
<Axis>
<Title />
<MajorGridLines>
<ShowGridLines>true</ShowGridLines>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
</MajorGridLines>
<MinorGridLines>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
</MinorGridLines>
<MajorTickMarks>Outside</MajorTickMarks>
<Min>0</Min>
<Margin>true</Margin>
<Visible>true</Visible>
<Scalar>true</Scalar>
</Axis>
</ValueAxis>
</Chart>
</ReportItems>
<Style />
<Height>5.125in</Height>
</Body>
<TopMargin>1in</TopMargin>
<DataSources>
<DataSource Name="List_History ReadOnly">
<rd:DataSourceID>f2bd5a97-e7bc-444d-a3f9-b6f33e8fb5a7</rd:DataSourceID>
<DataSourceReference>List_History ReadOnly</DataSourceReference>
</DataSource>
</DataSources>
<Code>Public Function PickColor(iResultSort As Integer) As String
Dim sColor As String
Select Case iResultSort
Case 0: sColor = "#000000" ' Black, Full
Case 3: sColor = "#800000" ' Brown, Avg
End Select
PickColor = sColor
End Function
Public Function PickLineWidth(sResultSort As String) As String
Dim sWidth As String
Select Case sResultSort
Case 0: sWidth = "1.5pt" ' Thicker
Case Else: sWidth = "1pt" ' Normal
End Select
End Function
</Code>
<Width>6.625in</Width>
<DataSets>
<DataSet Name="DataSet1">
<Fields>
<Field Name="DaysAfter">
<DataField>DaysAfter</DataField>
<rd:TypeName>System.Int32</rd:TypeName>
</Field>
<Field Name="ResultSort">
<DataField>ResultSort</DataField>
<rd:TypeName>System.Int32</rd:TypeName>
</Field>
<Field Name="DPC">
<DataField>DPC</DataField>
<rd:TypeName>System.Decimal</rd:TypeName>
</Field>
</Fields>
<Query>
<DataSourceName>List_History ReadOnly</DataSourceName>
<CommandText>SELECT * FROM dbo.Dale</CommandText>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
</Query>
</DataSet>
</DataSets>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<Description />
<rd:ReportID>1f236bff-9e92-4d02-a9b0-b41e2d7f6950</rd:ReportID>
<BottomMargin>1in</BottomMargin>
<Language>en-US</Language>
</Report>
<SampleData>
<DataRow DaysAfter="34" ResultSort="0" DPC="4.07"/><DataRow
DaysAfter="65" ResultSort="0" DPC="4.07"/><DataRow DaysAfter="95"
ResultSort="0" DPC="4.07"/><DataRow DaysAfter="126" ResultSort="0"
DPC="4.07"/><DataRow DaysAfter="156" ResultSort="0"
DPC="4.07"/><DataRow DaysAfter="187" ResultSort="0"
DPC="4.07"/><DataRow DaysAfter="218" ResultSort="0"
DPC="4.07"/><DataRow DaysAfter="248" ResultSort="0"
DPC="4.07"/><DataRow DaysAfter="279" ResultSort="0"
DPC="4.07"/><DataRow ResultSort="0" DPC="4.07"/><DataRow
DaysAfter="34" ResultSort="1" DPC="3.06"/><DataRow DaysAfter="65"
ResultSort="1" DPC="3.06"/><DataRow DaysAfter="95" ResultSort="1"
DPC="3.06"/><DataRow DaysAfter="126" ResultSort="1"
DPC="3.06"/><DataRow DaysAfter="156" ResultSort="1"
DPC="3.06"/><DataRow DaysAfter="187" ResultSort="1"
DPC="3.06"/><DataRow DaysAfter="218" ResultSort="1"
DPC="3.06"/><DataRow DaysAfter="248" ResultSort="1"
DPC="3.06"/><DataRow DaysAfter="279" ResultSort="1"
DPC="3.06"/><DataRow ResultSort="1" DPC="3.06"/><DataRow
DaysAfter="34" ResultSort="3" DPC="8.59"/><DataRow DaysAfter="65"
ResultSort="3" DPC="11.32"/><DataRow DaysAfter="95" ResultSort="3"
DPC="14.78"/><DataRow DaysAfter="126" ResultSort="3"
DPC="15.42"/><DataRow DaysAfter="156" ResultSort="3"
DPC="16.04"/><DataRow DaysAfter="187" ResultSort="3"
DPC="16.33"/></SampleData>I think there might be several issues here:
* you use DaysAfter as category grouping. Your data has NULLs for DaysAfter
in some of the rows - is this intended?
* the category grouping does not use a sort expression (to sort DaysAfter
ascending) - add a sort expression identical on the category group
expression: =Fields!DaysAfter.Value
* A series grouping is present in the chart - therefore instead of using
=Code.PickColor( Fields!ResultSort.Value), you should use this expression:
=Code.PickColor(First(Fields!ResultSort.Value, "chart1_SeriesGroup1")
The important part is the aggregate scope which has to be identical to the
chart series grouping name. Just using the First aggregate without the scope
will give you incorrect results, because the aggregate will be just scoped
for every chart datapoint (and therefore null if you don't have any
datapoints for a particular series group / category group combination).
Finally, I'm not sure but you might run into an issue in the chart control
we have identified recently and for which we have provided a fix. The fix is
related to NULL datapoints in line charts. Details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;883675. Please feel
free to contact PSS and refer them to KB 883675.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Shrumishi" <shrumishi@.yahoo.com> wrote in message
news:4380bfd3.0409170628.7daebbd3@.posting.google.com...
> I'll try posting this again, since it garnered no reply either of the
> times that I posted it. Is my post being ignored for some reason?
> Greetings.
> I found an odd issue when working with a series style in a line chart
> in SP1. I was using my own function to determine the color of the
> series. So I entered =Code.PickColor(Fields!ResultSort.Value) for the
> formula. My code is this:
> Public Function PickColor(iResultSort As Integer) As String
> Dim sColor As String
> Select Case iResultSort
> Case 0: sColor = "#000000" ' Black, Full
> Case 3: sColor = "#800000" ' Brown, Avg
> End Select
> PickColor = sColor
> End Function
> The ResultSort field is defined in SQL as an integer. What happened
> on the chart is that the data line was drawn in the color expected,
> but from the end of the line to the x axis, a black line was drawn.
> If I change the code to use a String instead:
> Public Function PickColor(sResultSort As String) As String
> Dim sColor As String
> Select Case sResultSort
> Case "0": sColor = "#000000" ' Black, Full
> Case "3": sColor = "#800000" ' Brown, Avg
> End Select
> PickColor = sColor
> End Function
> then it draws as expected.
> I would sort of like to know if there is something that I am missing
> here that causes it to behave like this or if there is an issue with
> the functionality.
> I have the rdl and sample data as xml attached here, and can email
> screenshots or whatever if desired.
> Thanks.
> Dale.
> <?xml version="1.0" encoding="utf-8"?>
> <Report
>
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefini
tion"
>
xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Chart Name="chart1">
> <ThreeDProperties>
> <Rotation>30</Rotation>
> <Inclination>30</Inclination>
> <Shading>Simple</Shading>
> <WallThickness>50</WallThickness>
> </ThreeDProperties>
> <Style>
> <BackgroundColor>White</BackgroundColor>
> </Style>
> <Legend>
> <Visible>true</Visible>
> <Style>
> <BorderStyle>
> <Default>Solid</Default>
> </BorderStyle>
> </Style>
> <Position>RightCenter</Position>
> </Legend>
> <Palette>Default</Palette>
> <ChartData>
> <ChartSeries>
> <DataPoints>
> <DataPoint>
> <DataValues>
> <DataValue>
> <Value>=Fields!DPC.Value</Value>
> </DataValue>
> </DataValues>
> <DataLabel />
> <Style>
> <BorderColor>
> <Default>=Code.PickColor( Fields!ResultSort.Value
> )</Default>
> </BorderColor>
> </Style>
> <Marker>
> <Type>Auto</Type>
> <Size>6pt</Size>
> </Marker>
> </DataPoint>
> </DataPoints>
> </ChartSeries>
> </ChartData>
> <CategoryAxis>
> <Axis>
> <Title />
> <MajorGridLines>
> <Style>
> <BorderStyle>
> <Default>Solid</Default>
> </BorderStyle>
> </Style>
> </MajorGridLines>
> <MinorGridLines>
> <Style>
> <BorderStyle>
> <Default>Solid</Default>
> </BorderStyle>
> </Style>
> </MinorGridLines>
> <MajorTickMarks>Outside</MajorTickMarks>
> <Min>0</Min>
> <Visible>true</Visible>
> </Axis>
> </CategoryAxis>
> <DataSetName>DataSet1</DataSetName>
> <PointWidth>0</PointWidth>
> <Type>Line</Type>
> <Title />
> <CategoryGroupings>
> <CategoryGrouping>
> <DynamicCategories>
> <Grouping Name="chart1_CategoryGroup1">
> <GroupExpressions>
>
<GroupExpression>=Fields!DaysAfter.Value</GroupExpression>
> </GroupExpressions>
> </Grouping>
> <Label>=Fields!DaysAfter.Value</Label>
> </DynamicCategories>
> </CategoryGrouping>
> </CategoryGroupings>
> <SeriesGroupings>
> <SeriesGrouping>
> <DynamicSeries>
> <Grouping Name="chart1_SeriesGroup1">
> <GroupExpressions>
>
<GroupExpression>=Fields!ResultSort.Value</GroupExpression>
> </GroupExpressions>
> </Grouping>
> <Label>=Fields!ResultSort.Value</Label>
> </DynamicSeries>
> </SeriesGrouping>
> </SeriesGroupings>
> <Subtype>Plain</Subtype>
> <PlotArea>
> <Style>
> <BackgroundColor>White</BackgroundColor>
> <BorderStyle>
> <Default>Solid</Default>
> </BorderStyle>
> </Style>
> </PlotArea>
> <ValueAxis>
> <Axis>
> <Title />
> <MajorGridLines>
> <ShowGridLines>true</ShowGridLines>
> <Style>
> <BorderStyle>
> <Default>Solid</Default>
> </BorderStyle>
> </Style>
> </MajorGridLines>
> <MinorGridLines>
> <Style>
> <BorderStyle>
> <Default>Solid</Default>
> </BorderStyle>
> </Style>
> </MinorGridLines>
> <MajorTickMarks>Outside</MajorTickMarks>
> <Min>0</Min>
> <Margin>true</Margin>
> <Visible>true</Visible>
> <Scalar>true</Scalar>
> </Axis>
> </ValueAxis>
> </Chart>
> </ReportItems>
> <Style />
> <Height>5.125in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <DataSources>
> <DataSource Name="List_History ReadOnly">
>
<rd:DataSourceID>f2bd5a97-e7bc-444d-a3f9-b6f33e8fb5a7</rd:DataSourceID>
> <DataSourceReference>List_History ReadOnly</DataSourceReference>
> </DataSource>
> </DataSources>
> <Code>Public Function PickColor(iResultSort As Integer) As String
> Dim sColor As String
> Select Case iResultSort
> Case 0: sColor = "#000000" ' Black, Full
> Case 3: sColor = "#800000" ' Brown, Avg
> End Select
> PickColor = sColor
> End Function
> Public Function PickLineWidth(sResultSort As String) As String
> Dim sWidth As String
> Select Case sResultSort
> Case 0: sWidth = "1.5pt" ' Thicker
> Case Else: sWidth = "1pt" ' Normal
> End Select
> End Function
> </Code>
> <Width>6.625in</Width>
> <DataSets>
> <DataSet Name="DataSet1">
> <Fields>
> <Field Name="DaysAfter">
> <DataField>DaysAfter</DataField>
> <rd:TypeName>System.Int32</rd:TypeName>
> </Field>
> <Field Name="ResultSort">
> <DataField>ResultSort</DataField>
> <rd:TypeName>System.Int32</rd:TypeName>
> </Field>
> <Field Name="DPC">
> <DataField>DPC</DataField>
> <rd:TypeName>System.Decimal</rd:TypeName>
> </Field>
> </Fields>
> <Query>
> <DataSourceName>List_History ReadOnly</DataSourceName>
> <CommandText>SELECT * FROM dbo.Dale</CommandText>
> <rd:UseGenericDesigner>true</rd:UseGenericDesigner>
> </Query>
> </DataSet>
> </DataSets>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <Description />
> <rd:ReportID>1f236bff-9e92-4d02-a9b0-b41e2d7f6950</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <Language>en-US</Language>
> </Report>
> <SampleData>
> <DataRow DaysAfter="34" ResultSort="0" DPC="4.07"/><DataRow
> DaysAfter="65" ResultSort="0" DPC="4.07"/><DataRow DaysAfter="95"
> ResultSort="0" DPC="4.07"/><DataRow DaysAfter="126" ResultSort="0"
> DPC="4.07"/><DataRow DaysAfter="156" ResultSort="0"
> DPC="4.07"/><DataRow DaysAfter="187" ResultSort="0"
> DPC="4.07"/><DataRow DaysAfter="218" ResultSort="0"
> DPC="4.07"/><DataRow DaysAfter="248" ResultSort="0"
> DPC="4.07"/><DataRow DaysAfter="279" ResultSort="0"
> DPC="4.07"/><DataRow ResultSort="0" DPC="4.07"/><DataRow
> DaysAfter="34" ResultSort="1" DPC="3.06"/><DataRow DaysAfter="65"
> ResultSort="1" DPC="3.06"/><DataRow DaysAfter="95" ResultSort="1"
> DPC="3.06"/><DataRow DaysAfter="126" ResultSort="1"
> DPC="3.06"/><DataRow DaysAfter="156" ResultSort="1"
> DPC="3.06"/><DataRow DaysAfter="187" ResultSort="1"
> DPC="3.06"/><DataRow DaysAfter="218" ResultSort="1"
> DPC="3.06"/><DataRow DaysAfter="248" ResultSort="1"
> DPC="3.06"/><DataRow DaysAfter="279" ResultSort="1"
> DPC="3.06"/><DataRow ResultSort="1" DPC="3.06"/><DataRow
> DaysAfter="34" ResultSort="3" DPC="8.59"/><DataRow DaysAfter="65"
> ResultSort="3" DPC="11.32"/><DataRow DaysAfter="95" ResultSort="3"
> DPC="14.78"/><DataRow DaysAfter="126" ResultSort="3"
> DPC="15.42"/><DataRow DaysAfter="156" ResultSort="3"
> DPC="16.04"/><DataRow DaysAfter="187" ResultSort="3"
> DPC="16.33"/></SampleData>sql

Thursday, March 8, 2012

Bug in Ent Mgr Maintenance Plan Wizard if MSDE vs SQL

I have seen this "bug" many times personally, but cannot seem to find any posting on the Internet about it. I have many customers using MSDE
The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise Manager when connecting to MSDE.
Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT include licence for Enterprize Manager (EM)... but any technician who does have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access Licence) does have Enterprize Manag
er and can connect and manage MSDE and SQL engines/servers equally well.
Consider http://support.microsoft.com/default...22&Product=sql Here we see substantiation that one "can" use EM and Maintenance Plans on MSDE, albeit that you had better be the latest Service Pack since the sqlmaint feature was over
looked in the original release to market.
The bug I am reporting is with the "Remove after X Weeks/Days" option for Database Backup, Transaction Backup (and Log text files). This is important because unless you can also choose to do so, one will end up filling the hard disk with far too many SQL
dumps.
If connected to an SQL server... the option works fine. If connected to an MSDE, the option fails to provie the drop-down for days/weeks and the resulting job created has bugs in the command line options of the job step which one must then go and manuall
y tweak to be correct (never report a bug without a workaround eh? ;-P)
John,
As far as im aware this happens because the maintenance wizard
(sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
instance registry location.
(I would maybe do this on a test machine first if possible or make sure you
have backups)
So firstly make sure the following backup folder path exists , if not create
it :
c:\program files\microsoft sql server\<MSDE instance>\Backup.
Then in regedit:
HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
there should be a BackupDirectory string value , the value data should be
the physical path to the backup folder in our case c:\program
files\microsoft sql server\<MSDE instance>\Backup.
HTH
Dylan
"John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
> I have seen this "bug" many times personally, but cannot seem to find any
posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
include licence for Enterprize Manager (EM)... but any technician who does
have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
Licence) does have Enterprize Manager and can connect and manage MSDE and
SQL engines/servers equally well.
> Consider
http://support.microsoft.com/default...22&Product=sql
Here we see substantiation that one "can" use EM and Maintenance Plans on
MSDE, albeit that you had better be the latest Service Pack since the
sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
Database Backup, Transaction Backup (and Log text files). This is important
because unless you can also choose to do so, one will end up filling the
hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to
an MSDE, the option fails to provie the drop-down for days/weeks and the
resulting job created has bugs in the command line options of the job step
which one must then go and manually tweak to be correct (never report a bug
without a workaround eh? ;-P)
|||Thanks for the thought. No that's not what I mean (see my additional post
in next thread). About the backup folder here is what I did discover the
hard way..
When creating the Maintenance Plan...if one chooses "use the default backup
directory" then it seems to work, and the (first) backup will create the
folder path even if it did not yet exist. However if you specify a "use
this directory" to backup to... then I have found that folder you specify
had better exist already because the backup job will fail rather than create
it. So there's a little idiosyncracy for ya. (I have not experienced the
issue you mention, but perhaps that is an issue if the SQL is installed as a
"named" instance of SQL instead of the default/single instance of SQL? in
which case thank you for the additional tweaks)
John D. Sullivan
ABELSoft Corporation
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:OQXmdsjaEHA.3596@.tk2msftngp13.phx.gbl...
> John,
> As far as im aware this happens because the maintenance wizard
> (sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
> instance registry location.
> (I would maybe do this on a test machine first if possible or make sure
you
> have backups)
> So firstly make sure the following backup folder path exists , if not
create[vbcol=seagreen]
> it :
> c:\program files\microsoft sql server\<MSDE instance>\Backup.
> Then in regedit:
> HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
> there should be a BackupDirectory string value , the value data should be
> the physical path to the backup folder in our case c:\program
> files\microsoft sql server\<MSDE instance>\Backup.
> HTH
> Dylan
>
>
> "John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
> message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
any[vbcol=seagreen]
> posting on the Internet about it. I have many customers using MSDE
Enterprise[vbcol=seagreen]
> Manager when connecting to MSDE.
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> http://support.microsoft.com/default...22&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
for
> Database Backup, Transaction Backup (and Log text files). This is
important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> an MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a
bug
> without a workaround eh? ;-P)
>

Bug in Ent Mgr Maintenance Plan Wizard if MSDE vs SQL

I have seen this "bug" many times personally, but cannot seem to find any posting on the Internet about it. I have many customers using MSDE
The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise Manager when connecting to MSDE.
Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT include licence for Enterprize Manager (EM)... but any technician who does have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access Licence) does have Enterprize Manag
er and can connect and manage MSDE and SQL engines/servers equally well.
Consider http://support.microsoft.com/default...22&Product=sql Here we see substantiation that one "can" use EM and Maintenance Plans on MSDE, albeit that you had better be the latest Service Pack since the sqlmaint feature was over
looked in the original release to market.
The bug I am reporting is with the "Remove after X Weeks/Days" option for Database Backup, Transaction Backup (and Log text files). This is important because unless you can also choose to do so, one will end up filling the hard disk with far too many SQL
dumps.
If connected to an SQL server... the option works fine. If connected to an MSDE, the option fails to provie the drop-down for days/weeks and the resulting job created has bugs in the command line options of the job step which one must then go and manuall
y tweak to be correct (never report a bug without a workaround eh? ;-P)
John,
As far as im aware this happens because the maintenance wizard
(sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
instance registry location.
(I would maybe do this on a test machine first if possible or make sure you
have backups)
So firstly make sure the following backup folder path exists , if not create
it :
c:\program files\microsoft sql server\<MSDE instance>\Backup.
Then in regedit:
HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
there should be a BackupDirectory string value , the value data should be
the physical path to the backup folder in our case c:\program
files\microsoft sql server\<MSDE instance>\Backup.
HTH
Dylan
"John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
> I have seen this "bug" many times personally, but cannot seem to find any
posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
include licence for Enterprize Manager (EM)... but any technician who does
have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
Licence) does have Enterprize Manager and can connect and manage MSDE and
SQL engines/servers equally well.
> Consider
http://support.microsoft.com/default...22&Product=sql
Here we see substantiation that one "can" use EM and Maintenance Plans on
MSDE, albeit that you had better be the latest Service Pack since the
sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
Database Backup, Transaction Backup (and Log text files). This is important
because unless you can also choose to do so, one will end up filling the
hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to
an MSDE, the option fails to provie the drop-down for days/weeks and the
resulting job created has bugs in the command line options of the job step
which one must then go and manually tweak to be correct (never report a bug
without a workaround eh? ;-P)
|||Thanks for the thought. No that's not what I mean (see my additional post
in next thread). About the backup folder here is what I did discover the
hard way..
When creating the Maintenance Plan...if one chooses "use the default backup
directory" then it seems to work, and the (first) backup will create the
folder path even if it did not yet exist. However if you specify a "use
this directory" to backup to... then I have found that folder you specify
had better exist already because the backup job will fail rather than create
it. So there's a little idiosyncracy for ya. (I have not experienced the
issue you mention, but perhaps that is an issue if the SQL is installed as a
"named" instance of SQL instead of the default/single instance of SQL? in
which case thank you for the additional tweaks)
John D. Sullivan
ABELSoft Corporation
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:OQXmdsjaEHA.3596@.tk2msftngp13.phx.gbl...
> John,
> As far as im aware this happens because the maintenance wizard
> (sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
> instance registry location.
> (I would maybe do this on a test machine first if possible or make sure
you
> have backups)
> So firstly make sure the following backup folder path exists , if not
create[vbcol=seagreen]
> it :
> c:\program files\microsoft sql server\<MSDE instance>\Backup.
> Then in regedit:
> HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
> there should be a BackupDirectory string value , the value data should be
> the physical path to the backup folder in our case c:\program
> files\microsoft sql server\<MSDE instance>\Backup.
> HTH
> Dylan
>
>
> "John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
> message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
any[vbcol=seagreen]
> posting on the Internet about it. I have many customers using MSDE
Enterprise[vbcol=seagreen]
> Manager when connecting to MSDE.
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> http://support.microsoft.com/default...22&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
for
> Database Backup, Transaction Backup (and Log text files). This is
important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> an MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a
bug
> without a workaround eh? ;-P)
>

Wednesday, March 7, 2012

Bug in Database Maintenance Plans Enterprise Manager and MSDE v SQL

I have seen this "bug" many times personally, but cannot seem to find any
posting on the Internet about it. I have many customers using MSDE
The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
Manager when connecting to MSDE.
Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
include licence for Enterprize Manager (EM)... but any technician who does
have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
Licence) does have Enterprize Manager and can connect and manage MSDE and
SQL engines/servers equally well.
Consider
http://support.microsoft.com/default.aspx?scid=kb;en-us;295022&Product=sql
Here we see substantiation that one "can" use EM and Maintenance Plans on
MSDE, albeit that you had better be the latest Service Pack since the
sqlmaint feature was overlooked in the original release to market.
The bug I am reporting is with the "Remove after X Weeks/Days" option for
Database Backup, Transaction Backup (and Log text files). This is important
because unless you can also choose to do so, one will end up filling the
hard disk with far too many SQL dumps.
If connected to an SQL server... the option works fine. If connected to an
MSDE, the option fails to provie the drop-down for days/weeks and the
resulting job created has bugs in the command line options of the job step
which one must then go and manually tweak to be correct (never report a bug
without a workaround eh? ;-P)
John D. Sullivan
ABELSoft Corporation
(email address munged)This is not just an MSDE problem. We have had problems with out Enterprise
version not deleting backups. Never resolved it. Wrote scripts to delete
files.
Bob
SuccessWare Software
"John D. Sullivan" <noone@.nothing.com> wrote in message
news:uGWJDreaEHA.3716@.TK2MSFTNGP11.phx.gbl...
> I have seen this "bug" many times personally, but cannot seem to find any
> posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
> Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> Consider
> http://support.microsoft.com/default.aspx?scid=kb;en-us;295022&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
> Database Backup, Transaction Backup (and Log text files). This is
important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to
an
> MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a
bug
> without a workaround eh? ;-P)
> John D. Sullivan
> ABELSoft Corporation
> (email address munged)
>|||John,
Yep, this is a bug. Have a look at these articles:
BUG: Sqlmaint Does Not Delete Expired Backup Files on Windows 95, 98 or
ME Computers
http://support.microsoft.com/?id=278667
BUG: Cannot Edit or Delete Database Maintenance Plan on MSDE Installation
http://support.microsoft.com/?id=247879
FIX: SQLMaint.exe Sets Database Status Incorrectly
http://support.microsoft.com/?id=276234
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
John D. Sullivan wrote:
> I have seen this "bug" many times personally, but cannot seem to find any
> posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
> Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> Consider
> http://support.microsoft.com/default.aspx?scid=kb;en-us;295022&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
> Database Backup, Transaction Backup (and Log text files). This is important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to an
> MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a bug
> without a workaround eh? ;-P)
> John D. Sullivan
> ABELSoft Corporation
> (email address munged)
>|||Excellent information that is very relevant. Thank you Mark. It is very
useful to know that the sqlmaint.exe tool fails to delete the backups on 9x
platform. While it is true that SQL 7 has no Database Maintenance Plan
branch under Management in the Enterprise Manager and therefore connecting
to an SQL 2k it is not possible to edit or delete a "plan" but only the
Job/steps... the problem I am citing is a bit different.
What I mean to say is that when creating a new Database Maintenance Plan
using the GUI Enterprise Manager (2000) that takes one through a multi-step
"wizard", it is possible to "check box" that you wish to "Remove files older
than" but the boxes for quantity and units (e.g. 4, Weeks) are fine if
manageing an SQL 2000 edition other than MSDE but when MSDE 2000 (all
service packs) is the engine/server the GUI of the Maintenance Plan Wizard
shows blanks for the qty/units of days/weeks to remove old files.
Workaround: if you go ahead and checkbox to remove old files, manually fill
in a number for qty (you cannot fill in units) and continue through the
wizard it WILL create the Job/step(s)... however the job step that EXECUTEs
xp_sqlmaint (notice this is the extended stored procedure equivalent of
command prompt sqlmaint.exe) will have slight syntax errors in the argument
list. The resulting Job fails to execute. Obviously the -DelBkUps switch
will not have the correct <time value> after it... if you filled in 77 it
will say 77 but has no WEEKS or DAYS or what have you. One has to edit the
job step and manually tweak the command line arguments until they are
correct, then it will work.
By the way, I find viewing the results of job and job steps pretty much
useless. You might see an error number you can lookup. One ends up copying
the entire command and pasting and running it as a query to find out exactly
where/why it is failing. Instead, I find it very useful to check the option
in the Maintenance Plan to write report to a text file..because the error
message(s) in there are far more detailed and useful.
John D. Sullivan
ABELSoft Corporation
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OAZ539laEHA.2908@.TK2MSFTNGP10.phx.gbl...
> John,
> Yep, this is a bug. Have a look at these articles:
> BUG: Sqlmaint Does Not Delete Expired Backup Files on Windows 95, 98 or
> ME Computers
> http://support.microsoft.com/?id=278667
> BUG: Cannot Edit or Delete Database Maintenance Plan on MSDE Installation
> http://support.microsoft.com/?id=247879
> FIX: SQLMaint.exe Sets Database Status Incorrectly
> http://support.microsoft.com/?id=276234
>
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> John D. Sullivan wrote:
> > I have seen this "bug" many times personally, but cannot seem to find
any
> > posting on the Internet about it. I have many customers using MSDE
> >
> > The bug is with the Database Maintenance Plans of Microsoft SQL
Enterprise
> > Manager when connecting to MSDE.
> >
> > Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
> > include licence for Enterprize Manager (EM)... but any technician who
does
> > have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client
Access
> > Licence) does have Enterprize Manager and can connect and manage MSDE
and
> > SQL engines/servers equally well.
> >
> > Consider
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;295022&Product=sql
> > Here we see substantiation that one "can" use EM and Maintenance Plans
on
> > MSDE, albeit that you had better be the latest Service Pack since the
> > sqlmaint feature was overlooked in the original release to market.
> >
> > The bug I am reporting is with the "Remove after X Weeks/Days" option
for
> > Database Backup, Transaction Backup (and Log text files). This is
important
> > because unless you can also choose to do so, one will end up filling the
> > hard disk with far too many SQL dumps.
> >
> > If connected to an SQL server... the option works fine. If connected to
an
> > MSDE, the option fails to provie the drop-down for days/weeks and the
> > resulting job created has bugs in the command line options of the job
step
> > which one must then go and manually tweak to be correct (never report a
bug
> > without a workaround eh? ;-P)
> >
> > John D. Sullivan
> > ABELSoft Corporation
> > (email address munged)
> >
> >|||John,
Yep it's annoying. I try not to use maintenance plans for my routine
tasks as I like to have the flexibility of creating my own maintenance
jobs. This may be a workaround you might wish to consider.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
John D. Sullivan wrote:
> Excellent information that is very relevant. Thank you Mark. It is very
> useful to know that the sqlmaint.exe tool fails to delete the backups on 9x
> platform. While it is true that SQL 7 has no Database Maintenance Plan
> branch under Management in the Enterprise Manager and therefore connecting
> to an SQL 2k it is not possible to edit or delete a "plan" but only the
> Job/steps... the problem I am citing is a bit different.
> What I mean to say is that when creating a new Database Maintenance Plan
> using the GUI Enterprise Manager (2000) that takes one through a multi-step
> "wizard", it is possible to "check box" that you wish to "Remove files older
> than" but the boxes for quantity and units (e.g. 4, Weeks) are fine if
> manageing an SQL 2000 edition other than MSDE but when MSDE 2000 (all
> service packs) is the engine/server the GUI of the Maintenance Plan Wizard
> shows blanks for the qty/units of days/weeks to remove old files.
> Workaround: if you go ahead and checkbox to remove old files, manually fill
> in a number for qty (you cannot fill in units) and continue through the
> wizard it WILL create the Job/step(s)... however the job step that EXECUTEs
> xp_sqlmaint (notice this is the extended stored procedure equivalent of
> command prompt sqlmaint.exe) will have slight syntax errors in the argument
> list. The resulting Job fails to execute. Obviously the -DelBkUps switch
> will not have the correct <time value> after it... if you filled in 77 it
> will say 77 but has no WEEKS or DAYS or what have you. One has to edit the
> job step and manually tweak the command line arguments until they are
> correct, then it will work.
> By the way, I find viewing the results of job and job steps pretty much
> useless. You might see an error number you can lookup. One ends up copying
> the entire command and pasting and running it as a query to find out exactly
> where/why it is failing. Instead, I find it very useful to check the option
> in the Maintenance Plan to write report to a text file..because the error
> message(s) in there are far more detailed and useful.
> John D. Sullivan
> ABELSoft Corporation
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:OAZ539laEHA.2908@.TK2MSFTNGP10.phx.gbl...
>>John,
>>Yep, this is a bug. Have a look at these articles:
>>BUG: Sqlmaint Does Not Delete Expired Backup Files on Windows 95, 98 or
>>ME Computers
>>http://support.microsoft.com/?id=278667
>>BUG: Cannot Edit or Delete Database Maintenance Plan on MSDE Installation
>>http://support.microsoft.com/?id=247879
>>FIX: SQLMaint.exe Sets Database Status Incorrectly
>>http://support.microsoft.com/?id=276234
>>
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602.html
>>
>>John D. Sullivan wrote:
>>I have seen this "bug" many times personally, but cannot seem to find
> any
>>posting on the Internet about it. I have many customers using MSDE
>>The bug is with the Database Maintenance Plans of Microsoft SQL
> Enterprise
>>Manager when connecting to MSDE.
>>Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
>>include licence for Enterprize Manager (EM)... but any technician who
> does
>>have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client
> Access
>>Licence) does have Enterprize Manager and can connect and manage MSDE
> and
>>SQL engines/servers equally well.
>>Consider
> http://support.microsoft.com/default.aspx?scid=kb;en-us;295022&Product=sql
>>Here we see substantiation that one "can" use EM and Maintenance Plans
> on
>>MSDE, albeit that you had better be the latest Service Pack since the
>>sqlmaint feature was overlooked in the original release to market.
>>The bug I am reporting is with the "Remove after X Weeks/Days" option
> for
>>Database Backup, Transaction Backup (and Log text files). This is
> important
>>because unless you can also choose to do so, one will end up filling the
>>hard disk with far too many SQL dumps.
>>If connected to an SQL server... the option works fine. If connected to
> an
>>MSDE, the option fails to provie the drop-down for days/weeks and the
>>resulting job created has bugs in the command line options of the job
> step
>>which one must then go and manually tweak to be correct (never report a
> bug
>>without a workaround eh? ;-P)
>>John D. Sullivan
>>ABELSoft Corporation
>>(email address munged)
>>
>
>
>

Thursday, February 16, 2012

Brilliant blog posting (Full-text search ideas)

I was just browsing SQL Server blogs appearing in my feeds, and this
one struck a note with me because I would kill for BOTH of the features
he mentions.
http://www.yafla.com/dforbes/categories/SQL/
Sorry for spamming some guy's blog, but if the SQL dev team reads this
please take a look at it. I doubt it's new ideas, but it's worth
reminding yourself of.Forwarded to the dev lead of Full-text search.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Seyton" <jseyton@.gmail.com> wrote in message
news:1126113969.155725.262800@.g49g2000cwa.googlegroups.com...
>I was just browsing SQL Server blogs appearing in my feeds, and this
> one struck a note with me because I would kill for BOTH of the features
> he mentions.
> http://www.yafla.com/dforbes/categories/SQL/
> Sorry for spamming some guy's blog, but if the SQL dev team reads this
> please take a look at it. I doubt it's new ideas, but it's worth
> reminding yourself of.
>|||seems to be pretty well known, I recall reading something like that on
Tom Kyte's site a while ago|||John,
The issues under "Improved Indexing in SQL Server" are well known on the
fulltext newsgroup. While both concerns are not features in SQL 2000 FTS or
SQL 2005 FTS, both issues are solvable at the application level with data
duplication. I've emailed DForbes to see if he's had previous emails on this
topic per his request.
Paul, I'm sure that the FTS Dev Lead knows about this issue and hopefully
post-Yukon it will be incorporated in the next SQL Server version, besides
he knows how to contact me.. <g>.
Regards,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:%23vTs1d9sFHA.4076@.TK2MSFTNGP11.phx.gbl...
> Forwarded to the dev lead of Full-text search.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "John Seyton" <jseyton@.gmail.com> wrote in message
> news:1126113969.155725.262800@.g49g2000cwa.googlegroups.com...
>>I was just browsing SQL Server blogs appearing in my feeds, and this
>> one struck a note with me because I would kill for BOTH of the features
>> he mentions.
>> http://www.yafla.com/dforbes/categories/SQL/
>> Sorry for spamming some guy's blog, but if the SQL dev team reads this
>> please take a look at it. I doubt it's new ideas, but it's worth
>> reminding yourself of.
>