Long time SSIS package loading

I load SSIS package using following code:

Application app = new Application();
Package pac = app.LoadFromSqlServer(packageName, serverName, null, null, null);

For simple package containing 2 tasks this code executes about 20 seconds.
If I load old version (SQL2K) package from SQL2000 then it takes 5 seconds.

Is any way to increase loading speed for SSIS packages?

Do you have SSIS service running? The service caches SSIS component information; in the absense of the service it may take long time (although it is usually 2-3 seconds on reasonable hardware) to enumerate them when loading the package.|||

Thank you Michael.
I carry out additional experiments with realworld package (contains 11 tasks) at another computer.
When I start this experiment I have to wait 1.5 minutes to load package every time. Then I examine if SSIS running. I discover SSIS don't running after SP1 was applied (widely known SP1 bug). I installed post SP1 cumulative hotfixes and continue investigation. Now package loading first time during 30 seconds. When I start it second time it takes about 2 seconds. This is good result. But is there ability to increase loading speed at first time? Will be loading perfomance improved if such delay caused internal implementation of SSIS?

|||Much of the time on the initial load of the package is due to validation of the metadata of each of your tasks. In order to speed of the initial load, you could change the DelayValidation property of your package and all tasks to true. However, that's not really best practices.|||

Thank you Martin
This helps.

BTW, BOL says:
"Validating the package before it runs is a way of finding some errors before execution starts. However, it processes the package to find errors, and if no errors are found, the package runs. Because this goes through the package two times, validating a package increases the amount of processing for the package, so should be used only when necessary."

|||

Alexey Rokhin wrote:

... I discover SSIS don't running after SP1 was applied (widely known SP1 bug). I installed post SP1 cumulative hotfixes and continue investigation. Now package loading first time during 30 seconds...

The bug you quote is described in http://support.microsoft.com/kb/918644. While the hotfix fixes the service startup failure, it can't fix the cause of the problem - long time to start the service due to network configuration that timeouts requests to CRL. So the service still takes 30+ seconds to start (which caused to fail before the hotfix, this later part is now fixed).

To avoid this 30+ delay you should either change the SSIS service to autostart (thus moving the delay to the computer boot time), or better fix the network configuration as described in the KB (although it might be very specific to your environment) to either allow access to CRL, or to quickly fail and return failure status to an application accessing CRL.

|||

Thank you, Michael.
In production environment SSIS service will autostart.

|||

Alexey,

IMHO, a good practice is defining a Events class and so, debugging the code and so you'll find issues faster, i.e with F11...

pkg = app.LoadFromSqlServer(ObjSSIS.sRutaDts & "\" & ObjSSIS.sSSISName, ObjSSIS.sServer, "usrSSIS", "ninot", EventsSSIS)

Public Class EventsSSIS

OnError

OnPreExecute

..

..

sql

Long MDX statement locks up report designer. Unknown bug?

The following query string locks up report designer on dev studio. Is there
a limitation or unknown bug that causes report designer to not be able to
parse this length of statement into xml? ( It's not too long for the query
designer text box, since the whole statement fits. I've had other queries
that needed to be redone do to length issues. something like 2k+ character
limit ) The query runs fine with the actual values instead of the parameters
that are being used here.
="WITH " &
"SET [TOP 20 CLIENTS ALL BILL TYPES] AS
'Filter([Client].[Client].Members,[Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """2D""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """6A""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """2A""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """HV""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """VK""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """VN""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """WM""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """0D""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """V5""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """VP""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """R2""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """RN""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """VT""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """CH""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """NX""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """T7""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """YV""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """N4""" & " OR [Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """MX""" & " OR
INSTR([Client].CurrentMember.Properties(" & """Client Name""" & "), " &
"""WEST RETAIL""" & ") OR INSTR([Client].CurrentMember.Properties(" &
"""Client Name""" & "), " & """WEST WHOLESALE""" & "))' " &
"SET [All Clients] as '[Client].[(All)].Members' " &
"MEMBER [Measures].[Pror#] as 'IIF([Client].CurrentMember IS [Top 20
SubTotal], " & """@.@.""" & ",IIF([Client].CurrentMember IS [All Other], " &
"""^^""" & ",IIF([Client].CurrentMember IS [Total], " & """**""" & ",
[Client].CurrentMember.Properties(" & """Client""" & "))))' " &
"SET [Weeks] as '{LastPeriods(49,[Margin Time].[Calendar].[Calendar Day].["
& Parameters!pWeekEndingDate.Label & "])}' " &
"SET [Months] as '{LastPeriods(6, [Margin Time].[Calendar].[Calendar
Month].[" & code.MonthYearPeriod(Parameters!pWeekEndingDate.Label, 0) & "])}'
" &
"SET [Expenses] as '{[Margin].&[Commission Exp].&[STD],[Margin].&[Direct
Mail Exp], [Margin].&[Internet Exp], [Margin].&[Memberlink Exp],
[Margin].&[Telemarketing Cost] }' " &
"MEMBER [Measures].[Period Ending DisplayName] as 'IIF([Margin
Time].[Calendar].CurrentMember.Level.Name = " & """Calendar Day""" & ", " &
"""Week """ & " + CSTR(VBA!DatePart(" & """ww""" & ", [Margin
Time].[Calendar].CurrentMember.Name)) + " & """ of """ & " +
CSTR(VBA!DatePart(" & """yyyy""" & ", [Margin
Time].[Calendar].CurrentMember.Name)), " & """Month """ & " +
CSTR(VBA!DatePart(" & """m""" & ", [Margin
Time].[Calendar].CurrentMember.Name)) + " & """ of """ & " +
CSTR(VBA!DatePart(" & """yyyy""" & ", [Margin
Time].[Calendar].CurrentMember.Name)))' " &
"MEMBER [Measures].[Client DisplayName] as 'IIF([Client].CurrentMember IS
[Top 20 SubTotal], " & """Top 20 SubTotal""" & ", IIF([Client].CurrentMember
IS [All Other], " & """All Other""" & ", IIF([Client].CurrentMember IS
[Total], " & """Total""" & ", IIF([Client].CurrentMember.Properties(" &
"""Client Group""" & ") <> " & """WEST TELESERVICES""" & ",
[Client].CurrentMember.Properties(" & """Client Group""" & "), " & """WEST
RETAIL""" & "))))' " &
"MEMBER [Measures].[Column Order] as 'IIF(([Margin
Time].[Calendar].CurrentMember IS [Months].Item(5)), 6, IIF(([Margin
Time].[Calendar].CurrentMember IS [Months].Item(4)), 5, IIF(([Margin
Time].[Calendar].CurrentMember IS [Months].Item(3)), 4, IIF(([Margin
Time].[Calendar].CurrentMember IS [Months].Item(2)), 3, IIF(([Margin
Time].[Calendar].CurrentMember IS [Months].Item(1)), 2, IIF(([Margin
Time].[Calendar].CurrentMember IS [Months].Item(0)), 1, 9))))))' " &
"MEMBER [Client].[Top 20 SubTotal] as '[Top 20 SubTotal]' " &
"MEMBER [Client].[All Other] as '[All Other]' " &
"MEMBER [Client].[Total] as '[Total]' " &
"MEMBER [Measures].[Rank] as ' IIF([Client].CurrentMember IS [Top 20
SubTotal], 21, IIF([Client].CurrentMember IS [All Other], 22,
IIF([Client].CurrentMember IS [Total],
23,IIF(INSTR([Client].CurrentMember.Properties(" & """Client Name""" & "), "
& """WEST RETAIL""" & ") OR INSTR([Client].CurrentMember.Properties(" &
"""Client Name""" & "), " & """WEST WHOLESALE""" & ") ,
1,IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """2D"""
& " , 2, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
"""6A""" & " , 3, IIF([Client].CurrentMember.Properties(" & """Client""" & ")
= " & """2A""" & " , 4, IIF([Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """HV""" & " , 5,
IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """VK""" &
" , 6, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
"""VN""" & " , 7, IIF([Client].CurrentMember.Properties(" & """Client""" & ")
= " & """WM""" & " , 8, IIF([Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """0D""" & " , 9,
IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """V5""" &
" , 10, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
"""VP""" & " , 11, IIF([Client].CurrentMember.Properties(" & """Client""" &
") = " & """R2""" & " , 12, IIF([Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """RN""" & " , 13,
IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """VT""" &
" , 14, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
"""CH""" & " , 15, IIF([Client].CurrentMember.Properties(" & """Client""" &
") = " & """NX""" & " , 16, IIF([Client].CurrentMember.Properties(" &
"""Client""" & ") = " & """T7""" & " , 17,
IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """YV""" &
" , 18, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
"""N4""" & " , 19, IIF([Client].CurrentMember.Properties(" & """Client""" &
") = " & """MX""" & " , 20, 99)))))))))))))))))))))))' " &
"MEMBER [Measures].[Actual] AS 'IIF([Client].CurrentMember IS [Top 20
SubTotal], SUM({Crossjoin([TOP 20 CLIENTS ALL BILL TYPES], [Expenses]) },
[Measures].[Dollars]) / 1000, IIF([Client].CurrentMember IS [All Other],
((SUM({Crossjoin( [All Clients], [Expenses]) }, [Measures].[Dollars])) -
(SUM({Crossjoin([TOP 20 CLIENTS ALL BILL TYPES], [Expenses]) },
[Measures].[Dollars]))) / 1000, IIF([Client].CurrentMember IS [Total],
SUM({Crossjoin( [All Clients], [Expenses]) }, [Measures].[Dollars]) / 1000,
SUM({ [Expenses] }, [Measures].[Dollars]) / 1000)))' " &
"SELECT {[Measures].[Rank], [Measures].[Column Order], [Measures].[Client
DisplayName], [Measures].[Pror#], [Measures].[Period Ending DisplayName],
[Measures].[Actual], [Measures].[Dollars] } ON COLUMNS, " &
"NON EMPTY {CROSSJOIN( {[TOP 20 CLIENTS ALL BILL TYPES], [Client].[Top 20
SubTotal] , [Client].[All Other], [Client].[Total] }, {[Weeks], [Months] } )
} ON ROWS " &
"FROM [Margins] WHERE ([Bill Type].[Bill Group].&[New] )"Created named set on the cube to shorten the length. No further help
needed.
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:C3338E73-870C-4425-B40E-99C8DCCC1D5E@.microsoft.com...
> The following query string locks up report designer on dev studio. Is
there
> a limitation or unknown bug that causes report designer to not be able to
> parse this length of statement into xml? ( It's not too long for the query
> designer text box, since the whole statement fits. I've had other queries
> that needed to be redone do to length issues. something like 2k+
character
> limit ) The query runs fine with the actual values instead of the
parameters
> that are being used here.
> ="WITH " &
> "SET [TOP 20 CLIENTS ALL BILL TYPES] AS
> 'Filter([Client].[Client].Members,[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """2D""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """6A""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """2A""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """HV""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """VK""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """VN""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """WM""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """0D""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """V5""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """VP""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """R2""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """RN""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """VT""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """CH""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """NX""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """T7""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """YV""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """N4""" & " OR
[Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """MX""" & " OR
> INSTR([Client].CurrentMember.Properties(" & """Client Name""" & "), " &
> """WEST RETAIL""" & ") OR INSTR([Client].CurrentMember.Properties(" &
> """Client Name""" & "), " & """WEST WHOLESALE""" & "))' " &
> "SET [All Clients] as '[Client].[(All)].Members' " &
> "MEMBER [Measures].[Pror#] as 'IIF([Client].CurrentMember IS [Top 20
> SubTotal], " & """@.@.""" & ",IIF([Client].CurrentMember IS [All Other], " &
> """^^""" & ",IIF([Client].CurrentMember IS [Total], " & """**""" & ",
> [Client].CurrentMember.Properties(" & """Client""" & "))))' " &
> "SET [Weeks] as '{LastPeriods(49,[Margin Time].[Calendar].[Calendar
Day].["
> & Parameters!pWeekEndingDate.Label & "])}' " &
> "SET [Months] as '{LastPeriods(6, [Margin Time].[Calendar].[Calendar
> Month].[" & code.MonthYearPeriod(Parameters!pWeekEndingDate.Label, 0) &
"])}'
> " &
> "SET [Expenses] as '{[Margin].&[Commission Exp].&[STD],[Margin].&[Direct
> Mail Exp], [Margin].&[Internet Exp], [Margin].&[Memberlink Exp],
> [Margin].&[Telemarketing Cost] }' " &
> "MEMBER [Measures].[Period Ending DisplayName] as 'IIF([Margin
> Time].[Calendar].CurrentMember.Level.Name = " & """Calendar Day""" & ", "
&
> """Week """ & " + CSTR(VBA!DatePart(" & """ww""" & ", [Margin
> Time].[Calendar].CurrentMember.Name)) + " & """ of """ & " +
> CSTR(VBA!DatePart(" & """yyyy""" & ", [Margin
> Time].[Calendar].CurrentMember.Name)), " & """Month """ & " +
> CSTR(VBA!DatePart(" & """m""" & ", [Margin
> Time].[Calendar].CurrentMember.Name)) + " & """ of """ & " +
> CSTR(VBA!DatePart(" & """yyyy""" & ", [Margin
> Time].[Calendar].CurrentMember.Name)))' " &
> "MEMBER [Measures].[Client DisplayName] as 'IIF([Client].CurrentMember IS
> [Top 20 SubTotal], " & """Top 20 SubTotal""" & ",
IIF([Client].CurrentMember
> IS [All Other], " & """All Other""" & ", IIF([Client].CurrentMember IS
> [Total], " & """Total""" & ", IIF([Client].CurrentMember.Properties(" &
> """Client Group""" & ") <> " & """WEST TELESERVICES""" & ",
> [Client].CurrentMember.Properties(" & """Client Group""" & "), " & """WEST
> RETAIL""" & "))))' " &
> "MEMBER [Measures].[Column Order] as 'IIF(([Margin
> Time].[Calendar].CurrentMember IS [Months].Item(5)), 6, IIF(([Margin
> Time].[Calendar].CurrentMember IS [Months].Item(4)), 5, IIF(([Margin
> Time].[Calendar].CurrentMember IS [Months].Item(3)), 4, IIF(([Margin
> Time].[Calendar].CurrentMember IS [Months].Item(2)), 3, IIF(([Margin
> Time].[Calendar].CurrentMember IS [Months].Item(1)), 2, IIF(([Margin
> Time].[Calendar].CurrentMember IS [Months].Item(0)), 1, 9))))))' " &
> "MEMBER [Client].[Top 20 SubTotal] as '[Top 20 SubTotal]' " &
> "MEMBER [Client].[All Other] as '[All Other]' " &
> "MEMBER [Client].[Total] as '[Total]' " &
> "MEMBER [Measures].[Rank] as ' IIF([Client].CurrentMember IS [Top 20
> SubTotal], 21, IIF([Client].CurrentMember IS [All Other], 22,
> IIF([Client].CurrentMember IS [Total],
> 23,IIF(INSTR([Client].CurrentMember.Properties(" & """Client Name""" & "),
"
> & """WEST RETAIL""" & ") OR INSTR([Client].CurrentMember.Properties(" &
> """Client Name""" & "), " & """WEST WHOLESALE""" & ") ,
> 1,IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
"""2D"""
> & " , 2, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
> """6A""" & " , 3, IIF([Client].CurrentMember.Properties(" & """Client""" &
")
> = " & """2A""" & " , 4, IIF([Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """HV""" & " , 5,
> IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """VK"""
&
> " , 6, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
> """VN""" & " , 7, IIF([Client].CurrentMember.Properties(" & """Client""" &
")
> = " & """WM""" & " , 8, IIF([Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """0D""" & " , 9,
> IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """V5"""
&
> " , 10, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
> """VP""" & " , 11, IIF([Client].CurrentMember.Properties(" & """Client"""
&
> ") = " & """R2""" & " , 12, IIF([Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """RN""" & " , 13,
> IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """VT"""
&
> " , 14, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
> """CH""" & " , 15, IIF([Client].CurrentMember.Properties(" & """Client"""
&
> ") = " & """NX""" & " , 16, IIF([Client].CurrentMember.Properties(" &
> """Client""" & ") = " & """T7""" & " , 17,
> IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " & """YV"""
&
> " , 18, IIF([Client].CurrentMember.Properties(" & """Client""" & ") = " &
> """N4""" & " , 19, IIF([Client].CurrentMember.Properties(" & """Client"""
&
> ") = " & """MX""" & " , 20, 99)))))))))))))))))))))))' " &
> "MEMBER [Measures].[Actual] AS 'IIF([Client].CurrentMember IS [Top 20
> SubTotal], SUM({Crossjoin([TOP 20 CLIENTS ALL BILL TYPES], [Expenses]) },
> [Measures].[Dollars]) / 1000, IIF([Client].CurrentMember IS [All Other],
> ((SUM({Crossjoin( [All Clients], [Expenses]) }, [Measures].[Dollars])) -
> (SUM({Crossjoin([TOP 20 CLIENTS ALL BILL TYPES], [Expenses]) },
> [Measures].[Dollars]))) / 1000, IIF([Client].CurrentMember IS [Total],
> SUM({Crossjoin( [All Clients], [Expenses]) }, [Measures].[Dollars]) /
1000,
> SUM({ [Expenses] }, [Measures].[Dollars]) / 1000)))' " &
> "SELECT {[Measures].[Rank], [Measures].[Column Order], [Measures].[Client
> DisplayName], [Measures].[Pror#], [Measures].[Period Ending DisplayName],
> [Measures].[Actual], [Measures].[Dollars] } ON COLUMNS, " &
> "NON EMPTY {CROSSJOIN( {[TOP 20 CLIENTS ALL BILL TYPES], [Client].[Top 20
> SubTotal] , [Client].[All Other], [Client].[Total] }, {[Weeks],
[Months] } )
> } ON ROWS " &
> "FROM [Margins] WHERE ([Bill Type].[Bill Group].&[New] )"
>

Long line of text error

Hey,
After working on a package for a while, I started to get the following error
when re-opening the package:
"Document contains one or more extremely long lines of text.
These lines will cause the editor to respond slowly when you open the file.
Do you still want to open the file?"
What is the problem and if there is fix or workaround?
Thanks.There is no fix or workaround however don't worry because there isn't a problem either. Its just a VS thing rather than a SSIS thing that's all.

I think (but may be wrong) it appears when you have a pre-compiled script task/component in your package. Perhaps you could confirm?

-Jamie|||Yes, I have precompiled script tasks in package. Otherwise they don't work :)|||Don't they?

This is a complete digression from the main point of this thread but...why not? What error do you get?

-Jamie

P.S. As I say, forget about the "long lines of text" thing!|||it's on this tread
http://forums.microsoft.com/msdn/showpost.aspx?postid=68546&siteid=1
actually I had the same problem. with precompilation I get no error.

ps. thanks for answering on "long line text..." stuff.

Logshipping question

Win 2K Adv Server SQL2K sp3a
I have implemented logshipping from server A to server B monitor
server C following the instructions
Everything works fine, every 15 minutes the Backup, Copy and Restore
jobs run
But the destination database is in Loading io Read Only
What is wrong ?
TIA
Jan Waumans<jw@.jw.com> wrote in message
news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
> Win 2K Adv Server SQL2K sp3a
> I have implemented logshipping from server A to server B monitor
> server C following the instructions
> Everything works fine, every 15 minutes the Backup, Copy and Restore
> jobs run
> But the destination database is in Loading io Read Only
> What is wrong ?
When the logs are restored onto server B they are restored WITH NO RECOVERY.
In other words the logs are not rolled forward to make the database
consistent. It is waiting for the next set of logs. If the database was
not read-only then if people made changes to the Server B database you would
not be able to read the next shipped logs.
If you want to have an updatable copy of your database where changes are
replicated every 15 minutes you might wnat to take a peek at replication.|||Bob,
I use replication since 6.0
The reason I want to go to logshipping is that replication is too
difficult to maintain for recovery sites (no schema changes except
with the unusable additional column in 2K mode, only 1 logreader per
published database, ...)
Since in Win2K you can restore a DB in read-only state allowing
additional log restores, I figure this is what logshipping should do
How the destination db could be usable anyway?
Our setup as disaster recovery does not need an access to the
destination db's in normal circumstances, but we need to be able to
switch over in case of emergency
MS clearly states that logshipping is a better solution for disaster
recovery than replication
I must do something wrong
JW
On Thu, 25 Mar 2004 20:42:59 -0000, "Bob Simms"
<bob_simms@.somewhere.com> wrote:

><jw@.jw.com> wrote in message
> news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
>When the logs are restored onto server B they are restored WITH NO RECOVERY
.
>In other words the logs are not rolled forward to make the database
>consistent. It is waiting for the next set of logs. If the database was
>not read-only then if people made changes to the Server B database you woul
d
>not be able to read the next shipped logs.
>If you want to have an updatable copy of your database where changes are
>replicated every 15 minutes you might wnat to take a peek at replication.
>|||log shipping is better than replication in case you want to have the second
server for stand-by. You can read DBs on stand-by server as long as the log
restore is not running. In your case there is nothing wrong when you see
the DB in single user mode.
<jw@.jw.com> wrote in message
news:2dh660tsgo13lv90e53dquf1c03jcren8m@.
4ax.com...
> Bob,
> I use replication since 6.0
> The reason I want to go to logshipping is that replication is too
> difficult to maintain for recovery sites (no schema changes except
> with the unusable additional column in 2K mode, only 1 logreader per
> published database, ...)
> Since in Win2K you can restore a DB in read-only state allowing
> additional log restores, I figure this is what logshipping should do
> How the destination db could be usable anyway?
> Our setup as disaster recovery does not need an access to the
> destination db's in normal circumstances, but we need to be able to
> switch over in case of emergency
> MS clearly states that logshipping is a better solution for disaster
> recovery than replication
> I must do something wrong
> JW
>
> On Thu, 25 Mar 2004 20:42:59 -0000, "Bob Simms"
> <bob_simms@.somewhere.com> wrote:
>
RECOVERY.
would
>|||Study the docs in books on line referring to Log Shipping... There is a
procedure you must go through to make the log ship databases Primary, in the
case of failure.. There is a DTS job and some exports involved... You'd be
well served to test this and ensure you have a good plan...
But until you run recovery on the secondary ( part of the process) it will
show as loading...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<jw@.jw.com> wrote in message
news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
> Win 2K Adv Server SQL2K sp3a
> I have implemented logshipping from server A to server B monitor
> server C following the instructions
> Everything works fine, every 15 minutes the Backup, Copy and Restore
> jobs run
> But the destination database is in Loading io Read Only
> What is wrong ?
> TIA
> Jan Waumans

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls advice
Are you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>
|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...
|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...
|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>
|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>
|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft]&
#91;ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp
4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empt
y
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanis
m
to ensure that data is completely written and also there are no power failur
e
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:
> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql
> sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
>|||"bijupg@.hotmail.com" schrieb:
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:
> "bijupg@.hotmail.com" schrieb:
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>> Hi Guys,
>> I am facing following problem with MSSQL Server 2000.
>> I am using Microsoft sql server Log Shipping feature to have a standby
>> server for disaster recovery purposes.
>> in the logshipping Destination server while restoring the transaction log
>> the restore process is failling with following error.
>> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
>> SQL
>> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
>> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
>> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
>> PrevPageLSN: (8122:7374:3)."
>> Both servers, source and destination were running with SQL SERVER
>> ENTERPRISE EDITION SP3 .
>> after this failure i rebuilded the logshipping process but same error
>> happened again so after one week updated the destination server with sql
>> sp4
>> and rebuilded the logshipping process . but the same error happened
>> again.
>> During this error SQL Server is creating a dump file and text file
>> pls advice
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>sql

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceThis is a multi-part message in MIME format.
--040104080107040407070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
--040104080107040407070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Sounds like the corruption on the primary DB has put the tlog syncs
out of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the
log shipping pair for you using the DB maint wizard.)</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD73EA24F-DBEA-4E4F-9F4F-797DC31E31FF@.microsoft.com"
type="cite">
<pre wrap="">Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
</pre>
</blockquote>
</body>
</html>
--040104080107040407070908--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

---

--=_NextPart_000_000D_01C56A79.C4EDC0F0--

Logshipping error

Hi,
I get the following error after I setup logshipping and
try to restore the copied trn file.
Any ideas'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log in
this backup set terminates at LSN 37123000007023700001,
which is too early to apply to the database. A more
recent log backup that includes LS
N 37731000001578500001 can be
restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
LOG is terminating
abnormally.| I get the following error after I setup logshipping and
| try to restore the copied trn file.
| Any ideas'
|
| [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326:
| [Microsoft][ODBC SQL Server Driver][SQL Server]The log in
| this backup set terminates at LSN 37123000007023700001,
| which is too early to apply to the database. A more
| recent log backup that includes LS
| N 37731000001578500001 can be
| restored.
|
| [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
| LOG is terminating
| abnormally.
--
It looks like your transaction log backups are out-of-synch. Can you review
your scheduled jobs and make sure that only the log shipping process and no
other independent jobs are creating transaction log backups.
Hope this helps,
--
Eric Cárdenas
SQL Server support

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceSounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:

>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][O
DBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:

>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

Logs

I can't get a 7.0 log to shrink. Can't I get it to shrink
if I do the following?
BACKUP LOG DBNAME WITH TRUNCATE_ONLY
Also: where does this backup go - into computer oblivion?That backup doesn't go anywhere. The log records that will be removed goes
into the "trash can". Check out below KB articles:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Log File Grows too big
http://www.support.microsoft.com/?id=317375
Log file filling up
http://www.support.microsoft.com/?id=110139
Considerations for Autogrow and AutoShrink
http://www.support.microsoft.com/?id=315512
http://www.mssqlserver.com/faq/logs-shrinklog.asp
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"CLM" <anonymous@.discussions.microsoft.com> wrote in message
news:ea7501c3f0c7$ccc226e0$a401280a@.phx.gbl...
> I can't get a 7.0 log to shrink. Can't I get it to shrink
> if I do the following?
> BACKUP LOG DBNAME WITH TRUNCATE_ONLY
> Also: where does this backup go - into computer oblivion?|||That's what I thought but wanted to confirm.
And thx for the articles...
>--Original Message--
>That backup doesn't go anywhere. The log records that
will be removed goes
>into the "trash can". Check out below KB articles:
>INF: How to Shrink the SQL Server 7.0 Transaction Log
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;256650
>INF: Shrinking the Transaction Log in SQL Server 2000
with DBCC SHRINKFILE
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;272318
>Log File Grows too big
>http://www.support.microsoft.com/?id=317375
>Log file filling up
>http://www.support.microsoft.com/?id=110139
>Considerations for Autogrow and AutoShrink
>http://www.support.microsoft.com/?id=315512
>http://www.mssqlserver.com/faq/logs-shrinklog.asp
>
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"CLM" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ea7501c3f0c7$ccc226e0$a401280a@.phx.gbl...
>> I can't get a 7.0 log to shrink. Can't I get it to
shrink
>> if I do the following?
>> BACKUP LOG DBNAME WITH TRUNCATE_ONLY
>> Also: where does this backup go - into computer
oblivion?
>
>.
>

Logparser issue with SQL Server 2005 Report Pack for IIS

Hi, I don't know if it is the right place to post this question, I am trying
to populate IISLOG DB with IIS log file using the following expression
(provided in the package DOC)
LogParser "SELECT date, time,
strcat(strcat(strcat(TO_STRING(TO_TIMESTAMP(date, time), 'hh'),':00-'),
TO_STRING(TO_TIMESTAMP(date, time), 'hh')),':59') AS Hour,
TO_Int(TO_String(date,'MM')) as Month, TO_Int(TO_String(date,'yyyy')) as
year,c-ip, cs-username, s-sitename, s-computername, s-ip, s-port, cs-method,
cs-uri-stem, cs-uri-query, sc-status, sc-substatus, sc-win32-status,
sc-bytes, cs-bytes, time-taken, cs-version, cs-host, cs(User-Agent),
cs(Cookie), cs(Referer) FROM d:\tracing\Tracingex061025.log TO
GlobalIISLogWF4"
-i:IISW3C -o:SQL -server:(local) -database:IISLog -createtable:ON -e:10
In the command line window, I wait for a while, then I get 3 lines
indicating Statistics without inserting any row in the table that has been
created which is "GlobalIISLogWF4"
I re-run the commande and launched SQL 2005 profiler,
I see the following events
***************************
RPC:Starting
RPC:Completed
in the text I see only
exec sp_cursor 180150003,65536
***************************
but absolutly no inserts
It is a win2k3R2 64bit, sql server 2005 64 bit and logparser the 2 versions
32 bit and 64 bit.
ThanksHello Eliassal,
I would like to know that if you have enable the IIS to log the cs(Cookie),
cs(Referer) event.
Also, what about using the following Command?
LogParser "SELECT date, time,
strcat(strcat(strcat(TO_STRING(TO_TIMESTAMP(date, time), 'hh'),':00-'),
TO_STRING(TO_TIMESTAMP(date, time), 'hh')),':59') AS Hour,
TO_Int(TO_String(date,'MM')) as Month, TO_Int(TO_String(date,'yyyy')) as
year,c-ip, cs-username, s-sitename, s-computername, s-ip, s-port,
cs-method,
cs-uri-stem, cs-uri-query, sc-status, sc-substatus, sc-win32-status,
sc-bytes, cs-bytes, time-taken, cs-version, cs-host, [cs(User-Agent)],
[cs(Cookie)], [cs(Referer)] FROM d:\tracing\Tracingex061025.log TO
GlobalIISLogWF4"
-i:IISW3C -o:SQL -server:(local) -database:IISLog -createtable:ON -e:10
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||HI, yes both are enabled. Only"Host" is not enabled.
I ran the sql you suggested, no inserts as well, the ouput was as follows
Statistics:
--
Elements processed: 422762
Elements output: 422762
Execution time: 22.00 seconds
Any idea? Thanks for your help
"Wei Lu [MSFT]" wrote:
> Hello Eliassal,
> I would like to know that if you have enable the IIS to log the cs(Cookie),
> cs(Referer) event.
> Also, what about using the following Command?
> LogParser "SELECT date, time,
> strcat(strcat(strcat(TO_STRING(TO_TIMESTAMP(date, time), 'hh'),':00-'),
> TO_STRING(TO_TIMESTAMP(date, time), 'hh')),':59') AS Hour,
> TO_Int(TO_String(date,'MM')) as Month, TO_Int(TO_String(date,'yyyy')) as
> year,c-ip, cs-username, s-sitename, s-computername, s-ip, s-port,
> cs-method,
> cs-uri-stem, cs-uri-query, sc-status, sc-substatus, sc-win32-status,
> sc-bytes, cs-bytes, time-taken, cs-version, cs-host, [cs(User-Agent)],
> [cs(Cookie)], [cs(Referer)] FROM d:\tracing\Tracingex061025.log TO
> GlobalIISLogWF4"
> -i:IISW3C -o:SQL -server:(local) -database:IISLog -createtable:ON -e:10
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>|||Hello Eliassal,
You could reduce the column, and check which column will cause this issue.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi, I launched a full sql 2005 profiler, In the session I HAVE THE FOLLOWING
ERROR
***********************************************************
exec sp_cursor 180150003, 65536
Error: 16902, Severity: 16, State: 33
sp_cursor: The value of the parameter 'optype' is invalid.
***********************************************************
I tried to execute the script by taking off 4 fields each time, no way
always the same error
The problem is we don't have the sql Insert phrase to execute in SSMS to be
able to see the error and don't no the internal of loparser of hiow it
inserts.
I am really going desperate. I need to demo the reporting to my director
next week
"Wei Lu [MSFT]" wrote:
> Hello Eliassal,
> You could reduce the column, and check which column will cause this issue.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Eliassal,
I searched our internal database and found that this error may caused by
the log file format is not correct.
You may try to get the IISLog from other machines and try it again.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||What is strange is that when I run the command against any other machine
(32bit) and not 64bit the upload works fine
The log files come from a win2k 32 bit machines. My sql2005 64bit is on a
win2k3 R2
"Wei Lu [MSFT]" wrote:
> Hello Eliassal,
> I searched our internal database and found that this error may caused by
> the log file format is not correct.
> You may try to get the IISLog from other machines and try it again.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Eliassal,
Please note the managed newsgroups are staffed weekdays by Microsoft
Support professionals. Our goal is to provide a one business day response
to all posts.
Since this issue is critical, I would like to suggest you to use the
following workaround:
1. Use the Logparser to import the IIS log to a SQL Server 2005 32bit
machine.
2. Use the SSIS to import from the 32 bit machine to the 64bit SQL Server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi, I setup another machine everything in 64bit and logparser works fine. So
I think it is something wrong with either the setup of sql or the OS.
However, I have a new issue now for displaying the results in Reporting
services. I have loaded 10 days worth of IIS log (5 million rows). Whenever I
try to launch any report, IN IE I have the message "Report is being
generated" and wait for almost 30 to 45 minutes then I get a timeout. I know
the table is provided with no optimization (indexes, non clustered....)
I launched SQKL profiler and found that in different SP there is a lot of
complex sql statements
Any idea or is there sombody who has optimized the table or the whole DB
Thanks in advance
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Eliassal,
I would like to suggest you use the Report Cache to improve the report
performence.
Also, I suggest you to reduce the record number in your dataset.
Please note, our service does not provide support on Resource Kit Utilities.
For more detailed information, please refer our team blog:
http://blogs.msdn.com/msdnts/archive/2006/11/08/msdn-service-introduction.as
px
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Logon failure: the user has not been granted the requested logon t

I get the following error when I try running a report using Reporting
Services 2005. The Data Source gets to SQL Server using a domain account. The
Application Pool is running under NETWORK SERVICE.
I see a lot of postings about allowing for Logon Locally. I am sure this
could fix the issue, but why is that standard practice? I don't allow that
for impersonating a user in a standard web application (with web.config --
impersonate user).
===== Error ========= An error has occurred during report processing.
Cannot impersonate user for data source 'DataSourceName'.
Logon failed.
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)We don't use logon locally rights...
Instead, we grant NETWORK SERVICE account the right to connect to the SQL
Server database (the specific database) instead.
Some administrators would flip out if they had to change their local
security policy. At least as a DBA I can make this change without having to
involve layers of people to get it implemented.
=-Chris
"Sanjay T" <SanjayT@.discussions.microsoft.com> wrote in message
news:2D831614-9BF9-4C7A-B290-13A1DCD23498@.microsoft.com...
>I get the following error when I try running a report using Reporting
> Services 2005. The Data Source gets to SQL Server using a domain account.
> The
> Application Pool is running under NETWORK SERVICE.
> I see a lot of postings about allowing for Logon Locally. I am sure this
> could fix the issue, but why is that standard practice? I don't allow that
> for impersonating a user in a standard web application (with web.config --
> impersonate user).
>
> ===== Error =========> An error has occurred during report processing.
> Cannot impersonate user for data source 'DataSourceName'.
> Logon failed.
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)

Logon failed when attempting to run report

When attempting to run a report, the following error appeared.
What does the following error message mean?
Logon failed.
Logon failure: unknown user name or bad password. (Exception from HRESULT:
0x8007052E)Looks like your report credentials are not set.
Go to Report Manager, navigate to the report, go to properties and make
sure your data sources are all correctly set up

Logon Error: 18456, Severity: 14, State: 8 - NEED HELP!!!!

Hi All,

I am getting the following error in the ERRORLOG File when I am
trying to connect to SQL Server 2005 Enterprise Edition 64bit with SP2 from
Reporting Services Configuration tool - Database Setup. The SQL Server
database and reporting services are on 2 different servers. Both are running
2003 SP2 64 bit.

2007-04-12 07:30:05.54 Logon Error: 18456, Severity: 14, State:
8.
2007-04-12 07:30:05.54 Logon Login failed for user 'sa'.
[CLIENT: xx.xx.xx.xx]

I know my password is valid as I can logged into SSMS using SA. I can create
the 2 reportserver databases using the Reporting Services Configuration tool
on the database server. The db server is in MIXED mode.

What am I missing?

Related articles I have followed are:

Login failed for user 'x'
http://msdn2.microsoft.com/en-us/library/ms366351.aspx

Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx

Any help to get passed this problem would greatly be appreciated.
Thanks in advance for your time!

Hello,

Can you verify that you have "SQL Server Credentials" selected as the "Credentials Type" in the Database Setup section?

Hope this helps.

Jarret

|||Yes I have "SQL Server Credentials" selected as the "Credentials Type" in the Database Setup section.|||

Can you try to use a Windows account (with administrator privileges) instead of the SQL account?

Jarret

|||I un-install and re-installed Reporting Services on the web server. This corrected the problem.

Thanks to everyone for their replies.

Logon Error: 18456, Severity: 14, State: 8 - NEED HELP!!!!

Hi All,

I am getting the following error in the ERRORLOG File when I am
trying to connect to SQL Server 2005 Enterprise Edition 64bit with SP2 from
Reporting Services Configuration tool - Database Setup. The SQL Server
database and reporting services are on 2 different servers. Both are running
2003 SP2 64 bit.

2007-04-12 07:30:05.54 Logon Error: 18456, Severity: 14, State:
8.
2007-04-12 07:30:05.54 Logon Login failed for user 'sa'.
[CLIENT: xx.xx.xx.xx]

I know my password is valid as I can logged into SSMS using SA. I can create
the 2 reportserver databases using the Reporting Services Configuration tool
on the database server. The db server is in MIXED mode.

What am I missing?

Related articles I have followed are:

Login failed for user 'x'
http://msdn2.microsoft.com/en-us/library/ms366351.aspx

Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx

Any help to get passed this problem would greatly be appreciated.
Thanks in advance for your time!

Are you using Vista?

http://www.microsoft.com/sql/howtobuy/windowsvistasupport.mspx

If not, try here:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

|||On both servers we have Windows 2003 Server 64bit with SP2 applied. I previously visited the second link listed above. All its explains that a State: 8 is a password mismatch. I know I'm entering the password correctly in the Reporting Services Configuration tool. However, I believe when it gets sent to the db server it is missing or encrypted someway that the db server can't decrypt.

Thanks again.
|||

I wasn't sure where you were connecting from, hence the Vista question. In Vista, your admin group token is stripped, and SQL Server might be depending on that membership to get you in.

So where are you connecting from and to? In other words, you say you have two servers, but I'm not sure which one you're connecting from. I want to be sure I have the whole picture.

In the meantime, you can fire up Profiler and see what you're sending across the net to connect. you're correct, in SQL 2K5, the connection info is encrypted, but both sides should know how to deal with that.

Also, I'm sure you've tried this already, but make sure you try a couple of accounts, just in case. Try the sa and a Windows account.

Between all these, you should be able to figure out where the problem is, if not its resolution. Then reply back and we'll see if we can get you closer to the right answer.

|||

State 8 does indeed indicate a password mismatch, so you should check that the password provided to Reporting Services is indeed the correct one. If you are certain that the password is correct, then Reporting Services may not be passing it correctly to SQL Server - please check on the SQL Server Reporting Services forum, to see if this is a known issue.

Thanks

Laurentiu

|||I un-install and re-installed Reporting Services on the web server. This corrected the problem.

Thanks to everyone for their replies.

Logon Error ?

The following error is logged in SQL Server 2005 Logfile. Could anyone
explain why this error is happening ?
Message
The server was unable to load the SSL provider library needed to log in; the
connection has been closed. SSL is used to encrypt either the login sequence
or all communications, depending on how the administrator has configured the
server. See Books Online for information on this error message: 0x6d.
[CLIENT: <named pipe>]Hi,
Have you installed an SSL certificate on the SQL Server?
If not then remove any configuration you may have on the server to force
encryption for connections (SQL Server Configuration Manager). You should
also remove any configuration on the client computers requiring them to
connect using encryption (SQL Native Client Configuration).
In BOL, please check
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e1e55519-97ec-4404-81ef-881d
a3b42006.htm
Nathan H. Omukwenyi
"swami" <swami@.discussions.microsoft.com> wrote in message
news:F4FC882D-DE26-4D8A-AACA-3DC7CF1C5F70@.microsoft.com...
> The following error is logged in SQL Server 2005 Logfile. Could anyone
> explain why this error is happening ?
> Message
> The server was unable to load the SSL provider library needed to log in;
> the
> connection has been closed. SSL is used to encrypt either the login
> sequence
> or all communications, depending on how the administrator has configured
> the
> server. See Books Online for information on this error message: 0x6d.
> [CLIENT: <named pipe>]|||As far as we can see - encryption is not set anywhere, either on the
server or client.
any other clues ?
"Nathan H. Omukwenyi" wrote:

> Hi,
> Have you installed an SSL certificate on the SQL Server?
> If not then remove any configuration you may have on the server to force
> encryption for connections (SQL Server Configuration Manager). You should
> also remove any configuration on the client computers requiring them to
> connect using encryption (SQL Native Client Configuration).
> In BOL, please check
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e1e55519-97ec-4404-81ef-88
1da3b42006.htm
> Nathan H. Omukwenyi
>
>
> "swami" <swami@.discussions.microsoft.com> wrote in message
> news:F4FC882D-DE26-4D8A-AACA-3DC7CF1C5F70@.microsoft.com...
>
>