Numerous SSIS and SSAS problems

First, in SSIS I cannot delete the data viewer from a connection between two tasks in the data flow without crashing BIDS. Even if I delete the connector or the tasks, BIDS crashes.

Second, in SSAS I accidentally deleted an attribute and the undo does not work in SSAS/BIDS. I put the attribute back and the dim won't deploy. It just runs forever.

Finally, in ProClarity my drill to detail is not displaying the fact rows I want. Plus the column headers are not easy to read. How can I make SSAS reference the correct data and corresponding column headers.

TJ

> Second, in SSAS I accidentally deleted an attribute and the undo does not work in SSAS/BIDS.

> I put the attribute back and the dim won't deploy. It just runs forever.

Indeed, undo is not yet implemented. After putting back the attribute, when you deploy, do you get an error or the deployment takes a long time ? If the deployment takes a long time, it's probably because the data is re-processed (although you put back the attribute, I believe its ID changed and will trigger a re-processing of the dimension). To stop re-processing on each deployment, right click on the project node -> Properties -> Deployment tab -> Processing Option.

Things to check/recover when putting back the attribute: was the attribute involved in hierarchies (was it source of levels in hierarchies ?) or attribute relationships or was used as granularity in measure groups ? (by default, the key attribute is the granularity)

Adrian Dumitrascu

Numerous event 17137 in event log

Hello,
I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
get an event 17137 "Starting database MyDB" at each connection to my
database, which is a very frequent event.
The problem is that the application event log of the machine is full of this
event, with the consequence on old servers like Windows 2000 to get a message
saying the log is full and you have to empty it.
I would like to know how I can turn off the logging of SQL SERVER event 17137.
--
Olivier GIL
LAFON SAOliver GIL,
Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF, thus
keeping MyDB open by:
ALTER DATABASE MyDB SET AUTO_CLOSE OFF
That should get rid of the messages and make your accesses to MyDB run more
quickly.
RLF
"Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
> Hello,
> I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
> get an event 17137 "Starting database MyDB" at each connection to my
> database, which is a very frequent event.
> The problem is that the application event log of the machine is full of
> this
> event, with the consequence on old servers like Windows 2000 to get a
> message
> saying the log is full and you have to empty it.
> I would like to know how I can turn off the logging of SQL SERVER event
> 17137.
> --
> Olivier GIL
> LAFON SA|||Hello,
AUTO_CLOSE OFF actually solves the problem.
It is surprising this option not being the default value for a CREATE
DATABASE command, knowing that the performance is better in that case.
--
Olivier GIL
LAFON SA
"Russell Fields" wrote:
> Oliver GIL,
> Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF, thus
> keeping MyDB open by:
> ALTER DATABASE MyDB SET AUTO_CLOSE OFF
> That should get rid of the messages and make your accesses to MyDB run more
> quickly.
> RLF
> "Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
> news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
> > Hello,
> >
> > I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
> > get an event 17137 "Starting database MyDB" at each connection to my
> > database, which is a very frequent event.
> >
> > The problem is that the application event log of the machine is full of
> > this
> > event, with the consequence on old servers like Windows 2000 to get a
> > message
> > saying the log is full and you have to empty it.
> >
> > I would like to know how I can turn off the logging of SQL SERVER event
> > 17137.
> >
> > --
> > Olivier GIL
> > LAFON SA
>
>|||Hi Olivier,
Regarding your concerns, you can find the following description regarding
AUTO_CLOSE OFF in SQL Server Books Online:
AUTO_CLOSE Default Value:
ON for all databases when using Microsoft SQL Server 2000 Desktop Engine or
SQL Server 2005 Express Edition, and OFF for all other editions, regardless
of operating system.
(REF: http://msdn2.microsoft.com/en-us/library/ms190249.aspx)
"The AUTO_CLOSE option is useful for desktop databases because it allows
database files to be managed as normal files. They can be moved, copied to
make backups, or even e-mailed to other users. The AUTO_CLOSE option should
not be used for databases accessed by an application that repeatedly makes
and breaks connections to SQL Server. The overhead of closing and reopening
the database between each connection will impair performance."
(REF: http://technet.microsoft.com/en-us/library/aa933082(SQL.80).aspx)
Please feel free to let us know if you have any other questions or
concerns. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hello Olivier,
AUTO_CLOSE option if ON by default only for MSDE and Express Editions.
I suggest you to take a look at the following link for further info:
http://msdn2.microsoft.com/en-us/library/ms190249.aspx
--
Ekrem Ã?nsoy
"Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
news:C20E229A-83E5-4D09-9B1F-F830E84EA438@.microsoft.com...
> Hello,
> AUTO_CLOSE OFF actually solves the problem.
>
> It is surprising this option not being the default value for a CREATE
> DATABASE command, knowing that the performance is better in that case.
> --
> Olivier GIL
> LAFON SA
>
> "Russell Fields" wrote:
>> Oliver GIL,
>> Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF,
>> thus
>> keeping MyDB open by:
>> ALTER DATABASE MyDB SET AUTO_CLOSE OFF
>> That should get rid of the messages and make your accesses to MyDB run
>> more
>> quickly.
>> RLF
>> "Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
>> news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
>> > Hello,
>> >
>> > I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and
>> > I
>> > get an event 17137 "Starting database MyDB" at each connection to my
>> > database, which is a very frequent event.
>> >
>> > The problem is that the application event log of the machine is full of
>> > this
>> > event, with the consequence on old servers like Windows 2000 to get a
>> > message
>> > saying the log is full and you have to empty it.
>> >
>> > I would like to know how I can turn off the logging of SQL SERVER event
>> > 17137.
>> >
>> > --
>> > Olivier GIL
>> > LAFON SA
>>

Numerous event 17137 in event log

Hello,
I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
get an event 17137 "Starting database MyDB" at each connection to my
database, which is a very frequent event.
The problem is that the application event log of the machine is full of this
event, with the consequence on old servers like Windows 2000 to get a messag
e
saying the log is full and you have to empty it.
I would like to know how I can turn off the logging of SQL SERVER event 1713
7.
Olivier GIL
LAFON SAOliver GIL,
Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF, thus
keeping MyDB open by:
ALTER DATABASE MyDB SET AUTO_CLOSE OFF
That should get rid of the messages and make your accesses to MyDB run more
quickly.
RLF
"Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
> Hello,
> I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
> get an event 17137 "Starting database MyDB" at each connection to my
> database, which is a very frequent event.
> The problem is that the application event log of the machine is full of
> this
> event, with the consequence on old servers like Windows 2000 to get a
> message
> saying the log is full and you have to empty it.
> I would like to know how I can turn off the logging of SQL SERVER event
> 17137.
> --
> Olivier GIL
> LAFON SA|||Hello,
AUTO_CLOSE OFF actually solves the problem.
It is surprising this option not being the default value for a CREATE
DATABASE command, knowing that the performance is better in that case.
Olivier GIL
LAFON SA
"Russell Fields" wrote:

> Oliver GIL,
> Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF, thus
> keeping MyDB open by:
> ALTER DATABASE MyDB SET AUTO_CLOSE OFF
> That should get rid of the messages and make your accesses to MyDB run mor
e
> quickly.
> RLF
> "Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
> news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
>
>|||Hi Olivier,
Regarding your concerns, you can find the following description regarding
AUTO_CLOSE OFF in SQL Server Books Online:
AUTO_CLOSE Default Value:
ON for all databases when using Microsoft SQL Server 2000 Desktop Engine or
SQL Server 2005 Express Edition, and OFF for all other editions, regardless
of operating system.
(REF: http://msdn2.microsoft.com/en-us/library/ms190249.aspx)
"The AUTO_CLOSE option is useful for desktop databases because it allows
database files to be managed as normal files. They can be moved, copied to
make backups, or even e-mailed to other users. The AUTO_CLOSE option should
not be used for databases accessed by an application that repeatedly makes
and breaks connections to SQL Server. The overhead of closing and reopening
the database between each connection will impair performance."
(REF: http://technet.microsoft.com/en-us/library/aa933082(SQL.80).aspx)
Please feel free to let us know if you have any other questions or
concerns. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hello Olivier,
AUTO_CLOSE option if ON by default only for MSDE and Express Editions.
I suggest you to take a look at the following link for further info:
http://msdn2.microsoft.com/en-us/library/ms190249.aspx
Ekrem ?nsoy
"Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
news:C20E229A-83E5-4D09-9B1F-F830E84EA438@.microsoft.com...[vbcol=seagreen]
> Hello,
> AUTO_CLOSE OFF actually solves the problem.
>
> It is surprising this option not being the default value for a CREATE
> DATABASE command, knowing that the performance is better in that case.
> --
> Olivier GIL
> LAFON SA
>
> "Russell Fields" wrote:
>

Numerous event 17137 in event log

Hello,
I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
get an event 17137 "Starting database MyDB" at each connection to my
database, which is a very frequent event.
The problem is that the application event log of the machine is full of this
event, with the consequence on old servers like Windows 2000 to get a message
saying the log is full and you have to empty it.
I would like to know how I can turn off the logging of SQL SERVER event 17137.
Olivier GIL
LAFON SA
Oliver GIL,
Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF, thus
keeping MyDB open by:
ALTER DATABASE MyDB SET AUTO_CLOSE OFF
That should get rid of the messages and make your accesses to MyDB run more
quickly.
RLF
"Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
> Hello,
> I am using SQL SERVER 2005 EXPRESS SP1 with an ASP.NET application, and I
> get an event 17137 "Starting database MyDB" at each connection to my
> database, which is a very frequent event.
> The problem is that the application event log of the machine is full of
> this
> event, with the consequence on old servers like Windows 2000 to get a
> message
> saying the log is full and you have to empty it.
> I would like to know how I can turn off the logging of SQL SERVER event
> 17137.
> --
> Olivier GIL
> LAFON SA
|||Hello,
AUTO_CLOSE OFF actually solves the problem.
It is surprising this option not being the default value for a CREATE
DATABASE command, knowing that the performance is better in that case.
Olivier GIL
LAFON SA
"Russell Fields" wrote:

> Oliver GIL,
> Is your MyDB in AUTO_CLOSE = ON mode? If so, you can turn this OFF, thus
> keeping MyDB open by:
> ALTER DATABASE MyDB SET AUTO_CLOSE OFF
> That should get rid of the messages and make your accesses to MyDB run more
> quickly.
> RLF
> "Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
> news:D985059D-D4CD-490B-8299-FB4924A4FF7F@.microsoft.com...
>
>
|||Hi Olivier,
Regarding your concerns, you can find the following description regarding
AUTO_CLOSE OFF in SQL Server Books Online:
AUTO_CLOSE Default Value:
ON for all databases when using Microsoft SQL Server 2000 Desktop Engine or
SQL Server 2005 Express Edition, and OFF for all other editions, regardless
of operating system.
(REF: http://msdn2.microsoft.com/en-us/library/ms190249.aspx)
"The AUTO_CLOSE option is useful for desktop databases because it allows
database files to be managed as normal files. They can be moved, copied to
make backups, or even e-mailed to other users. The AUTO_CLOSE option should
not be used for databases accessed by an application that repeatedly makes
and breaks connections to SQL Server. The overhead of closing and reopening
the database between each connection will impair performance."
(REF: http://technet.microsoft.com/en-us/library/aa933082(SQL.80).aspx)
Please feel free to let us know if you have any other questions or
concerns. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hello Olivier,
AUTO_CLOSE option if ON by default only for MSDE and Express Editions.
I suggest you to take a look at the following link for further info:
http://msdn2.microsoft.com/en-us/library/ms190249.aspx
Ekrem ?nsoy
"Olivier GIL" <ogil@.newsgroup.nospam> wrote in message
news:C20E229A-83E5-4D09-9B1F-F830E84EA438@.microsoft.com...[vbcol=seagreen]
> Hello,
> AUTO_CLOSE OFF actually solves the problem.
>
> It is surprising this option not being the default value for a CREATE
> DATABASE command, knowing that the performance is better in that case.
> --
> Olivier GIL
> LAFON SA
>
> "Russell Fields" wrote:
sql

Number of SQL Client is . . .

SQLServer 10Client; the number 10 is:
- a physical limit of connections (ADODB.Connection)?
- a licences limit ?
- a PCs limit?
- a number of processes limit?
- a number of served query and the next queries are queued?
Some ideas?
Tnx in advance.
Sorry for my bad english...
Alfredo.A licenses limit.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alfredo Volpari" <alfredo@.siam.it> wrote in message
news:bq4jds$r8n$1@.fata.cs.interbusiness.it...
> SQLServer 10Client; the number 10 is:
> - a physical limit of connections (ADODB.Connection)?
> - a licences limit ?
> - a PCs limit?
> - a number of processes limit?
> - a number of served query and the next queries are queued?
> Some ideas?
> Tnx in advance.
> Sorry for my bad english...
> Alfredo.
>

number of connections

Hi,
I would like to know if I can over the limit of user connection using the
sqlserver 2005, that is 32,767 user connections(I know that I need some
hardware resource as memory, etc).
Thanks,
Serge
"Serge" <Serge@.discussions.microsoft.com> wrote in message
news:160EB448-A632-423D-BF14-7A372277BBF3@.microsoft.com...
> Hi,
> I would like to know if I can over the limit of user connection using the
> sqlserver 2005, that is 32,767 user connections(I know that I need some
> hardware resource as memory, etc).
>
I don't know of anyway.
But I'd be surprsied if you ever really needed to. That would be a MASSIVE
system that required that many simultaneous connections.
I'm curious what you're end-goal is.

> Thanks,
> Serge
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

number of connections

Hi,
I would like to know if I can over the limit of user connection using the
sqlserver 2005, that is 32,767 user connections(I know that I need some
hardware resource as memory, etc).
Thanks,
Serge"Serge" <Serge@.discussions.microsoft.com> wrote in message
news:160EB448-A632-423D-BF14-7A372277BBF3@.microsoft.com...
> Hi,
> I would like to know if I can over the limit of user connection using the
> sqlserver 2005, that is 32,767 user connections(I know that I need some
> hardware resource as memory, etc).
>
I don't know of anyway.
But I'd be surprsied if you ever really needed to. That would be a MASSIVE
system that required that many simultaneous connections.
I'm curious what you're end-goal is.

> Thanks,
> Serge
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.htmlsql

number of connections

Hi,
I would like to know if I can over the limit of user connection using the
sqlserver 2005, that is 32,767 user connections(I know that I need some
hardware resource as memory, etc).
Thanks,
Serge"Serge" <Serge@.discussions.microsoft.com> wrote in message
news:160EB448-A632-423D-BF14-7A372277BBF3@.microsoft.com...
> Hi,
> I would like to know if I can over the limit of user connection using the
> sqlserver 2005, that is 32,767 user connections(I know that I need some
> hardware resource as memory, etc).
>
I don't know of anyway.
But I'd be surprsied if you ever really needed to. That would be a MASSIVE
system that required that many simultaneous connections.
I'm curious what you're end-goal is.
> Thanks,
> Serge
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Number of Connection

Hi Friends,
I wants to know , number of sql server connection is active and how
close the connection explicitily?
Please help me
Thanks
Prakash.rhI
1) Run sp_who 'active'
2) Use KILL command
<prakashaspnet@.gmail.com> wrote in message
news:1153891993.761054.305280@.i42g2000cwa.googlegroups.com...
> Hi Friends,
> I wants to know , number of sql server connection is active and how
> close the connection explicitily?
> Please help me
> Thanks
> Prakash.r
>

Number of Connection

Hi Friends,
I wants to know , number of sql server connection is active and how
close the connection explicitily?
Please help me
Thanks
Prakash.rhI
1) Run sp_who 'active'
2) Use KILL command
<prakashaspnet@.gmail.com> wrote in message
news:1153891993.761054.305280@.i42g2000cwa.googlegroups.com...
> Hi Friends,
> I wants to know , number of sql server connection is active and how
> close the connection explicitily?
> Please help me
> Thanks
> Prakash.r
>