disks when doing mirroirng

Hi,
I'm using SQL 2005 with 2 identical servers
I want to use Mirroring between the two.
I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
services)
each server has 6 disks.
what is the best configuration of these disks ?
3 RAID1, 1 RAID1 + RAID5 ?
and where should i put things ?
e.g. OS, data files, log files, tempDB, reporting services, SSIS ..If all drives are the same size and type, for fault tolerance:
1- Mirror of two disks for OS and SQL Server
2- Create two mirrors (2 drives each) and then create a stripe with parity
between both mirrors (RAID 0). I will put the data and log files there.
This way, you can have 3 failed disks (one failed disk on each mirror) and
the system will still be online. Also RAID 0 will give you better performance.
Another option would be to create a RAID 5 with for the data and the files,
which will give you a good performance for reads (not as good for wites..)
and you will be having more space for storage for the data and the logs,
compared with the first option
"raviv762@.gmail.com" wrote:
> Hi,
> I'm using SQL 2005 with 2 identical servers
> I want to use Mirroring between the two.
> I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
> services)
> each server has 6 disks.
>
> what is the best configuration of these disks ?
> 3 RAID1, 1 RAID1 + RAID5 ?
> and where should i put things ?
> e.g. OS, data files, log files, tempDB, reporting services, SSIS ..
>|||Is your database OLTP? ... if not, you can setup your server like this:
RAID 1 (2 disks) = Os
RAID 5 (4 disks) = Data and Log files
If your data is not static, then ...
RAID 1 = Os
RAID 1 = Data Files
RAID 1 = Log Files
Using this last config. you won't have a high availability option like
RAID 5 for your data but you'll have a better performance for your
transactions and log files...
Edgardo wrote:
> If all drives are the same size and type, for fault tolerance:
> 1- Mirror of two disks for OS and SQL Server
> 2- Create two mirrors (2 drives each) and then create a stripe with parity
> between both mirrors (RAID 0). I will put the data and log files there.
> This way, you can have 3 failed disks (one failed disk on each mirror) and
> the system will still be online. Also RAID 0 will give you better performance.
> Another option would be to create a RAID 5 with for the data and the files,
> which will give you a good performance for reads (not as good for wites..)
> and you will be having more space for storage for the data and the logs,
> compared with the first option
> "raviv762@.gmail.com" wrote:
> >
> > Hi,
> >
> > I'm using SQL 2005 with 2 identical servers
> > I want to use Mirroring between the two.
> > I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
> > services)
> >
> > each server has 6 disks.
> >
> >
> > what is the best configuration of these disks ?
> > 3 RAID1, 1 RAID1 + RAID5 ?
> >
> > and where should i put things ?
> > e.g. OS, data files, log files, tempDB, reporting services, SSIS ..
> >
> >|||thanks for the quick answer.
some remarks and a question ...
1) i can not do RAID10 since my disks are not so big ... and i can not
buy bigger.
2) my data is not static, so i guess the second option is better.
the high availability will be supported by the mirroring between
servers so i'm relaxed on that.
do you have recomendation were to put the SSIS, Reporting services,
tempDB ?
jocamp3@.gmail.com wrote:
> Is your database OLTP? ... if not, you can setup your server like this:
> RAID 1 (2 disks) = Os
> RAID 5 (4 disks) = Data and Log files
> If your data is not static, then ...
> RAID 1 = Os
> RAID 1 = Data Files
> RAID 1 = Log Files
> Using this last config. you won't have a high availability option like
> RAID 5 for your data but you'll have a better performance for your
> transactions and log files...
>
> Edgardo wrote:
> > If all drives are the same size and type, for fault tolerance:
> >
> > 1- Mirror of two disks for OS and SQL Server
> > 2- Create two mirrors (2 drives each) and then create a stripe with parity
> > between both mirrors (RAID 0). I will put the data and log files there.
> >
> > This way, you can have 3 failed disks (one failed disk on each mirror) and
> > the system will still be online. Also RAID 0 will give you better performance.
> >
> > Another option would be to create a RAID 5 with for the data and the files,
> > which will give you a good performance for reads (not as good for wites..)
> > and you will be having more space for storage for the data and the logs,
> > compared with the first option
> >
> > "raviv762@.gmail.com" wrote:
> >
> > >
> > > Hi,
> > >
> > > I'm using SQL 2005 with 2 identical servers
> > > I want to use Mirroring between the two.
> > > I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
> > > services)
> > >
> > > each server has 6 disks.
> > >
> > >
> > > what is the best configuration of these disks ?
> > > 3 RAID1, 1 RAID1 + RAID5 ?
> > >
> > > and where should i put things ?
> > > e.g. OS, data files, log files, tempDB, reporting services, SSIS ..
> > >
> > >sql

disks when doing mirroirng

Hi,
I'm using SQL 2005 with 2 identical servers
I want to use Mirroring between the two.
I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
services)
each server has 6 disks.
what is the best configuration of these disks ?
3 RAID1, 1 RAID1 + RAID5 ?
and where should i put things ?
e.g. OS, data files, log files, tempDB, reporting services, SSIS ..
If all drives are the same size and type, for fault tolerance:
1- Mirror of two disks for OS and SQL Server
2- Create two mirrors (2 drives each) and then create a stripe with parity
between both mirrors (RAID 0). I will put the data and log files there.
This way, you can have 3 failed disks (one failed disk on each mirror) and
the system will still be online. Also RAID 0 will give you better performance.
Another option would be to create a RAID 5 with for the data and the files,
which will give you a good performance for reads (not as good for wites..)
and you will be having more space for storage for the data and the logs,
compared with the first option
"raviv762@.gmail.com" wrote:

> Hi,
> I'm using SQL 2005 with 2 identical servers
> I want to use Mirroring between the two.
> I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
> services)
> each server has 6 disks.
>
> what is the best configuration of these disks ?
> 3 RAID1, 1 RAID1 + RAID5 ?
> and where should i put things ?
> e.g. OS, data files, log files, tempDB, reporting services, SSIS ..
>

disks when doing mirroirng

Hi,
I'm using SQL 2005 with 2 identical servers
I want to use Mirroring between the two.
I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
services)
each server has 6 disks.
what is the best configuration of these disks ?
3 RAID1, 1 RAID1 + RAID5 ?
and where should i put things ?
e.g. OS, data files, log files, tempDB, reporting services, SSIS ..If all drives are the same size and type, for fault tolerance:
1- Mirror of two disks for OS and SQL Server
2- Create two mirrors (2 drives each) and then create a stripe with parity
between both mirrors (RAID 0). I will put the data and log files there.
This way, you can have 3 failed disks (one failed disk on each mirror) and
the system will still be online. Also RAID 0 will give you better performanc
e.
Another option would be to create a RAID 5 with for the data and the files,
which will give you a good performance for reads (not as good for wites..)
and you will be having more space for storage for the data and the logs,
compared with the first option
"raviv762@.gmail.com" wrote:

> Hi,
> I'm using SQL 2005 with 2 identical servers
> I want to use Mirroring between the two.
> I'll have on both SQL Engine, SSIS & Reporting services (no Analysis
> services)
> each server has 6 disks.
>
> what is the best configuration of these disks ?
> 3 RAID1, 1 RAID1 + RAID5 ?
> and where should i put things ?
> e.g. OS, data files, log files, tempDB, reporting services, SSIS ..
>|||Is your database OLTP? ... if not, you can setup your server like this:
RAID 1 (2 disks) = Os
RAID 5 (4 disks) = Data and Log files
If your data is not static, then ...
RAID 1 = Os
RAID 1 = Data Files
RAID 1 = Log Files
Using this last config. you won't have a high availability option like
RAID 5 for your data but you'll have a better performance for your
transactions and log files...
Edgardo wrote:[vbcol=seagreen]
> If all drives are the same size and type, for fault tolerance:
> 1- Mirror of two disks for OS and SQL Server
> 2- Create two mirrors (2 drives each) and then create a stripe with parity
> between both mirrors (RAID 0). I will put the data and log files there.
> This way, you can have 3 failed disks (one failed disk on each mirror) and
> the system will still be online. Also RAID 0 will give you better performa
nce.
> Another option would be to create a RAID 5 with for the data and the files
,
> which will give you a good performance for reads (not as good for wites..)
> and you will be having more space for storage for the data and the logs,
> compared with the first option
> "raviv762@.gmail.com" wrote:
>|||thanks for the quick answer.
some remarks and a question ...
1) i can not do RAID10 since my disks are not so big ... and i can not
buy bigger.
2) my data is not static, so i guess the second option is better.
the high availability will be supported by the mirroring between
servers so i'm relaxed on that.
do you have recomendation were to put the SSIS, Reporting services,
tempDB ?
jocamp3@.gmail.com wrote:[vbcol=seagreen]
> Is your database OLTP? ... if not, you can setup your server like this:
> RAID 1 (2 disks) = Os
> RAID 5 (4 disks) = Data and Log files
> If your data is not static, then ...
> RAID 1 = Os
> RAID 1 = Data Files
> RAID 1 = Log Files
> Using this last config. you won't have a high availability option like
> RAID 5 for your data but you'll have a better performance for your
> transactions and log files...
>
> Edgardo wrote:

Disconnected Edit in SSIS 2005

Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in SQL
Server 2005 Integration Services ? If so, What ?
Thanks.In SSIS you can accomplish editing packages without a connection to the SQL
Server Several different ways.
If you are using file system deployment you can just make sure that your
development folder for the dtsx files is something different then the folder
that the agent is executing packages from.
If you are using SQL Server deployment then every package that you are
working is essentially disconnected. You have to deploy it to the sql
server using the deploy option inside of the business intelligence studio or
a package installer.
In both cases, you do not need any type of connection to the SQL server
until you deploy. You will lose some niceties that way since you cant
connect to get column or table info.
Make sense?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
Tech Blog - www.technologyis.com
*/
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
> Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in
> SQL
> Server 2005 Integration Services ? If so, What ?
> Thanks.|||No it doesn't. Here is why,
I imported a DTS package from a SQL Server 2000 server to 2005 Integration
services on another SQL Server 2005 computer. Regardles of where I open it,
it takes at least 20 second to scroll the horizantal bar 1 inch. I am
assuming that it is trying to check the resources/connections even though
they don't exists on the new server. This is why I thought that disconnected
edit may help to speed editing the DTS package or the SSIS package since it
has been converted..........
Thanks.
"Warren Brunk" wrote:
> In SSIS you can accomplish editing packages without a connection to the SQL
> Server Several different ways.
> If you are using file system deployment you can just make sure that your
> development folder for the dtsx files is something different then the folder
> that the agent is executing packages from.
> If you are using SQL Server deployment then every package that you are
> working is essentially disconnected. You have to deploy it to the sql
> server using the deploy option inside of the business intelligence studio or
> a package installer.
> In both cases, you do not need any type of connection to the SQL server
> until you deploy. You will lose some niceties that way since you cant
> connect to get column or table info.
> Make sense?
>
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> Tech Blog - www.technologyis.com
> */
>
> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
> > Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in
> > SQL
> > Server 2005 Integration Services ? If so, What ?
> >
> > Thanks.
>
>

Disconnected Edit in SSIS 2005

Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in SQL
Server 2005 Integration Services ? If so, What ?
Thanks.In SSIS you can accomplish editing packages without a connection to the SQL
Server Several different ways.
If you are using file system deployment you can just make sure that your
development folder for the dtsx files is something different then the folder
that the agent is executing packages from.
If you are using SQL Server deployment then every package that you are
working is essentially disconnected. You have to deploy it to the sql
server using the deploy option inside of the business intelligence studio or
a package installer.
In both cases, you do not need any type of connection to the SQL server
until you deploy. You will lose some niceties that way since you cant
connect to get column or table info.
Make sense?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
Tech Blog - www.technologyis.com
*/
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
> Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in
> SQL
> Server 2005 Integration Services ? If so, What ?
> Thanks.|||No it doesn't. Here is why,
I imported a DTS package from a SQL Server 2000 server to 2005 Integration
services on another SQL Server 2005 computer. Regardles of where I open it,
it takes at least 20 second to scroll the horizantal bar 1 inch. I am
assuming that it is trying to check the resources/connections even though
they don't exists on the new server. This is why I thought that disconnected
edit may help to speed editing the DTS package or the SSIS package since it
has been converted..........
Thanks.
"Warren Brunk" wrote:

> In SSIS you can accomplish editing packages without a connection to the SQ
L
> Server Several different ways.
> If you are using file system deployment you can just make sure that your
> development folder for the dtsx files is something different then the fold
er
> that the agent is executing packages from.
> If you are using SQL Server deployment then every package that you are
> working is essentially disconnected. You have to deploy it to the sql
> server using the deploy option inside of the business intelligence studio
or
> a package installer.
> In both cases, you do not need any type of connection to the SQL server
> until you deploy. You will lose some niceties that way since you cant
> connect to get column or table info.
> Make sense?
>
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> Tech Blog - www.technologyis.com
> */
>
> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
>
>

Disconnected Edit in SSIS 2005

Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in SQL
Server 2005 Integration Services ? If so, What ?
Thanks.
In SSIS you can accomplish editing packages without a connection to the SQL
Server Several different ways.
If you are using file system deployment you can just make sure that your
development folder for the dtsx files is something different then the folder
that the agent is executing packages from.
If you are using SQL Server deployment then every package that you are
working is essentially disconnected. You have to deploy it to the sql
server using the deploy option inside of the business intelligence studio or
a package installer.
In both cases, you do not need any type of connection to the SQL server
until you deploy. You will lose some niceties that way since you cant
connect to get column or table info.
Make sense?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
Tech Blog - www.technologyis.com
*/
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
> Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in
> SQL
> Server 2005 Integration Services ? If so, What ?
> Thanks.
|||No it doesn't. Here is why,
I imported a DTS package from a SQL Server 2000 server to 2005 Integration
services on another SQL Server 2005 computer. Regardles of where I open it,
it takes at least 20 second to scroll the horizantal bar 1 inch. I am
assuming that it is trying to check the resources/connections even though
they don't exists on the new server. This is why I thought that disconnected
edit may help to speed editing the DTS package or the SSIS package since it
has been converted..........
Thanks.
"Warren Brunk" wrote:

> In SSIS you can accomplish editing packages without a connection to the SQL
> Server Several different ways.
> If you are using file system deployment you can just make sure that your
> development folder for the dtsx files is something different then the folder
> that the agent is executing packages from.
> If you are using SQL Server deployment then every package that you are
> working is essentially disconnected. You have to deploy it to the sql
> server using the deploy option inside of the business intelligence studio or
> a package installer.
> In both cases, you do not need any type of connection to the SQL server
> until you deploy. You will lose some niceties that way since you cant
> connect to get column or table info.
> Make sense?
>
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> Tech Blog - www.technologyis.com
> */
>
> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
>
>
sql

Disconnect All Ussers But Me

I have setup a small SSIS package that will regularly delete my log files by detaching the database, removing the file and then reattaching it.

Problem I'm having is that there is almost always at least one other connection to the database and I have to kill it for this to work.

Is there any TSQL command that allows me to shut down all open connections except the one the command is coming from?

There is no command like that. But you could use ALTER DATABASE to set the database in single user or restricted user mode. This may or may not work depending on the permissions of the login used by the SSIS package and how often the clients reconnect etc. Check out the ALTER DATABASE topic and see.

Btw, why are you recreating the log file periodically? What is the purpose?

|||

just to add what Umachander has already told.. read about Alter Database and Singler_User in BOL first

ALTER DATABASE SomeDatabase SET SiNGLE_USER WITH ROLLBACK IMMEDIATE;

and ofcourse answer the abovementioned questions also... very risky and unethical method of truncating and shrinking log.. not atall recommended and you should not do this. there are another /professional approach to control the growth and size of log file.

Refer this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1272445&SiteID=1

Madhu

|||Thank you, I'll check those links out.

As for the reason, right now I inherited a database that is running some heavy SSIS packages, every time these run they do a lot of copying and deleting, in the end they inflate the log files drastically. However we don't really need the log files at all, we have all the data ready to be loaded in backup tapes should anything drastic happen.

I bet the SSIS packages can use a lot of optimization but for the time being I'm not in control of these and was instructed to take care of the logs ASAP. I already did this process manually and it worked so I figured it may be an OK temporary solution to run weekly until I got a hold of what is truly going on in this database and how to optimize it.

Heck, for the purposes of this project, if it was possible to disable logging as a permanent option, I'd do it.
|||If you aren't worried about he log files, then set the database recovery model to "simple". That will keep the logs much smaller and increase the speed of updates to the tables.

The way to shrink the log files is to use a maintenance plan. You can back it up and shrink the logs at night, which is what you are trying to do anyway.

Disconnect All Ussers But Me

I have setup a small SSIS package that will regularly delete my log files by detaching the database, removing the file and then reattaching it.

Problem I'm having is that there is almost always at least one other connection to the database and I have to kill it for this to work.

Is there any TSQL command that allows me to shut down all open connections except the one the command is coming from?

There is no command like that. But you could use ALTER DATABASE to set the database in single user or restricted user mode. This may or may not work depending on the permissions of the login used by the SSIS package and how often the clients reconnect etc. Check out the ALTER DATABASE topic and see.

Btw, why are you recreating the log file periodically? What is the purpose?

|||

just to add what Umachander has already told.. read about Alter Database and Singler_User in BOL first

ALTER DATABASE SomeDatabase SET SiNGLE_USER WITH ROLLBACK IMMEDIATE;

and ofcourse answer the abovementioned questions also... very risky and unethical method of truncating and shrinking log.. not atall recommended and you should not do this. there are another /professional approach to control the growth and size of log file.

Refer this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1272445&SiteID=1

Madhu

|||Thank you, I'll check those links out.

As for the reason, right now I inherited a database that is running some heavy SSIS packages, every time these run they do a lot of copying and deleting, in the end they inflate the log files drastically. However we don't really need the log files at all, we have all the data ready to be loaded in backup tapes should anything drastic happen.

I bet the SSIS packages can use a lot of optimization but for the time being I'm not in control of these and was instructed to take care of the logs ASAP. I already did this process manually and it worked so I figured it may be an OK temporary solution to run weekly until I got a hold of what is truly going on in this database and how to optimize it.

Heck, for the purposes of this project, if it was possible to disable logging as a permanent option, I'd do it.|||If you aren't worried about he log files, then set the database recovery model to "simple". That will keep the logs much smaller and increase the speed of updates to the tables.

The way to shrink the log files is to use a maintenance plan. You can back it up and shrink the logs at night, which is what you are trying to do anyway.

Disabling the TransactionLog

I have an SSIS task that transforms 70 million rows of data nightly.

The data is dumped and imported fresh every day.

Obviously I don't want my production Transaction Log getting cluttered up with 70 million rows of transaction logs daily.

Is there any way to avoid logging to the transaction log with an SSIS task?Are you using bulk insert or are you running 70 million insert statements? There is a varitety of ways to truncate / shrink the transaction log after you are done processing records.|||

Greg Van Mullem wrote:

Are you using bulk insert or are you running 70 million insert statements? There is a varitety of ways to truncate / shrink the transaction log after you are done processing records.

I am going to be using bulk inserts.|||

You can either put your database into simple recovery which will provide 0 recovery and then put back into "full" mode and do a full backup after your finished.

With "simple" you will only be able to recover from your previous backup up to the point you flipped into simple mode

The other option is to use BULK Logged mode. This mode logs extent allocations, once completed you should put your database back into full mode at which point when you back up the log all pages/extents changed during the bulk logged period are written to the backup.

Your transaction log will always grow until a in simple mode a checkpoint occurs at which point it is emptied of commited transactions, or in bulk logged/full the transaction log is backed up. If you have 1 transaction for all the work then the transaction log will need to be big enough to handle all the changes made in the transaction

|||Have you consided solving this problem with a hardware purchase instead of software tweaks? Buy big disk drives and let the transaction log explode in size. If it's too slow then buy faster disk drives or servers.

This is often the most cost effective approach these days. More often than not, when I run the numbers on an issue like this, an expensive hardware purchase turns out be cheaper, faster and easier! Just a thought.

Later,
Greg Van Mullem|||

Use the batchsize parameter (I hope bulkinsert has one, as the bcp utility has one). This will leasd into a checkpoint. If you now define an alert for the database (log is used by e.g. 75 percent) and you define a job which will dump the transaction log, you should have no problems with it.

Maybe you have to deal with the percent value. That's it.

The advantage is, that you do not change the recovery model of the database and even your inserts will be part of the backup.

Regards

Norbert

Disabling SQLISPackage start/finish events sent to eventlog

I'm running my SSIS packages from a scheduler (WindowsService) that I wrote in .Net. For the logging of the SSIS events I only use te SSIS Log provider for SQL Server. Nevertheless, the package run start and stop events (and execution failures) are still logged in the Windows Event Log. Is there a way to stop SSIS from writing this event-log entries?

Hi,

i have a scheduled package that runs every one minute and my eventviewer/application is full of these start/finish events.

i would like to see the resolution for this issue.

TIA

Disabling SQLISPackage start/finish events sent to eventlog

I'm running my SSIS packages from a scheduler (WindowsService) that I wrote in .Net. For the logging of the SSIS events I only use te SSIS Log provider for SQL Server. Nevertheless, the package run start and stop events (and execution failures) are still logged in the Windows Event Log. Is there a way to stop SSIS from writing this event-log entries?

Hi,

i have a scheduled package that runs every one minute and my eventviewer/application is full of these start/finish events.

i would like to see the resolution for this issue.

TIA

Disable SSIS Studio validations?

Is there any way to disable the validations within the package upon startup of the SSIS studio? We have a few really large packages that can take almost an hour to validate, since the packages could be pointed to different environments (depending on each developer). The alternative (which could get messy) is to alter the *.dtsx file to point the connections to the correct DB before starting them up in studio.

Any ideas?Try setting DelayValidation=TRUE on the package.
-Jamie|||You can use configurations so that the connections point to the correct place on any server (as long as the configuration is valid and that way you don't have to alter the dtsx file directly).

You can switch into offline mode before opening the package.

You can use DelayValidation set to true.

HTH,
Matt

Disable Event Logging to Windows Application Log?

Hi,

We are starting to work with SSIS in our production environment & due to support issues; we are trying to get rid of the "Package xxx started" log entries inside of the Windows Application Event Log...

So far, I have tried many different things, including setting the LoggingMode to "Disabled", as well as adding a new logging reference with a different destination... All of which still do not get rid of the extra log entries...

Is this possible? & does anyone know how to get this done?

Thanks!

I am having this same problem. Have you had any luck with this?

I have LoggingMode disabled in the properties of the package, I don't have anything checked on the Configure SSIS Logs screen in the Containers list nor on the Providers and Logs tab and the Details tab. The packages are being run from a SQL Server Agent job.

Thanks.

Bobette

|||

I move the thread to SQL Server Tools general because this looks like and SQL Agent problem

Thanks,
Ovidiu

|||

Hi,

Unfortunately I still haven't found a way to get this accomplished... At least I'm not the only one with the same problem.. . :) Thanks Bobette..

For now, we are simply living with the problem & have built a custom app that queries the event log for error's only... But this isn't a solution, just a band-aid...

~James

|||

Hopefully someone that knows will find our posting here. Thanks for the quick reply!

bobette

|||

After I read your poost twice I realized this is a SSIS thing.

The current implementation will always post the "Package xxx started" event and there is no way to disable this message

Thanks,
Ovidiu Burlacu

|||

Thanks! At least I know to quit trying to figure it out.

Bobette

Disable Event Logging to Windows Application Log?

Hi,

We are starting to work with SSIS in our production environment & due to support issues; we are trying to get rid of the "Package xxx started" log entries inside of the Windows Application Event Log...

So far, I have tried many different things, including setting the LoggingMode to "Disabled", as well as adding a new logging reference with a different destination... All of which still do not get rid of the extra log entries...

Is this possible? & does anyone know how to get this done?

Thanks!

I am having this same problem. Have you had any luck with this?

I have LoggingMode disabled in the properties of the package, I don't have anything checked on the Configure SSIS Logs screen in the Containers list nor on the Providers and Logs tab and the Details tab. The packages are being run from a SQL Server Agent job.

Thanks.

Bobette

|||

I move the thread to SQL Server Tools general because this looks like and SQL Agent problem

Thanks,
Ovidiu

|||

Hi,

Unfortunately I still haven't found a way to get this accomplished... At least I'm not the only one with the same problem.. . :) Thanks Bobette..

For now, we are simply living with the problem & have built a custom app that queries the event log for error's only... But this isn't a solution, just a band-aid...

~James

|||

Hopefully someone that knows will find our posting here. Thanks for the quick reply!

bobette

|||

After I read your poost twice I realized this is a SSIS thing.

The current implementation will always post the "Package xxx started" event and there is no way to disable this message

Thanks,
Ovidiu Burlacu

|||

Thanks! At least I know to quit trying to figure it out.

Bobette

Disable Event Logging to Windows Application Log?

Hi,

We are starting to work with SSIS in our production environment & due to support issues; we are trying to get rid of the "Package xxx started" log entries inside of the Windows Application Event Log...

So far, I have tried many different things, including setting the LoggingMode to "Disabled", as well as adding a new logging reference with a different destination... All of which still do not get rid of the extra log entries...

Is this possible? & does anyone know how to get this done?

Thanks!

I am having this same problem. Have you had any luck with this?

I have LoggingMode disabled in the properties of the package, I don't have anything checked on the Configure SSIS Logs screen in the Containers list nor on the Providers and Logs tab and the Details tab. The packages are being run from a SQL Server Agent job.

Thanks.

Bobette

|||

I move the thread to SQL Server Tools general because this looks like and SQL Agent problem

Thanks,
Ovidiu

|||

Hi,

Unfortunately I still haven't found a way to get this accomplished... At least I'm not the only one with the same problem.. . :) Thanks Bobette..

For now, we are simply living with the problem & have built a custom app that queries the event log for error's only... But this isn't a solution, just a band-aid...

~James

|||

Hopefully someone that knows will find our posting here. Thanks for the quick reply!

bobette

|||

After I read your poost twice I realized this is a SSIS thing.

The current implementation will always post the "Package xxx started" event and there is no way to disable this message

Thanks,
Ovidiu Burlacu

|||

Thanks! At least I know to quit trying to figure it out.

Bobette