sql login permissions: loading

Showing posts with label loading. Show all posts

Friday, March 30, 2012

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

Monday, March 26, 2012

long loading times! Please help!

Hi everyone,
I have extremely long loading/refreshing times when
running anything with SQL Server (i.e. Axapta, Analysis
Manager, Enterprise Manager), but I know that my CPU isnt
getting slammed (Task Manager indicates lts of free
memory, CPU usage low). I have recently installed SQL
Server 2000 and Axapta. I do not have many other
programs and when a other large files/programs are
loaded, they run perfectly fine. I am pretty sure the
problem lies in the SQL Server, but not too sure on where
to troubleshoot?
Thanks,
Carl
.I think you can use SQL Profiler to monitor performance on
your SQL server.
http://www.techrepublic.com/article.jhtml?
id=r00220020919wrr01.htm&page=1
Hope this helps.
Sunny
>--Original Message--
>Hi everyone,
>I have extremely long loading/refreshing times when
>running anything with SQL Server (i.e. Axapta, Analysis
>Manager, Enterprise Manager), but I know that my CPU isnt
>getting slammed (Task Manager indicates lts of free
>memory, CPU usage low). I have recently installed SQL
>Server 2000 and Axapta. I do not have many other
>programs and when a other large files/programs are
>loaded, they run perfectly fine. I am pretty sure the
>problem lies in the SQL Server, but not too sure on where
>to troubleshoot?
>Thanks,
>Carl
>..
>
>.
>

Friday, March 23, 2012

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> 
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson | database administrator
| mallesons stephen jaques 
T +61 (2) 9296 3668 | F +61
(2) 9296 3885 | M +61
(408) 675 907 
E
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> | W <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a> 
</div>
 
 
<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

Logshipping

Wednesday, March 21, 2012

Logshipping

Hi
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We already
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
UdayHi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't find
> the network path name. The full backup job says that it ran for 1:26minutes
> before it failed. But i see transaction log for every 15minutes in that 1:26
> minutes. Usually when the ful backup starts, the transaction log back starts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
> > Hi
> > Can you see how did the last LOG restore to the database? What happened?
> >
> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > > Hi
> > >
> > > I have a strange problem started happening in my log shipping. The
> > > database
> > > went to suspect/loading/read-only mode in the middle of the night.
> > > Can't see any particular reason in the sql srever errorlog.
> > >
> > > One thing i noticed in th msdb..backupset. This table did not have an
> > > entry
> > > for anyother transaction log that happened after the last transaction log
> > > that got applid to the database. But the logshipping copy job is fine and
> > > it
> > > copies all the logs. Something broken internally in the logshpping. I
> > > looked
> > > online for anymore info. Apparently there was a hotfix before SP3. We
> > > already
> > > have sp3 on this server.
> > >
> > > Did anyone experience this problem?
> > > Any idea?
> > > Any kind of help is appreciated.
> > >
> > > Thanks
> > > Uday
> >
> >
> >|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
>> Hi Uri
>> I also notice something strange.
>> The database that was doing the full backup job failed.
>> It actually did do the backup. But the job failed saying that it can't
>> find
>> the network path name. The full backup job says that it ran for
>> 1:26minutes
>> before it failed. But i see transaction log for every 15minutes in that
>> 1:26
>> minutes. Usually when the ful backup starts, the transaction log back
>> starts
>> but never does the transaction log backup until its completed. Right.
>> This is strange.
>> --Uday
>> "Uri Dimant" wrote:
>> > Hi
>> > Can you see how did the last LOG restore to the database? What
>> > happened?
>> >
>> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
>> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>> > > Hi
>> > >
>> > > I have a strange problem started happening in my log shipping. The
>> > > database
>> > > went to suspect/loading/read-only mode in the middle of the night.
>> > > Can't see any particular reason in the sql srever errorlog.
>> > >
>> > > One thing i noticed in th msdb..backupset. This table did not have an
>> > > entry
>> > > for anyother transaction log that happened after the last transaction
>> > > log
>> > > that got applid to the database. But the logshipping copy job is fine
>> > > and
>> > > it
>> > > copies all the logs. Something broken internally in the logshpping. I
>> > > looked
>> > > online for anymore info. Apparently there was a hotfix before SP3. We
>> > > already
>> > > have sp3 on this server.
>> > >
>> > > Did anyone experience this problem?
>> > > Any idea?
>> > > Any kind of help is appreciated.
>> > >
>> > > Thanks
>> > > Uday
>> >
>> >
>> >|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> > Ignore this reply.
> > It did say that it waited for the hour that it took for the full backup to
> > fail.
> > I had the backup file. Bayut the job reported failure.
> >
> > Back to square onw. I am not sure what happened.
> > Help please
> > Ud
> >
> > "Udayasree" wrote:
> >
> >> Hi Uri
> >>
> >> I also notice something strange.
> >> The database that was doing the full backup job failed.
> >> It actually did do the backup. But the job failed saying that it can't
> >> find
> >> the network path name. The full backup job says that it ran for
> >> 1:26minutes
> >> before it failed. But i see transaction log for every 15minutes in that
> >> 1:26
> >> minutes. Usually when the ful backup starts, the transaction log back
> >> starts
> >> but never does the transaction log backup until its completed. Right.
> >> This is strange.
> >>
> >> --Uday
> >>
> >> "Uri Dimant" wrote:
> >>
> >> > Hi
> >> > Can you see how did the last LOG restore to the database? What
> >> > happened?
> >> >
> >> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> >> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> >> > > Hi
> >> > >
> >> > > I have a strange problem started happening in my log shipping. The
> >> > > database
> >> > > went to suspect/loading/read-only mode in the middle of the night.
> >> > > Can't see any particular reason in the sql srever errorlog.
> >> > >
> >> > > One thing i noticed in th msdb..backupset. This table did not have an
> >> > > entry
> >> > > for anyother transaction log that happened after the last transaction
> >> > > log
> >> > > that got applid to the database. But the logshipping copy job is fine
> >> > > and
> >> > > it
> >> > > copies all the logs. Something broken internally in the logshpping. I
> >> > > looked
> >> > > online for anymore info. Apparently there was a hotfix before SP3. We
> >> > > already
> >> > > have sp3 on this server.
> >> > >
> >> > > Did anyone experience this problem?
> >> > > Any idea?
> >> > > Any kind of help is appreciated.
> >> > >
> >> > > Thanks
> >> > > Uday
> >> >
> >> >
> >> >
>
>sql

Friday, March 30, 2012

Long time SSIS package loading

Monday, March 26, 2012

long loading times! Please help!

Friday, March 23, 2012

logshipping error

logshipping error

logshipping error

Logshipping

Logshipping

Wednesday, March 21, 2012

Logshipping

sql login permissions

Blog Archive

About Me