environment variables

Well, having only one disk partition, and only one directory, and running only one application probably ROCKS too, at least for that one application :)
But if you're unfortunate enough to be required to use multiple applications, you might be saddened by certain aspects of environment variables, such as them living in one globally competitive namespace, or them being not covered by the NT security model (AFAIK).
But I grant you, that they solve the portability problem with package configurations, so I was happy to use them nonetheless.
I'd use environment variables (or any other hack in all likelihood), if I could find a solution for the lack of reusability in SSIS -- that is driving us to move as much code as possible outside of SSIS for maintainability. :(

We're always looking for product feedback; what are the aspects of your packages that you wish you could re-use? (Also, it sounds like you're replying to another thread... Was this post misplaced?)

|||

Cim Ryan wrote:

We're always looking for product feedback; what are the aspects of your packages that you wish you could re-use? (Also, it sounds like you're replying to another thread... Was this post misplaced?)

Cim/Perry,
I'm jumping in on your thread here, sorry about that.

Here's a list of things that could, IMO, be made reusable:
-Data-Flows (the most obvious one)
-Tasks (e.g. an Execute SQL task that calls a auditing sproc)
-A sequence container that carries out a single unit of work
-A For/ForEach Loop (including all tasks within it)
-A configured component
-A group of configured components (http://blogs.conchango.com/jamiethomson/archive/2005/05/26/1470.aspx)
The important point to make is that they shouldn't just be made reusable in the same package, they should be reusable in ANY package. In that sense, each one of them could be a deployable object. Currently the only deployable object is a package - why should that be the case? Why not deploy (for example) a task, or even a component, and then use that in any package?

-Jamie

|||To add to Jamie's excellent list at the lower level,
expressions
I say this because copying and pasting transformations from one Derived Column task to another is tedious, and I tend to believe that copy&paste leads to poor maintainability and scalability.

|||Also, the Aggregate defaults most columns to Group By, it usually misses one out of a long list, and for some reason it always misses the ErrorCode and ErrorNumber, when they are added at the bottom of the output column list from a Lookup Error, so when you finish checking all the columns to group by, you track the Validation error back and find that the Aggregate left those columns unspecified -- which means it is in an invalid state -- so you have to manually set those to Group By.
Actually, sounds more like a bug than an RFE to me, but I don't care what list it goes on if it gets fixed :)
sql

Entreprise Manager behaviour

Dear all,
I've got the following scenario:
-Got two EM instances running at the same time. The same view on the right
for both, this is, Tables.
From EM1 I create a table called T. After that I'm going to EM2 and refresh.
Fine because I am seeing the same object.
-Come back to EM1 and drop T object and create again another T object but
different, with more fields. When this time I'm going to EM2 and I do drop
action I've dropped the most new object not the old one when I was waiting a
messagebox or something like that warning me that I am deleting an object
which is different than I though.
Jezz, how can I do for to change this behaviour?
Any help or comment woud be very appreciated.
Current location: Alicante (ES)The behaviour you describe is exactly os should be expected.
When you drop a table in EM, EM actually executes a T-SQL drop table
statement.
"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
> Dear all,
> I've got the following scenario:
> -Got two EM instances running at the same time. The same view on the right
> for both, this is, Tables.
> From EM1 I create a table called T. After that I'm going to EM2 and
> refresh.
> Fine because I am seeing the same object.
> -Come back to EM1 and drop T object and create again another T object but
> different, with more fields. When this time I'm going to EM2 and I do drop
> action I've dropped the most new object not the old one when I was waiting
> a
> messagebox or something like that warning me that I am deleting an object
> which is different than I though.
> Jezz, how can I do for to change this behaviour?
> Any help or comment woud be very appreciated.
> --
> Current location: Alicante (ES)|||Hi Stephany,
Yes, I perfectly know it, but I was wondering myself how to change
thanks anyway
--
Current location: Alicante (ES)
"Stephany Young" wrote:

> The behaviour you describe is exactly os should be expected.
> When you drop a table in EM, EM actually executes a T-SQL drop table
> statement.
>
> "Enric" <vtam13@.terra.es.(donotspam)> wrote in message
> news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
>
>|||> Jezz, how can I do for to change this behaviour?
Stop using EM at all :-))
"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
> Dear all,
> I've got the following scenario:
> -Got two EM instances running at the same time. The same view on the right
> for both, this is, Tables.
> From EM1 I create a table called T. After that I'm going to EM2 and
> refresh.
> Fine because I am seeing the same object.
> -Come back to EM1 and drop T object and create again another T object but
> different, with more fields. When this time I'm going to EM2 and I do drop
> action I've dropped the most new object not the old one when I was waiting
> a
> messagebox or something like that warning me that I am deleting an object
> which is different than I though.
> Jezz, how can I do for to change this behaviour?
> Any help or comment woud be very appreciated.
> --
> Current location: Alicante (ES)|||What would you like to change? Do you want to drop objects without actually
dropping them?
What are you trying to achieve?
ML
http://milambda.blogspot.com/|||In fact, I hope that in early period of time EM will be living and sharing
time with Sql Management Studio
--
Current location: Alicante (ES)
"Uri Dimant" wrote:

> Stop using EM at all :-))
> "Enric" <vtam13@.terra.es.(donotspam)> wrote in message
> news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
>
>|||No, I hope that EM works fine. Did it make sense such scenario? I think so.
--
Current location: Alicante (ES)
"ML" wrote:

> What would you like to change? Do you want to drop objects without actuall
y
> dropping them?
> What are you trying to achieve?
> ML
> --
> http://milambda.blogspot.com/|||Great, trade in your Yugo for a Kia. Management Studio is certainly a
better tool than Enterprise Manager in general, but it still shares a lot of
its flaws and limitations.
Hopefully, at least, you'll learn commands like DROP TABLE and BEGIN TRAN /
COMMIT TRAN, instead of pointing and clicking yourself to inevitable
disaster.

> In fact, I hope that in early period of time EM will be living and sharing
> time with Sql Management Studio|||drop and commit? I unfortunately know them
--
Current location: Alicante (ES)
"Aaron Bertrand [SQL Server MVP]" wrote:

> Great, trade in your Yugo for a Kia. Management Studio is certainly a
> better tool than Enterprise Manager in general, but it still shares a lot
of
> its flaws and limitations.
> Hopefully, at least, you'll learn commands like DROP TABLE and BEGIN TRAN
/
> COMMIT TRAN, instead of pointing and clicking yourself to inevitable
> disaster.
>
>
>
>
>
>|||> drop and commit? I unfortunately know them
Well, I should have said, learn to use them. I would much rather write DROP
TABLE and/or wrap my commands in transactions than blindly trust what some
GUI is going to do. Especially when I'm doing some backhanded thing like
just trying to see what will happen when I bounce quickly between two open
apps on the same machine...
A

Enterprise to Standard downgrade

We have a SQL 2000 server running Enterprise Edition. We also have a separate machine running SQL 2000, Standard edition. We then detached the database from the Enterprise server, copied the MDF and LDF files to the Standard server and reattached. Currently, a program running on the Standard Edition server is returning an error message when trying to access "systables". The questions are as follows:
1) is this error a result of the copy process?
2) is this a recoverable error, and if so, how?
3) are there any other problems and side-effects of which we need to be aware?I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:

The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.

This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||The default database for the user is the same on both servers. Any other ideas? Is there any other information I could give that might be of assistance?

Originally posted by bpdWork
I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:

The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.

This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||1) Are you sure the database you moved has the table systables, and that it is not in a different database?

2) Does the user account being used by the application have SELECT (etc) permissions for the table?

The exact error message might be helpful.|||check the service pack level|||We've found the issue. Basically, an error was made during the installation of the software. To everyone, thanks for the help.

Enterprise Mgr Snap-In Issue

I have been running SQL Server 2000, client tools only.
i installed SQL Server Express (and associated .NET
framework upgrade) to take a look.
I then uninstalled sql server express and went back to
version 1.1 of .NET framework.
My query analyzer works fine, however when i try to load
Enterprise Manager, it says:
Snap-in failed to initialize.
Name: Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I have looked through the knowledge base articles and
have not found one specific to my situation.
I have uninstalled/reinstalled sql server 2000 (and
therefore, MDAC as well) and I am running into the same
issues.
Any help is appreciated.
Did you try regsvr32 c:\...\...\sqldmo.dll
http://www.aspfaq.com/
(Reverse address to reply.)
"RR" <anonymous@.discussions.microsoft.com> wrote in message
news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
> I have been running SQL Server 2000, client tools only.
> i installed SQL Server Express (and associated .NET
> framework upgrade) to take a look.
> I then uninstalled sql server express and went back to
> version 1.1 of .NET framework.
> My query analyzer works fine, however when i try to load
> Enterprise Manager, it says:
> Snap-in failed to initialize.
> Name: Microsoft SQL Enterprise Manager
> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
> I have looked through the knowledge base articles and
> have not found one specific to my situation.
> I have uninstalled/reinstalled sql server 2000 (and
> therefore, MDAC as well) and I am running into the same
> issues.
> Any help is appreciated.
|||I just tried it with the same result.

>--Original Message--
>Did you try regsvr32 c:\...\...\sqldmo.dll
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"RR" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
load
>
>.
>
|||> I just tried it with the same result.
Did you find the actual sqldmo.dll file that corresponds to the SQL Server
2000 install? Or did you run exactly what I posted? Did you get a dialog
that told you the registration was successful?
http://www.aspfaq.com/
(Reverse address to reply.)
|||Yes - the file came from the sql 2000 install and
received a message that is was successful.

>--Original Message--
>Did you find the actual sqldmo.dll file that corresponds
to the SQL Server
>2000 install? Or did you run exactly what I posted?
Did you get a dialog
>that told you the registration was successful?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||You might want to post your issue and any relevant log files from the
install/uninstall to the SQL Server 2005 newsgroups. I'm sure they are
dealing with a lot of similar issues.
For information on access to those groups:
http://communities.microsoft.com/new...elcomePage.htm
http://www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:508f01c489e1$cf7b55b0$a301280a@.phx.gbl...[vbcol=seagreen]
> Yes - the file came from the sql 2000 install and
> received a message that is was successful.
>
> to the SQL Server
> Did you get a dialog
sql

Enterprise Mgr Snap-In Issue

I have been running SQL Server 2000, client tools only.
i installed SQL Server Express (and associated .NET
framework upgrade) to take a look.
I then uninstalled sql server express and went back to
version 1.1 of .NET framework.
My query analyzer works fine, however when i try to load
Enterprise Manager, it says:
Snap-in failed to initialize.
Name: Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I have looked through the knowledge base articles and
have not found one specific to my situation.
I have uninstalled/reinstalled sql server 2000 (and
therefore, MDAC as well) and I am running into the same
issues.
Any help is appreciated.Did you try regsvr32 c:\...\...\sqldmo.dll
http://www.aspfaq.com/
(Reverse address to reply.)
"RR" <anonymous@.discussions.microsoft.com> wrote in message
news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
> I have been running SQL Server 2000, client tools only.
> i installed SQL Server Express (and associated .NET
> framework upgrade) to take a look.
> I then uninstalled sql server express and went back to
> version 1.1 of .NET framework.
> My query analyzer works fine, however when i try to load
> Enterprise Manager, it says:
> Snap-in failed to initialize.
> Name: Microsoft SQL Enterprise Manager
> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
> I have looked through the knowledge base articles and
> have not found one specific to my situation.
> I have uninstalled/reinstalled sql server 2000 (and
> therefore, MDAC as well) and I am running into the same
> issues.
> Any help is appreciated.|||I just tried it with the same result.

>--Original Message--
>Did you try regsvr32 c:\...\...\sqldmo.dll
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"RR" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
load[vbcol=seagreen]
>
>.
>|||> I just tried it with the same result.
Did you find the actual sqldmo.dll file that corresponds to the SQL Server
2000 install? Or did you run exactly what I posted? Did you get a dialog
that told you the registration was successful?
http://www.aspfaq.com/
(Reverse address to reply.)|||Yes - the file came from the sql 2000 install and
received a message that is was successful.

>--Original Message--
>Did you find the actual sqldmo.dll file that corresponds
to the SQL Server
>2000 install? Or did you run exactly what I posted?
Did you get a dialog
>that told you the registration was successful?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||You might want to post your issue and any relevant log files from the
install/uninstall to the SQL Server 2005 newsgroups. I'm sure they are
dealing with a lot of similar issues.
For information on access to those groups:
url]
[url]http://www.aspfaq.com/" target="_blank">http://communities.microsoft.com/ne...www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:508f01c489e1$cf7b55b0$a301280a@.phx.gbl...[vbcol=seagreen]
> Yes - the file came from the sql 2000 install and
> received a message that is was successful.
>
> to the SQL Server
> Did you get a dialog

Enterprise Mgr Snap-In Issue

I have been running SQL Server 2000, client tools only.
i installed SQL Server Express (and associated .NET
framework upgrade) to take a look.
I then uninstalled sql server express and went back to
version 1.1 of .NET framework.
My query analyzer works fine, however when i try to load
Enterprise Manager, it says:
Snap-in failed to initialize.
Name: Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I have looked through the knowledge base articles and
have not found one specific to my situation.
I have uninstalled/reinstalled sql server 2000 (and
therefore, MDAC as well) and I am running into the same
issues.
Any help is appreciated.Did you try regsvr32 c:\...\...\sqldmo.dll
--
http://www.aspfaq.com/
(Reverse address to reply.)
"RR" <anonymous@.discussions.microsoft.com> wrote in message
news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
> I have been running SQL Server 2000, client tools only.
> i installed SQL Server Express (and associated .NET
> framework upgrade) to take a look.
> I then uninstalled sql server express and went back to
> version 1.1 of .NET framework.
> My query analyzer works fine, however when i try to load
> Enterprise Manager, it says:
> Snap-in failed to initialize.
> Name: Microsoft SQL Enterprise Manager
> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
> I have looked through the knowledge base articles and
> have not found one specific to my situation.
> I have uninstalled/reinstalled sql server 2000 (and
> therefore, MDAC as well) and I am running into the same
> issues.
> Any help is appreciated.|||I just tried it with the same result.
>--Original Message--
>Did you try regsvr32 c:\...\...\sqldmo.dll
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"RR" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
>> I have been running SQL Server 2000, client tools only.
>> i installed SQL Server Express (and associated .NET
>> framework upgrade) to take a look.
>> I then uninstalled sql server express and went back to
>> version 1.1 of .NET framework.
>> My query analyzer works fine, however when i try to
load
>> Enterprise Manager, it says:
>> Snap-in failed to initialize.
>> Name: Microsoft SQL Enterprise Manager
>> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
>> I have looked through the knowledge base articles and
>> have not found one specific to my situation.
>> I have uninstalled/reinstalled sql server 2000 (and
>> therefore, MDAC as well) and I am running into the same
>> issues.
>> Any help is appreciated.
>
>.
>|||> I just tried it with the same result.
Did you find the actual sqldmo.dll file that corresponds to the SQL Server
2000 install? Or did you run exactly what I posted? Did you get a dialog
that told you the registration was successful?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Yes - the file came from the sql 2000 install and
received a message that is was successful.
>--Original Message--
>> I just tried it with the same result.
>Did you find the actual sqldmo.dll file that corresponds
to the SQL Server
>2000 install? Or did you run exactly what I posted?
Did you get a dialog
>that told you the registration was successful?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||You might want to post your issue and any relevant log files from the
install/uninstall to the SQL Server 2005 newsgroups. I'm sure they are
dealing with a lot of similar issues.
For information on access to those groups:
http://communities.microsoft.com/newsgroups/ICP/sqlserver2005/us/welcomePage.htm
--
http://www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:508f01c489e1$cf7b55b0$a301280a@.phx.gbl...
> Yes - the file came from the sql 2000 install and
> received a message that is was successful.
>
> >--Original Message--
> >> I just tried it with the same result.
> >
> >Did you find the actual sqldmo.dll file that corresponds
> to the SQL Server
> >2000 install? Or did you run exactly what I posted?
> Did you get a dialog
> >that told you the registration was successful?
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >.
> >

Enterprise Mananger Info not sticking

My PC is running Windows XP.
When I registered SQL Server in the Enterprise Manager,
the information of the registered server is gone (No
items) after I log off.
I have found some registry entries under
HKCU\Software\Microsoft\Microsoft SQL Server\80
\Tools\SQLEW\Registered Servers X\SQL Server Group
that seem to deal with Enterprise Manager.
Any ideas ?
Johnny
Hi,
It seems you do not have previlages in writing into the registry. Try
registering with a Admin OS user. If it is able to do then , ask your
system administrater to give prev (Write) to the below registry key .
HKLM\Software\microsoft\MSSQLSERVER (Root key itself)
Thanks
Hari
MCDBA
"Johnny" <jtao@.ssc.nsw.gov.au> wrote in message
news:f81601c43e31$9ca40110$a101280a@.phx.gbl...
> My PC is running Windows XP.
> When I registered SQL Server in the Enterprise Manager,
> the information of the registered server is gone (No
> items) after I log off.
> I have found some registry entries under
> HKCU\Software\Microsoft\Microsoft SQL Server\80
> \Tools\SQLEW\Registered Servers X\SQL Server Group
> that seem to deal with Enterprise Manager.
> Any ideas ?
> Johnny

Enterprise Mananger Info not sticking

My PC is running Windows XP.
When I registered SQL Server in the Enterprise Manager,
the information of the registered server is gone (No
items) after I log off.
I have found some registry entries under
HKCU\Software\Microsoft\Microsoft SQL Server\80
\Tools\SQLEW\Registered Servers X\SQL Server Group
that seem to deal with Enterprise Manager.
Any ideas ?
JohnnyHi,
It seems you do not have previlages in writing into the registry. Try
registering with a Admin OS user. If it is able to do then , ask your
system administrater to give prev (Write) to the below registry key .
HKLM\Software\microsoft\MSSQLSERVER (Root key itself)
Thanks
Hari
MCDBA
"Johnny" <jtao@.ssc.nsw.gov.au> wrote in message
news:f81601c43e31$9ca40110$a101280a@.phx.gbl...
> My PC is running Windows XP.
> When I registered SQL Server in the Enterprise Manager,
> the information of the registered server is gone (No
> items) after I log off.
> I have found some registry entries under
> HKCU\Software\Microsoft\Microsoft SQL Server\80
> \Tools\SQLEW\Registered Servers X\SQL Server Group
> that seem to deal with Enterprise Manager.
> Any ideas ?
> Johnnysql

Enterprise Mananger Info not sticking

My PC is running Windows XP.
When I registered SQL Server in the Enterprise Manager,
the information of the registered server is gone (No
items) after I log off.
I have found some registry entries under
HKCU\Software\Microsoft\Microsoft SQL Server\80
\Tools\SQLEW\Registered Servers X\SQL Server Group
that seem to deal with Enterprise Manager.
Any ideas ?
JohnnyHi,
It seems you do not have previlages in writing into the registry. Try
registering with a Admin OS user. If it is able to do then , ask your
system administrater to give prev (Write) to the below registry key .
HKLM\Software\microsoft\MSSQLSERVER (Root key itself)
Thanks
Hari
MCDBA
"Johnny" <jtao@.ssc.nsw.gov.au> wrote in message
news:f81601c43e31$9ca40110$a101280a@.phx.gbl...
> My PC is running Windows XP.
> When I registered SQL Server in the Enterprise Manager,
> the information of the registered server is gone (No
> items) after I log off.
> I have found some registry entries under
> HKCU\Software\Microsoft\Microsoft SQL Server\80
> \Tools\SQLEW\Registered Servers X\SQL Server Group
> that seem to deal with Enterprise Manager.
> Any ideas ?
> Johnny

Enterprise Manager: The connection to SQL Server <server> has been broken.

All~
I am currently running the most recent version of MSDE and using EM as
a front end interface. In EM, I go to look at the databases I had
previously created, but receive the message:
The connection to SQL Server <server> has been broken. The connection
to the SQL Server is broken. Do you want to try reconnection...
I am unable to start SQL Agent, but I am not sure whether this is the
cause. I am able to connect via the Query Analyzer facility fine. I
get the following SQLDump [truncated].
What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
...
**
*
* BEGIN STACK DUMP:
* 07/31/04 09:59:24 spid 0
*
* Exception Address = 00000000
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
...
Your help is greatly appreciated.
Richard
Check your SQL Server error logs for more information. Also
check the SQL Agent log and see if you find any errors
related to that issue. You may also want to check the stack
dump and compare it with that mentioned in the following
article:
PRB: Removal of Guest Account May Cause Handled Exception
Access Violation in SQL Server
http://support.microsoft.com/?id=315523
-Sue
On 31 Jul 2004 07:22:35 -0700, rkinnie01@.excite.com (Richard
K) wrote:

>All~
>I am currently running the most recent version of MSDE and using EM as
>a front end interface. In EM, I go to look at the databases I had
>previously created, but receive the message:
>The connection to SQL Server <server> has been broken. The connection
>to the SQL Server is broken. Do you want to try reconnection...
>I am unable to start SQL Agent, but I am not sure whether this is the
>cause. I am able to connect via the Query Analyzer facility fine. I
>get the following SQLDump [truncated].
>What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
>...
>**
>*
>* BEGIN STACK DUMP:
>* 07/31/04 09:59:24 spid 0
>*
>* Exception Address = 00000000
>* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
>* Access Violation occurred reading address 00000000
>...
>Your help is greatly appreciated.
>Richard

Enterprise Manager: The connection to SQL Server <server> has been broken.

All~
I am currently running the most recent version of MSDE and using EM as
a front end interface. In EM, I go to look at the databases I had
previously created, but receive the message:
The connection to SQL Server <server> has been broken. The connection
to the SQL Server is broken. Do you want to try reconnection...
I am unable to start SQL Agent, but I am not sure whether this is the
cause. I am able to connect via the Query Analyzer facility fine. I
get the following SQLDump [truncated].
What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
...
**
*
* BEGIN STACK DUMP:
* 07/31/04 09:59:24 spid 0
*
* Exception Address = 00000000
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
...
Your help is greatly appreciated.
RichardCheck your SQL Server error logs for more information. Also
check the SQL Agent log and see if you find any errors
related to that issue. You may also want to check the stack
dump and compare it with that mentioned in the following
article:
PRB: Removal of Guest Account May Cause Handled Exception
Access Violation in SQL Server
http://support.microsoft.com/?id=315523
-Sue
On 31 Jul 2004 07:22:35 -0700, rkinnie01@.excite.com (Richard
K) wrote:

>All~
>I am currently running the most recent version of MSDE and using EM as
>a front end interface. In EM, I go to look at the databases I had
>previously created, but receive the message:
>The connection to SQL Server <server> has been broken. The connection
>to the SQL Server is broken. Do you want to try reconnection...
>I am unable to start SQL Agent, but I am not sure whether this is the
>cause. I am able to connect via the Query Analyzer facility fine. I
>get the following SQLDump [truncated].
>What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
>...
>**
>*
>* BEGIN STACK DUMP:
>* 07/31/04 09:59:24 spid 0
>*
>* Exception Address = 00000000
>* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
>* Access Violation occurred reading address 00000000
>...
>Your help is greatly appreciated.
>Richard

Enterprise Manager Use of Port 445

SQL Server 2005 Enterprise Manager running on a Windows 2003 member server
is constantly trying to reach the remote SQL Server on port 445. That
implies that File & Printer Sharing would be turned on at the destination
SQL Server. We do turn on File & Printer sharing lightly on servers
because of the security implications, so in this case the Enterprise Manager
cannot connect on port 445. It is still trying to do this persistently,
and even after the admin connects to the database and starts using it, the
Enterprise Manager is persisting repeatedly, forever, to connect on port
445.
What specific functionality is Enterprise Manager attempting to invoke on
the target by use of port 445? Is it something as simple as an
automatic service start request to the SQL Server service on the target
machine?
--
WillHi Will
SQL Server 2005 has Management Studio and not Enterprise Manager.
Port 445 is used in for Named Pipes, if your server is not using this
protocol it should be disabled in the server configuration tool.
John
"Will" wrote:
> SQL Server 2005 Enterprise Manager running on a Windows 2003 member server
> is constantly trying to reach the remote SQL Server on port 445. That
> implies that File & Printer Sharing would be turned on at the destination
> SQL Server. We do turn on File & Printer sharing lightly on servers
> because of the security implications, so in this case the Enterprise Manager
> cannot connect on port 445. It is still trying to do this persistently,
> and even after the admin connects to the database and starts using it, the
> Enterprise Manager is persisting repeatedly, forever, to connect on port
> 445.
> What specific functionality is Enterprise Manager attempting to invoke on
> the target by use of port 445? Is it something as simple as an
> automatic service start request to the SQL Server service on the target
> machine?
> --
> Will
>
>|||My guess is that it is SSMS that periodically check if the instance is running (service is
starting). In 2000's EM, you could configure whether to do this with the registration, but I didn't
find such an option in SSMS...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Will" <westes-usc@.noemail.nospam> wrote in message
news:OoSdnTJTDtYbFpDanZ2dnUVZ_jWdnZ2d@.giganews.com...
> SQL Server 2005 Enterprise Manager running on a Windows 2003 member server is constantly trying to
> reach the remote SQL Server on port 445. That implies that File & Printer Sharing would be
> turned on at the destination SQL Server. We do turn on File & Printer sharing lightly on servers
> because of the security implications, so in this case the Enterprise Manager cannot connect on
> port 445. It is still trying to do this persistently, and even after the admin connects to the
> database and starts using it, the Enterprise Manager is persisting repeatedly, forever, to connect
> on port 445.
> What specific functionality is Enterprise Manager attempting to invoke on the target by use of
> port 445? Is it something as simple as an automatic service start request to the SQL Server
> service on the target machine?
> --
> Will
>|||Tibor Karaszi (tibor_please.no.email_karaszi@.hotmail.nomail.com) writes:
> My guess is that it is SSMS that periodically check if the instance is
> running (service is starting). In 2000's EM, you could configure whether
> to do this with the registration, but I didn't find such an option in
> SSMS...
You can make it happen less often if you set
HKLM\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\PollingInterval
to a suitable value. The unit is apparently centiseconds. See
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247367.
Beware that on a 64-bit machine the location is
HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\Shell
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B1E5FB9-7471-4623-A237-55F873D6B7F4@.microsoft.com...
> SQL Server 2005 has Management Studio and not Enterprise Manager.
> Port 445 is used in for Named Pipes, if your server is not using this
> protocol it should be disabled in the server configuration tool.
Apparently my programmer is using a third party administrator tool. I'm
sure he also uses Enterprise Manager. Are you saying Enterprise Manager
will fail to work on a client when contact SQL Server 2005? He is managing
a production SQL Server 2000 database and just now starting to work with SQL
Server 2005 experimentally.
We already set the client and server protocols at the console of the SQL
Server 2005 computer using the SQL configuration tool, and all protocols
except for TCP and Shared Memory are disabled.
How does the client bootstrap which protocol to use to initiate connection
to the server? There is a catch 22 there where the client does not know
the server configuration regarding client protocols until after client
connects. How does the server communicate its client protocol settings
back to the client? Client is just attempting named pipes no matter what,
then backing off to TCP as a second choice, and once connection is made,
then obeying client protocol rules configured on the server?
--
Will
> "Will" wrote:
>> SQL Server 2005 Enterprise Manager running on a Windows 2003 member
>> server
>> is constantly trying to reach the remote SQL Server on port 445. That
>> implies that File & Printer Sharing would be turned on at the destination
>> SQL Server. We do turn on File & Printer sharing lightly on servers
>> because of the security implications, so in this case the Enterprise
>> Manager
>> cannot connect on port 445. It is still trying to do this persistently,
>> and even after the admin connects to the database and starts using it,
>> the
>> Enterprise Manager is persisting repeatedly, forever, to connect on port
>> 445.
>> What specific functionality is Enterprise Manager attempting to invoke on
>> the target by use of port 445? Is it something as simple as an
>> automatic service start request to the SQL Server service on the target
>> machine?
>> --
>> Will
>>|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99C728CF744BYazorman@.127.0.0.1...
> Tibor Karaszi (tibor_please.no.email_karaszi@.hotmail.nomail.com) writes:
>> My guess is that it is SSMS that periodically check if the instance is
>> running (service is starting). In 2000's EM, you could configure whether
>> to do this with the registration, but I didn't find such an option in
>> SSMS...
> You can make it happen less often if you set
> HKLM\Software\Microsoft\Microsoft SQL
> Server\90\Tools\Shell\PollingInterval
> to a suitable value. The unit is apparently centiseconds. See
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247367.
> Beware that on a 64-bit machine the location is
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\Shell
When I went to the appropriate location on a 32-bit machine, the
PollingInterval Value does not exist. Should I create it and what Value
type should it be?
Since my programmer is using an older management client, my guess is the
port 445 behavior we are seeing is specific to that tool and not
controllable by this registry value, but no harm in trying to change its
value and seeing effect on client behavior.
Is there really nothing that can be set on the client computer itself as a
guideline for behavior of client applications? Are applications like
Enterprise Manager and Management Studio using any specific database API
like OLEDB, or are they using proprietary protocols?
--
Will|||Will (westes-usc@.noemail.nospam) writes:
> When I went to the appropriate location on a 32-bit machine, the
> PollingInterval Value does not exist. Should I create it and what Value
> type should it be?
Yes, you need to create it. I only have it on my machine at home, but I
believe it was a DWORD. The reason I looked into this, is that I had the
same problem as in the bug report.
> Since my programmer is using an older management client, my guess is the
> port 445 behavior we are seeing is specific to that tool and not
> controllable by this registry value, but no harm in trying to change its
> value and seeing effect on client behavior.
Is that some non-MS product? In your original post you said "SQL Server 2005
Enterprise Manager", but there is no such beast. If your programmer simply
running the old Enterprise Manager from SQL 2000, simply have him to
delete that registration, or uncheck the option to display server status.
> Is there really nothing that can be set on the client computer itself as a
> guideline for behavior of client applications? Are applications like
> Enterprise Manager and Management Studio using any specific database API
> like OLEDB, or are they using proprietary protocols?
The client computer is the only place where you can set this. Obviously.
And typically it's per application, since it's the application that polls
the server.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Will (westes-usc@.noemail.nospam) writes:
> We already set the client and server protocols at the console of the SQL
> Server 2005 computer using the SQL configuration tool, and all protocols
> except for TCP and Shared Memory are disabled.
> How does the client bootstrap which protocol to use to initiate
> connection to the server? There is a catch 22 there where the client
> does not know the server configuration regarding client protocols until
> after client connects. How does the server communicate its client
> protocol settings back to the client? Client is just attempting named
> pipes no matter what, then backing off to TCP as a second choice, and
> once connection is made, then obeying client protocol rules configured
> on the server?
You control this with with SQL Configuration Manager or the Client Network
Utility in the SQL 2000 toolset. There you set up in which order the client
is to attempt which protocols.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Will wrote on Thu, 11 Oct 2007 20:03:45 -0700:
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:1B1E5FB9-7471-4623-A237-55F873D6B7F4@.microsoft.com...
>> SQL Server 2005 has Management Studio and not Enterprise Manager.
>> Port 445 is used in for Named Pipes, if your server is not using this
>> protocol it should be disabled in the server configuration tool.
> Apparently my programmer is using a third party administrator tool. I'm
> sure he also uses Enterprise Manager. Are you saying Enterprise
> Manager will fail to work on a client when contact SQL Server 2005? He
> is managing a production SQL Server 2000 database and just now
> starting to work with SQL Server 2005 experimentally.
Enterprise Manager does not work with SQL Server 2005. SMSS will work with
SQL Server 2000 and 2005, but not version 7 or lower. Makes my job here fun,
as I'm having to support 7, 2000, and 2005 and so have to use both EM and
SMSS. It also means that there's no GUI for handling setting up replication
between 2005 and 7 either, it all has to be done using T-SQL - but it does
work :)
Dan

Enterprise Manager Unknown Error

I am running SQL2000 sp3 with 819 hotfix on a 2003
Cluster. When I am on one of the database servers in the
cluster I can select from a table and get data returned.
When I am on the webserver and use EnterPrise I can see
the tables but when I try to select I get 'Unknown Error'.
The same select works from ISQL/W GUI and isql at the
command line while on the webserver.
Any ideas on what to look for would be helpful, nothing is
being logged in the eventlog or the sql log.
Thanks
Check the following;
- The MDAC version on the good and the bad machine. If possible upgrade to
the latest version of MDAC
- Capture the T-SQL command from profiler while you are try to retrieve the
data and see if you can identify the issue.
- Permissions
- The client configuration options by comparing them to the good machine.
HTH
SQL Server Support
Agnes Panosian

Enterprise manager taking up to 10 minutes to save design changes

Hi,
I am running SQL 2000 with an 8 GB database. I have two relatively large
tables (each with about 2 million records in them), and I occasionally need
to make changes to the table design (add a column, increase the size of an
existing field, etc.) on these two tables through the Enterprise Manager.
However, saving these changes can take betwen 5-10 minutes to complete.
If I make changes to any of my other smaller tables, they are saved
instantly. Is it really supposed to take this long for larger tables to be
updated?
Any suggestions would be greatly appreciated.
Never make a change to a production db with EM. Most of the time it will
create a temp table, copy all the data over from the original, drop the
original and then rename the temp table to the original name. Most of the
time a simple ALTER TABLE is all you need to issue. If it is something
simple like increasing a varchar column it might just be a meta data change.
Andrew J. Kelly SQL MVP
"Stu" <Stu@.discussions.microsoft.com> wrote in message
news:BACB0B6C-FDA2-439A-BFA5-A5672AE7AE21@.microsoft.com...
> Hi,
> I am running SQL 2000 with an 8 GB database. I have two relatively large
> tables (each with about 2 million records in them), and I occasionally
> need
> to make changes to the table design (add a column, increase the size of an
> existing field, etc.) on these two tables through the Enterprise Manager.
> However, saving these changes can take betwen 5-10 minutes to complete.
> If I make changes to any of my other smaller tables, they are saved
> instantly. Is it really supposed to take this long for larger tables to
> be
> updated?
> Any suggestions would be greatly appreciated.

Enterprise manager taking up to 10 minutes to save design changes

Hi,
I am running SQL 2000 with an 8 GB database. I have two relatively large
tables (each with about 2 million records in them), and I occasionally need
to make changes to the table design (add a column, increase the size of an
existing field, etc.) on these two tables through the Enterprise Manager.
However, saving these changes can take betwen 5-10 minutes to complete.
If I make changes to any of my other smaller tables, they are saved
instantly. Is it really supposed to take this long for larger tables to be
updated?
Any suggestions would be greatly appreciated.Never make a change to a production db with EM. Most of the time it will
create a temp table, copy all the data over from the original, drop the
original and then rename the temp table to the original name. Most of the
time a simple ALTER TABLE is all you need to issue. If it is something
simple like increasing a varchar column it might just be a meta data change.
--
Andrew J. Kelly SQL MVP
"Stu" <Stu@.discussions.microsoft.com> wrote in message
news:BACB0B6C-FDA2-439A-BFA5-A5672AE7AE21@.microsoft.com...
> Hi,
> I am running SQL 2000 with an 8 GB database. I have two relatively large
> tables (each with about 2 million records in them), and I occasionally
> need
> to make changes to the table design (add a column, increase the size of an
> existing field, etc.) on these two tables through the Enterprise Manager.
> However, saving these changes can take betwen 5-10 minutes to complete.
> If I make changes to any of my other smaller tables, they are saved
> instantly. Is it really supposed to take this long for larger tables to
> be
> updated?
> Any suggestions would be greatly appreciated.

Enterprise manager taking up to 10 minutes to save design changes

Hi,
I am running SQL 2000 with an 8 GB database. I have two relatively large
tables (each with about 2 million records in them), and I occasionally need
to make changes to the table design (add a column, increase the size of an
existing field, etc.) on these two tables through the Enterprise Manager.
However, saving these changes can take betwen 5-10 minutes to complete.
If I make changes to any of my other smaller tables, they are saved
instantly. Is it really supposed to take this long for larger tables to be
updated?
Any suggestions would be greatly appreciated.Never make a change to a production db with EM. Most of the time it will
create a temp table, copy all the data over from the original, drop the
original and then rename the temp table to the original name. Most of the
time a simple ALTER TABLE is all you need to issue. If it is something
simple like increasing a varchar column it might just be a meta data change.
Andrew J. Kelly SQL MVP
"Stu" <Stu@.discussions.microsoft.com> wrote in message
news:BACB0B6C-FDA2-439A-BFA5-A5672AE7AE21@.microsoft.com...
> Hi,
> I am running SQL 2000 with an 8 GB database. I have two relatively large
> tables (each with about 2 million records in them), and I occasionally
> need
> to make changes to the table design (add a column, increase the size of an
> existing field, etc.) on these two tables through the Enterprise Manager.
> However, saving these changes can take betwen 5-10 minutes to complete.
> If I make changes to any of my other smaller tables, they are saved
> instantly. Is it really supposed to take this long for larger tables to
> be
> updated?
> Any suggestions would be greatly appreciated.sql

Enterprise Manager Stops Responding

I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?
"Rajan" wrote:

> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database

Cheers,
harry
|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:

> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>
|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:

Enterprise Manager Stops Responding

I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
:)
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> > Manager
> > on the server via RDP, the server stops responding. At this time, when
> > IRDP
> > another session I dont get the windows login screen...all I get is grey
> > screen and mouse pointer....it is as if the server is hung. Most of the
> > times, I have no other option than hard rebooting the server.
> >
> > What is wrong here?
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> When you reboot the server, do you see anything in the event log or SQL
>> Server error logs?
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
>> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187)
>> > on
>> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
>> > Manager
>> > on the server via RDP, the server stops responding. At this time, when
>> > IRDP
>> > another session I dont get the windows login screen...all I get is grey
>> > screen and mouse pointer....it is as if the server is hung. Most of
>> > the
>> > times, I have no other option than hard rebooting the server.
>> >
>> > What is wrong here?
>>sql

Enterprise Manager Stops Responding

I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:

> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) o
n
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manage
r
> on the server via RDP, the server stops responding. At this time, when IRD
P
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database

Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:

> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>

Enterprise manager running a BAT file

I wish to use Enterprise manager to run a batch file that the program
displays a window, but there is no user input for it. If I run the command
job it runs fine, If I use E.M to run it the job starts and looks like it
hangs and does nothing. Any ideas?
Jay
The GUI that is called runs in the context of a service. It will not be
visible on the screen. Re-write the application so that it is without a GUI
and things should work better.
Keith
"Jay" <Jay@.discussions.microsoft.com> wrote in message
news:47313383-F298-4B62-9597-CADE32CDCBE3@.microsoft.com...
>I wish to use Enterprise manager to run a batch file that the program
> displays a window, but there is no user input for it. If I run the
> command
> job it runs fine, If I use E.M to run it the job starts and looks like it
> hangs and does nothing. Any ideas?
> Jay