Is there a possibility to enumerate all available sql servers in pure java.
At this time i execute osl -L and interprete the result.
Process p = runTime.exec("osql -L");
Computers without a msde or sql server installed do not have the osql
program. Is there a way to install osql? Or is there an other way to find all
available sql servers?
Thanks in advance Davy
You could simply try to connect to port 1433 of all machines and/or use
a JDBC driver that supports named pipes and try to connect via named
pipe to each machine in the network. This might take quite a while,
though.
Alin.
|||Thanks for the respond.
I already tried to connect to all machines, but i took a while (some minutes
which is too long).
I also tried to open a socket on port 1433, but sql server does not respond.
Is there a possibility to multicast a udp message to all ms-sql-monitors
(port 1434)?
Pipes is maybe an alternitive, but i'm not sure if pipes are enabled.
Davy
|||UDP port 1434 might just work. Give it a try and let me know how it
goes.
Alin.
|||Davy:
Rolling your own sqlbrowse with UDP on port 1434 should work, but if
you're considering going through OSQL then you'd be better off using
ODBC (SQLBrowseConnect) which is on every Windows box.
Be careful that this broadcast method is pretty imprecise -- Windows
machines after XPSP2 (esp. W2K3+) turn off port 1434 by default, and the
SQL Server 2005 will also ship with this port off by default for most
scenarios.
-shelby
Shelby Goerlitz
Microsoft SQL Server
"Davy" <Davy@.discussions.microsoft.com> wrote in message
news:Davy@.discussions.microsoft.com:
> Thanks for the respond.
> I already tried to connect to all machines, but i took a while (some
> minutes
> which is too long).
> I also tried to open a socket on port 1433, but sql server does not
> respond.
> Is there a possibility to multicast a udp message to all ms-sql-monitors
> (port 1434)?
> Pipes is maybe an alternitive, but i'm not sure if pipes are enabled.
> Davy
|||It’s quite difficult to find out the structure of the udp messages send by
the sql monitor. If anyone knows the udp structure all information is
welcome. I can try to write the udp messages with some help.
Davy
"Alin Sinpalean" schreef:
> UDP port 1434 might just work. Give it a try and let me know how it
> goes.
> Alin.
>
|||So it doesn’t seem a good idea?
I'll give it try, if someone has any idea which information to store in the
udp messages.
I tried the SQLBrowseConnect method as well. I couldn't call it directly
from java, but I found a C++ program.
http://www.sqldev.net/misc/ListSQLSvr.htm
It's easy to use from java and it uses the SQLBrowseConnect API, which is
osql independent.
Thank you very much
Davy
|||> I'll give it try, if someone has any idea which information to store
in the
> udp messages.
Just send a single 0x02 byte. You can find more info about the response
here [jTDS source code]:
http://cvs.sourceforge.net/viewcvs.p...=1.7&view=auto
Alin.
|||So, it's not even that difficult. I'm working on it, i hope to finish it
tomorrow. I'll post the result. Maybe one more question: any idea how to find
out the multicast address?
Right now i'm testing with a fixed 10.0.0.255 multicast address. Probably
this address want be te same for every company, but how can i calculate this
address?
Davy
"Alin Sinpalean" schreef:
> in the
> Just send a single 0x02 byte. You can find more info about the response
> here [jTDS source code]:
> http://cvs.sourceforge.net/viewcvs.p...=1.7&view=auto
> Alin.
>
|||Ok, i created some classes to look up all sql servers reachable by a
computer. The program performs a lookup of all subnets of a computer and send
the 02 multicast message on each subnet.
Where should i put the classes? Here as plain text on the forum?
To lookup the subnet of an ip, I use IPCONFIG. Ipconfig is translated, so I
included english, french and dutch. If you need more languages you should add
the texts. I'll add some comment to the source code.
Davy
"Alin Sinpalean" wrote:
> in the
> Just send a single 0x02 byte. You can find more info about the response
> here [jTDS source code]:
> http://cvs.sourceforge.net/viewcvs.p...=1.7&view=auto
> Alin.
>
sql
Showing posts with label time. Show all posts
Showing posts with label time. Show all posts
Tuesday, March 27, 2012
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
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
Thursday, March 22, 2012
Enterprise Mgr Can Not Sort?
Why can I not sort my stored procedure listing by creation date?
I am seeing these dates (omitted the time as not relevant)
2004-03-06
2004-05-14
2004-05-18
2004-03-06
After clicking the 'Create Date' header.
What gives??Brian (bonei@.vafb.com) writes:
> Why can I not sort my stored procedure listing by creation date?
> I am seeing these dates (omitted the time as not relevant)
> 2004-03-06
> 2004-05-14
> 2004-05-18
> 2004-03-06
> After clicking the 'Create Date' header.
> What gives??
I vaguely recall having seen incorrect date formatting in Enterprise
Manager before, although I think that was the Jobs listing. Looking
now, I cannot see anything funny. Maybe there was a bug that was fixed
in a service pack? I'm running SP3, and you? Then again, regional
settings may also matter.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Enterprise Manger Crash Creating user
Please can you help with this?
I created a new users for the first time in SQL Server 2000. While doing
that, Enterprise Manager crashed...and:
1. If I try to add the user again, I get an error because the User already
exists...yet I cannot see it on the console.
2. The user name does not show under Users (or Roles)
Any idea what I need to do to fix it - or what I might be doing wrong?
Is there a problem with Enterprise manager, how can it be fixed? (Looks to
me like it fails while waiting for a response from NT...)Patrik
Open Query Analyzer and use
sp_adduser ,sp_dropuser system stored procedures
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
> Please can you help with this?
> I created a new users for the first time in SQL Server 2000. While
> doing
> that, Enterprise Manager crashed...and:
> 1. If I try to add the user again, I get an error because the User already
> exists...yet I cannot see it on the console.
> 2. The user name does not show under Users (or Roles)
> Any idea what I need to do to fix it - or what I might be doing wrong?
> Is there a problem with Enterprise manager, how can it be fixed? (Looks
> to
> me like it fails while waiting for a response from NT...)
>|||Thx.
Q. Does a SQL Server User Id have be created on the NT Server on which SQL
Server resides? Or can the NT user id be on another server?
"Uri Dimant" wrote:
> Patrik
> Open Query Analyzer and use
> sp_adduser ,sp_dropuser system stored procedures
>
>
>
> "Patrick" <Patrick@.discussions.microsoft.com> wrote in message
> news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
>
>|||Patrick
Users and Logins are two different things
1)Logins are created to allow the person access to SQL Server .
2) Users are created to grant/allow access to the database/s located on the
server
http://vyaskn.tripod.com/sql_server...t_practices.htm --sec
urity
best practices
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:21715426-1674-48EE-A782-0709C183E456@.microsoft.com...[vbcol=seagreen]
> Thx.
> Q. Does a SQL Server User Id have be created on the NT Server on which
> SQL
> Server resides? Or can the NT user id be on another server?
> "Uri Dimant" wrote:
>
I created a new users for the first time in SQL Server 2000. While doing
that, Enterprise Manager crashed...and:
1. If I try to add the user again, I get an error because the User already
exists...yet I cannot see it on the console.
2. The user name does not show under Users (or Roles)
Any idea what I need to do to fix it - or what I might be doing wrong?
Is there a problem with Enterprise manager, how can it be fixed? (Looks to
me like it fails while waiting for a response from NT...)Patrik
Open Query Analyzer and use
sp_adduser ,sp_dropuser system stored procedures
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
> Please can you help with this?
> I created a new users for the first time in SQL Server 2000. While
> doing
> that, Enterprise Manager crashed...and:
> 1. If I try to add the user again, I get an error because the User already
> exists...yet I cannot see it on the console.
> 2. The user name does not show under Users (or Roles)
> Any idea what I need to do to fix it - or what I might be doing wrong?
> Is there a problem with Enterprise manager, how can it be fixed? (Looks
> to
> me like it fails while waiting for a response from NT...)
>|||Thx.
Q. Does a SQL Server User Id have be created on the NT Server on which SQL
Server resides? Or can the NT user id be on another server?
"Uri Dimant" wrote:
> Patrik
> Open Query Analyzer and use
> sp_adduser ,sp_dropuser system stored procedures
>
>
>
> "Patrick" <Patrick@.discussions.microsoft.com> wrote in message
> news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
>
>|||Patrick
Users and Logins are two different things
1)Logins are created to allow the person access to SQL Server .
2) Users are created to grant/allow access to the database/s located on the
server
http://vyaskn.tripod.com/sql_server...t_practices.htm --sec
urity
best practices
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:21715426-1674-48EE-A782-0709C183E456@.microsoft.com...[vbcol=seagreen]
> Thx.
> Q. Does a SQL Server User Id have be created on the NT Server on which
> SQL
> Server resides? Or can the NT user id be on another server?
> "Uri Dimant" wrote:
>
Enterprise Manger CLOSES!
Hello everyone,
I have SQL server 2000 installed on Windows 2003 std
edition. The first time I opened E manager I was able to
right click on any database and go to properties to set
the location of transaction logs and so forth! The second
time I went into it I tried the same thing and now E
manager shuts down. It does the same thing to all the
databases. Does anyone know why this is happening. I have
sp3 installed...
GiacomoI don't know what happening but my be able to supply
information for you to find out.
The 2003 should contain logs of programs / services that
have started an stopped including SQL Server, so have a
chat to your 2003 Administrator to see if you can have a
look at them.
SQL Server also keeps a log, under the server - Managment -
SQL Server Logs have a look at that and see if it helps.
Run a trace and see what the server was doing before the
shut down.
J
>--Original Message--
>Hello everyone,
>I have SQL server 2000 installed on Windows 2003 std
>edition. The first time I opened E manager I was able to
>right click on any database and go to properties to set
>the location of transaction logs and so forth! The second
>time I went into it I tried the same thing and now E
>manager shuts down. It does the same thing to all the
>databases. Does anyone know why this is happening. I have
>sp3 installed...
>Giacomo
>.
>
I have SQL server 2000 installed on Windows 2003 std
edition. The first time I opened E manager I was able to
right click on any database and go to properties to set
the location of transaction logs and so forth! The second
time I went into it I tried the same thing and now E
manager shuts down. It does the same thing to all the
databases. Does anyone know why this is happening. I have
sp3 installed...
GiacomoI don't know what happening but my be able to supply
information for you to find out.
The 2003 should contain logs of programs / services that
have started an stopped including SQL Server, so have a
chat to your 2003 Administrator to see if you can have a
look at them.
SQL Server also keeps a log, under the server - Managment -
SQL Server Logs have a look at that and see if it helps.
Run a trace and see what the server was doing before the
shut down.
J
>--Original Message--
>Hello everyone,
>I have SQL server 2000 installed on Windows 2003 std
>edition. The first time I opened E manager I was able to
>right click on any database and go to properties to set
>the location of transaction logs and so forth! The second
>time I went into it I tried the same thing and now E
>manager shuts down. It does the same thing to all the
>databases. Does anyone know why this is happening. I have
>sp3 installed...
>Giacomo
>.
>
Wednesday, March 21, 2012
Enterprise Manager Very Slow on one PC
I have had a problem with EM being extremely slow. The first time this
ocurred it was related to one users Windows Logon Profile... i.e. whichever
PC he logged onto, EM was very slow to connect and run. It turned out his
Windows Network roaming profile was corrupt and fixing this solved the
problem.
I now have the same problem on my PC but it is PC dependant... i.e. it
doesn't matter who logs onto this PC, EM is always slow. If I log onto
another PC EM runs fine.
Any ideas what may have gone wrong on my PC?
Could it be Windows registry values that are incorrect? If so is there a way
of checking these registry values?
I have tried creating a new Windows logon profile and uninstalling and
reinstalling EM. I do not want to have to resort to rebuilding the PC.
Any ideas would be great
Thanks
Martyn
Did you check to see if ODBC tracing is turned on? You can
check from the ODBC data source administrator, go to the
tracing tab. If the button on the left has the caption Stop
Tracing Now, the tracing is turned on. Click on the button
and the caption will change to start tracing now - meaning
that tracing is turned off.
-Sue
On Thu, 23 Sep 2004 01:35:03 -0700, "martynhogg"
<martynhogg@.discussions.microsoft.com> wrote:
>I have had a problem with EM being extremely slow. The first time this
>ocurred it was related to one users Windows Logon Profile... i.e. whichever
>PC he logged onto, EM was very slow to connect and run. It turned out his
>Windows Network roaming profile was corrupt and fixing this solved the
>problem.
>I now have the same problem on my PC but it is PC dependant... i.e. it
>doesn't matter who logs onto this PC, EM is always slow. If I log onto
>another PC EM runs fine.
>Any ideas what may have gone wrong on my PC?
>Could it be Windows registry values that are incorrect? If so is there a way
>of checking these registry values?
>I have tried creating a new Windows logon profile and uninstalling and
>reinstalling EM. I do not want to have to resort to rebuilding the PC.
>Any ideas would be great
>Thanks
>Martyn
|||Sue, you are a genius!!! I've posted on several sites and no-one could answer
this one. It worked! Thankyou so much!
Martyn
"Sue Hoegemeier" wrote:
> Did you check to see if ODBC tracing is turned on? You can
> check from the ODBC data source administrator, go to the
> tracing tab. If the button on the left has the caption Stop
> Tracing Now, the tracing is turned on. Click on the button
> and the caption will change to start tracing now - meaning
> that tracing is turned off.
> -Sue
> On Thu, 23 Sep 2004 01:35:03 -0700, "martynhogg"
> <martynhogg@.discussions.microsoft.com> wrote:
>
>
sql
ocurred it was related to one users Windows Logon Profile... i.e. whichever
PC he logged onto, EM was very slow to connect and run. It turned out his
Windows Network roaming profile was corrupt and fixing this solved the
problem.
I now have the same problem on my PC but it is PC dependant... i.e. it
doesn't matter who logs onto this PC, EM is always slow. If I log onto
another PC EM runs fine.
Any ideas what may have gone wrong on my PC?
Could it be Windows registry values that are incorrect? If so is there a way
of checking these registry values?
I have tried creating a new Windows logon profile and uninstalling and
reinstalling EM. I do not want to have to resort to rebuilding the PC.
Any ideas would be great
Thanks
Martyn
Did you check to see if ODBC tracing is turned on? You can
check from the ODBC data source administrator, go to the
tracing tab. If the button on the left has the caption Stop
Tracing Now, the tracing is turned on. Click on the button
and the caption will change to start tracing now - meaning
that tracing is turned off.
-Sue
On Thu, 23 Sep 2004 01:35:03 -0700, "martynhogg"
<martynhogg@.discussions.microsoft.com> wrote:
>I have had a problem with EM being extremely slow. The first time this
>ocurred it was related to one users Windows Logon Profile... i.e. whichever
>PC he logged onto, EM was very slow to connect and run. It turned out his
>Windows Network roaming profile was corrupt and fixing this solved the
>problem.
>I now have the same problem on my PC but it is PC dependant... i.e. it
>doesn't matter who logs onto this PC, EM is always slow. If I log onto
>another PC EM runs fine.
>Any ideas what may have gone wrong on my PC?
>Could it be Windows registry values that are incorrect? If so is there a way
>of checking these registry values?
>I have tried creating a new Windows logon profile and uninstalling and
>reinstalling EM. I do not want to have to resort to rebuilding the PC.
>Any ideas would be great
>Thanks
>Martyn
|||Sue, you are a genius!!! I've posted on several sites and no-one could answer
this one. It worked! Thankyou so much!
Martyn
"Sue Hoegemeier" wrote:
> Did you check to see if ODBC tracing is turned on? You can
> check from the ODBC data source administrator, go to the
> tracing tab. If the button on the left has the caption Stop
> Tracing Now, the tracing is turned on. Click on the button
> and the caption will change to start tracing now - meaning
> that tracing is turned off.
> -Sue
> On Thu, 23 Sep 2004 01:35:03 -0700, "martynhogg"
> <martynhogg@.discussions.microsoft.com> wrote:
>
>
sql
Sunday, March 11, 2012
enterprise manager on Windows XP x64
I have just installed Windows XP Pro x64 on new computer and having hard
time installing enterprise manager (SQL Server 2000) to connect to my SQL
2000 Server running on remote machine.
Is there any version of SQL Client Tools for x64 or I have to purchase SQL
Server 2005.
Thanks,
Vlado"Vlado Jasovic \(www.excelleinc.com\)" <vjasovicATexcelleincDOTcom>
wrote in news:LIydnU5LKY-WLuLenZ2dnUVZ_tidnZ2d@.giganews.com:
> I have just installed Windows XP Pro x64 on new computer and having
> hard time installing enterprise manager (SQL Server 2000) to connect
> to my SQL 2000 Server running on remote machine.
You can install and run the 32-bit version of Enterprise Manager. As far as
I know there is no 64-bit version of it.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging
time installing enterprise manager (SQL Server 2000) to connect to my SQL
2000 Server running on remote machine.
Is there any version of SQL Client Tools for x64 or I have to purchase SQL
Server 2005.
Thanks,
Vlado"Vlado Jasovic \(www.excelleinc.com\)" <vjasovicATexcelleincDOTcom>
wrote in news:LIydnU5LKY-WLuLenZ2dnUVZ_tidnZ2d@.giganews.com:
> I have just installed Windows XP Pro x64 on new computer and having
> hard time installing enterprise manager (SQL Server 2000) to connect
> to my SQL 2000 Server running on remote machine.
You can install and run the 32-bit version of Enterprise Manager. As far as
I know there is no 64-bit version of it.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging
Friday, March 9, 2012
Enterprise Manager launch error
Not sure what has caused this to suddenly happen, but each time I attempt to launch Enterprise Manager I get the error:
"MMC cannot open the file C:\MSSQL\BINN\SQL Server Enterprises Manager.MSC
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file."
Now, I've already attempted to reinstall the client tools with no luck. The file does exist, and I have not changed my security settings -- at least that I'm aware of.
I use EM daily, so I'm perplexed as to why over night it stopped working. Is it possible a Windows Update could have caused this?
If you have any insight I'd appreciate it. Thanks.
PS. I'm using SQL 7.0 on a WinXP Pro laptop.
DavidI feel there could be some issue with h/w on the box and may refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;315341 to fix it.
Ensure to obtain latest service pack for XP also, if nothing works reinstall from scratch.
"MMC cannot open the file C:\MSSQL\BINN\SQL Server Enterprises Manager.MSC
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file."
Now, I've already attempted to reinstall the client tools with no luck. The file does exist, and I have not changed my security settings -- at least that I'm aware of.
I use EM daily, so I'm perplexed as to why over night it stopped working. Is it possible a Windows Update could have caused this?
If you have any insight I'd appreciate it. Thanks.
PS. I'm using SQL 7.0 on a WinXP Pro laptop.
DavidI feel there could be some issue with h/w on the box and may refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;315341 to fix it.
Ensure to obtain latest service pack for XP also, if nothing works reinstall from scratch.
Enterprise Manager Job Scheduler and the Time change problem
We just noticed a problem with the SQL Server Agent's Job Scheduler. During
the time change the other week, the system clock would reset itself every
day. I've seen it go an hour ahead and an hour behind. During this time,
some of the jobs got out of synch.
Let's say we have a few jobs that run every 4 hours. one of the clock
changes happened in the hour before it was to run, so afterward, the current
time is now passed when the job was scheduled to run. Since the time for
it's next scheduled run has already passed, the job just sits there and never
runs again.
Why does SQL Server not see that a jobs scheduled time has passed, and just
continue with the next run in the schedule?
Hi
"Granola Pete" wrote:
> We just noticed a problem with the SQL Server Agent's Job Scheduler. During
> the time change the other week, the system clock would reset itself every
> day. I've seen it go an hour ahead and an hour behind. During this time,
> some of the jobs got out of synch.
> Let's say we have a few jobs that run every 4 hours. one of the clock
> changes happened in the hour before it was to run, so afterward, the current
> time is now passed when the job was scheduled to run. Since the time for
> it's next scheduled run has already passed, the job just sits there and never
> runs again.
> Why does SQL Server not see that a jobs scheduled time has passed, and just
> continue with the next run in the schedule?
Is the system time being effected and where/how is the time being
synchronised to?
John
|||Yes the system clock is what was being affected. From about Monday the 12th
until about Wed 14th or Thurs 15th, the clock would reset itself each morning
to a different time. It is synching itself to "time.windows.com". It has
stabilized itself now.
Having the time switch near the time when a scheduled job is supposed to run
doesn't seem much of a problem.
It is more troubling that the Agent Job Scheduler couldn't recover the
schedule after "missing" a run at a certain time. Granted, I should have
been checking the jobs, but there is usually no need unless I get
notification that an error has occured.
"John Bell" wrote:
> Hi
> "Granola Pete" wrote:
>
> Is the system time being effected and where/how is the time being
> synchronised to?
> John
|||Hi
"Granola Pete" wrote:
> Yes the system clock is what was being affected. From about Monday the 12th
> until about Wed 14th or Thurs 15th, the clock would reset itself each morning
> to a different time. It is synching itself to "time.windows.com". It has
> stabilized itself now.
> Having the time switch near the time when a scheduled job is supposed to run
> doesn't seem much of a problem.
> It is more troubling that the Agent Job Scheduler couldn't recover the
> schedule after "missing" a run at a certain time. Granted, I should have
> been checking the jobs, but there is usually no need unless I get
> notification that an error has occured.
>
I am not sure how you are will reliably know that there has been a run
missed because of a time change! There could be numerous scenarios of time
changes that you would have to provide decissions on whether or not the job
should run.
John
|||Well, I know that a run has been missed and that it hasn't run again simply
by the fact that the scheduler shows the "Last Run Status(Start Date)" field
shows the 11th and the "Next Run Date" shows the 12th and it is already the
20th, no history of the run since 11th.
the problem isn't so much that it missed it, but that it didn't hit the next
scheduled time to run.
The system doesn't necessarily have to be smart enough to look back and see
when the last time it ran. If it is on a recurring schedule, say every 4
hours, it doesn't need to know that it didn't run at noon, only that it needs
to run at 4 and then 8, etc. but I would hope it is smart enough to know
that if it's "Next Run Date" is somehow an earlier date than the current
time, that it recovers or at least throws an error.
The thing is, if a job fails once, it still runs the next time it is
scheduled to run. How is that any different from missing a run time? It is
just odd to me that it would work in one instance, but not the other.
"John Bell" wrote:
> I am not sure how you are will reliably know that there has been a run
> missed because of a time change! There could be numerous scenarios of time
> changes that you would have to provide decissions on whether or not the job
> should run.
> John
the time change the other week, the system clock would reset itself every
day. I've seen it go an hour ahead and an hour behind. During this time,
some of the jobs got out of synch.
Let's say we have a few jobs that run every 4 hours. one of the clock
changes happened in the hour before it was to run, so afterward, the current
time is now passed when the job was scheduled to run. Since the time for
it's next scheduled run has already passed, the job just sits there and never
runs again.
Why does SQL Server not see that a jobs scheduled time has passed, and just
continue with the next run in the schedule?
Hi
"Granola Pete" wrote:
> We just noticed a problem with the SQL Server Agent's Job Scheduler. During
> the time change the other week, the system clock would reset itself every
> day. I've seen it go an hour ahead and an hour behind. During this time,
> some of the jobs got out of synch.
> Let's say we have a few jobs that run every 4 hours. one of the clock
> changes happened in the hour before it was to run, so afterward, the current
> time is now passed when the job was scheduled to run. Since the time for
> it's next scheduled run has already passed, the job just sits there and never
> runs again.
> Why does SQL Server not see that a jobs scheduled time has passed, and just
> continue with the next run in the schedule?
Is the system time being effected and where/how is the time being
synchronised to?
John
|||Yes the system clock is what was being affected. From about Monday the 12th
until about Wed 14th or Thurs 15th, the clock would reset itself each morning
to a different time. It is synching itself to "time.windows.com". It has
stabilized itself now.
Having the time switch near the time when a scheduled job is supposed to run
doesn't seem much of a problem.
It is more troubling that the Agent Job Scheduler couldn't recover the
schedule after "missing" a run at a certain time. Granted, I should have
been checking the jobs, but there is usually no need unless I get
notification that an error has occured.
"John Bell" wrote:
> Hi
> "Granola Pete" wrote:
>
> Is the system time being effected and where/how is the time being
> synchronised to?
> John
|||Hi
"Granola Pete" wrote:
> Yes the system clock is what was being affected. From about Monday the 12th
> until about Wed 14th or Thurs 15th, the clock would reset itself each morning
> to a different time. It is synching itself to "time.windows.com". It has
> stabilized itself now.
> Having the time switch near the time when a scheduled job is supposed to run
> doesn't seem much of a problem.
> It is more troubling that the Agent Job Scheduler couldn't recover the
> schedule after "missing" a run at a certain time. Granted, I should have
> been checking the jobs, but there is usually no need unless I get
> notification that an error has occured.
>
I am not sure how you are will reliably know that there has been a run
missed because of a time change! There could be numerous scenarios of time
changes that you would have to provide decissions on whether or not the job
should run.
John
|||Well, I know that a run has been missed and that it hasn't run again simply
by the fact that the scheduler shows the "Last Run Status(Start Date)" field
shows the 11th and the "Next Run Date" shows the 12th and it is already the
20th, no history of the run since 11th.
the problem isn't so much that it missed it, but that it didn't hit the next
scheduled time to run.
The system doesn't necessarily have to be smart enough to look back and see
when the last time it ran. If it is on a recurring schedule, say every 4
hours, it doesn't need to know that it didn't run at noon, only that it needs
to run at 4 and then 8, etc. but I would hope it is smart enough to know
that if it's "Next Run Date" is somehow an earlier date than the current
time, that it recovers or at least throws an error.
The thing is, if a job fails once, it still runs the next time it is
scheduled to run. How is that any different from missing a run time? It is
just odd to me that it would work in one instance, but not the other.
"John Bell" wrote:
> I am not sure how you are will reliably know that there has been a run
> missed because of a time change! There could be numerous scenarios of time
> changes that you would have to provide decissions on whether or not the job
> should run.
> John
Enterprise Manager Job Scheduler and the Time change problem
We just noticed a problem with the SQL Server Agent's Job Scheduler. During
the time change the other week, the system clock would reset itself every
day. I've seen it go an hour ahead and an hour behind. During this time,
some of the jobs got out of synch.
Let's say we have a few jobs that run every 4 hours. one of the clock
changes happened in the hour before it was to run, so afterward, the current
time is now passed when the job was scheduled to run. Since the time for
it's next scheduled run has already passed, the job just sits there and neve
r
runs again.
Why does SQL Server not see that a jobs scheduled time has passed, and just
continue with the next run in the schedule?Hi
"Granola Pete" wrote:
> We just noticed a problem with the SQL Server Agent's Job Scheduler. Duri
ng
> the time change the other week, the system clock would reset itself every
> day. I've seen it go an hour ahead and an hour behind. During this time,
> some of the jobs got out of synch.
> Let's say we have a few jobs that run every 4 hours. one of the clock
> changes happened in the hour before it was to run, so afterward, the curre
nt
> time is now passed when the job was scheduled to run. Since the time for
> it's next scheduled run has already passed, the job just sits there and ne
ver
> runs again.
> Why does SQL Server not see that a jobs scheduled time has passed, and jus
t
> continue with the next run in the schedule?
Is the system time being effected and where/how is the time being
synchronised to?
John|||Yes the system clock is what was being affected. From about Monday the 12th
until about Wed 14th or Thurs 15th, the clock would reset itself each mornin
g
to a different time. It is synching itself to "time.windows.com". It has
stabilized itself now.
Having the time switch near the time when a scheduled job is supposed to run
doesn't seem much of a problem.
It is more troubling that the Agent Job Scheduler couldn't recover the
schedule after "missing" a run at a certain time. Granted, I should have
been checking the jobs, but there is usually no need unless I get
notification that an error has occured.
"John Bell" wrote:
> Hi
> "Granola Pete" wrote:
>
> Is the system time being effected and where/how is the time being
> synchronised to?
> John|||Hi
"Granola Pete" wrote:
> Yes the system clock is what was being affected. From about Monday the 12
th
> until about Wed 14th or Thurs 15th, the clock would reset itself each morn
ing
> to a different time. It is synching itself to "time.windows.com". It has
> stabilized itself now.
> Having the time switch near the time when a scheduled job is supposed to r
un
> doesn't seem much of a problem.
> It is more troubling that the Agent Job Scheduler couldn't recover the
> schedule after "missing" a run at a certain time. Granted, I should have
> been checking the jobs, but there is usually no need unless I get
> notification that an error has occured.
>
I am not sure how you are will reliably know that there has been a run
missed because of a time change! There could be numerous scenarios of time
changes that you would have to provide decissions on whether or not the job
should run.
John|||Well, I know that a run has been missed and that it hasn't run again simply
by the fact that the scheduler shows the "Last Run Status(Start Date)" field
shows the 11th and the "Next Run Date" shows the 12th and it is already the
20th, no history of the run since 11th.
the problem isn't so much that it missed it, but that it didn't hit the next
scheduled time to run.
The system doesn't necessarily have to be smart enough to look back and see
when the last time it ran. If it is on a recurring schedule, say every 4
hours, it doesn't need to know that it didn't run at noon, only that it need
s
to run at 4 and then 8, etc. but I would hope it is smart enough to know
that if it's "Next Run Date" is somehow an earlier date than the current
time, that it recovers or at least throws an error.
The thing is, if a job fails once, it still runs the next time it is
scheduled to run. How is that any different from missing a run time? It i
s
just odd to me that it would work in one instance, but not the other.
"John Bell" wrote:
> I am not sure how you are will reliably know that there has been a run
> missed because of a time change! There could be numerous scenarios of time
> changes that you would have to provide decissions on whether or not the jo
b
> should run.
> John
the time change the other week, the system clock would reset itself every
day. I've seen it go an hour ahead and an hour behind. During this time,
some of the jobs got out of synch.
Let's say we have a few jobs that run every 4 hours. one of the clock
changes happened in the hour before it was to run, so afterward, the current
time is now passed when the job was scheduled to run. Since the time for
it's next scheduled run has already passed, the job just sits there and neve
r
runs again.
Why does SQL Server not see that a jobs scheduled time has passed, and just
continue with the next run in the schedule?Hi
"Granola Pete" wrote:
> We just noticed a problem with the SQL Server Agent's Job Scheduler. Duri
ng
> the time change the other week, the system clock would reset itself every
> day. I've seen it go an hour ahead and an hour behind. During this time,
> some of the jobs got out of synch.
> Let's say we have a few jobs that run every 4 hours. one of the clock
> changes happened in the hour before it was to run, so afterward, the curre
nt
> time is now passed when the job was scheduled to run. Since the time for
> it's next scheduled run has already passed, the job just sits there and ne
ver
> runs again.
> Why does SQL Server not see that a jobs scheduled time has passed, and jus
t
> continue with the next run in the schedule?
Is the system time being effected and where/how is the time being
synchronised to?
John|||Yes the system clock is what was being affected. From about Monday the 12th
until about Wed 14th or Thurs 15th, the clock would reset itself each mornin
g
to a different time. It is synching itself to "time.windows.com". It has
stabilized itself now.
Having the time switch near the time when a scheduled job is supposed to run
doesn't seem much of a problem.
It is more troubling that the Agent Job Scheduler couldn't recover the
schedule after "missing" a run at a certain time. Granted, I should have
been checking the jobs, but there is usually no need unless I get
notification that an error has occured.
"John Bell" wrote:
> Hi
> "Granola Pete" wrote:
>
> Is the system time being effected and where/how is the time being
> synchronised to?
> John|||Hi
"Granola Pete" wrote:
> Yes the system clock is what was being affected. From about Monday the 12
th
> until about Wed 14th or Thurs 15th, the clock would reset itself each morn
ing
> to a different time. It is synching itself to "time.windows.com". It has
> stabilized itself now.
> Having the time switch near the time when a scheduled job is supposed to r
un
> doesn't seem much of a problem.
> It is more troubling that the Agent Job Scheduler couldn't recover the
> schedule after "missing" a run at a certain time. Granted, I should have
> been checking the jobs, but there is usually no need unless I get
> notification that an error has occured.
>
I am not sure how you are will reliably know that there has been a run
missed because of a time change! There could be numerous scenarios of time
changes that you would have to provide decissions on whether or not the job
should run.
John|||Well, I know that a run has been missed and that it hasn't run again simply
by the fact that the scheduler shows the "Last Run Status(Start Date)" field
shows the 11th and the "Next Run Date" shows the 12th and it is already the
20th, no history of the run since 11th.
the problem isn't so much that it missed it, but that it didn't hit the next
scheduled time to run.
The system doesn't necessarily have to be smart enough to look back and see
when the last time it ran. If it is on a recurring schedule, say every 4
hours, it doesn't need to know that it didn't run at noon, only that it need
s
to run at 4 and then 8, etc. but I would hope it is smart enough to know
that if it's "Next Run Date" is somehow an earlier date than the current
time, that it recovers or at least throws an error.
The thing is, if a job fails once, it still runs the next time it is
scheduled to run. How is that any different from missing a run time? It i
s
just odd to me that it would work in one instance, but not the other.
"John Bell" wrote:
> I am not sure how you are will reliably know that there has been a run
> missed because of a time change! There could be numerous scenarios of time
> changes that you would have to provide decissions on whether or not the jo
b
> should run.
> John
Enterprise Manager Job Scheduler and the Time change problem
We just noticed a problem with the SQL Server Agent's Job Scheduler. During
the time change the other week, the system clock would reset itself every
day. I've seen it go an hour ahead and an hour behind. During this time,
some of the jobs got out of synch.
Let's say we have a few jobs that run every 4 hours. one of the clock
changes happened in the hour before it was to run, so afterward, the current
time is now passed when the job was scheduled to run. Since the time for
it's next scheduled run has already passed, the job just sits there and never
runs again.
Why does SQL Server not see that a jobs scheduled time has passed, and just
continue with the next run in the schedule?Hi
"Granola Pete" wrote:
> We just noticed a problem with the SQL Server Agent's Job Scheduler. During
> the time change the other week, the system clock would reset itself every
> day. I've seen it go an hour ahead and an hour behind. During this time,
> some of the jobs got out of synch.
> Let's say we have a few jobs that run every 4 hours. one of the clock
> changes happened in the hour before it was to run, so afterward, the current
> time is now passed when the job was scheduled to run. Since the time for
> it's next scheduled run has already passed, the job just sits there and never
> runs again.
> Why does SQL Server not see that a jobs scheduled time has passed, and just
> continue with the next run in the schedule?
Is the system time being effected and where/how is the time being
synchronised to?
John|||Yes the system clock is what was being affected. From about Monday the 12th
until about Wed 14th or Thurs 15th, the clock would reset itself each morning
to a different time. It is synching itself to "time.windows.com". It has
stabilized itself now.
Having the time switch near the time when a scheduled job is supposed to run
doesn't seem much of a problem.
It is more troubling that the Agent Job Scheduler couldn't recover the
schedule after "missing" a run at a certain time. Granted, I should have
been checking the jobs, but there is usually no need unless I get
notification that an error has occured.
"John Bell" wrote:
> Hi
> "Granola Pete" wrote:
> > We just noticed a problem with the SQL Server Agent's Job Scheduler. During
> > the time change the other week, the system clock would reset itself every
> > day. I've seen it go an hour ahead and an hour behind. During this time,
> > some of the jobs got out of synch.
> >
> > Let's say we have a few jobs that run every 4 hours. one of the clock
> > changes happened in the hour before it was to run, so afterward, the current
> > time is now passed when the job was scheduled to run. Since the time for
> > it's next scheduled run has already passed, the job just sits there and never
> > runs again.
> >
> > Why does SQL Server not see that a jobs scheduled time has passed, and just
> > continue with the next run in the schedule?
> Is the system time being effected and where/how is the time being
> synchronised to?
> John|||Hi
"Granola Pete" wrote:
> Yes the system clock is what was being affected. From about Monday the 12th
> until about Wed 14th or Thurs 15th, the clock would reset itself each morning
> to a different time. It is synching itself to "time.windows.com". It has
> stabilized itself now.
> Having the time switch near the time when a scheduled job is supposed to run
> doesn't seem much of a problem.
> It is more troubling that the Agent Job Scheduler couldn't recover the
> schedule after "missing" a run at a certain time. Granted, I should have
> been checking the jobs, but there is usually no need unless I get
> notification that an error has occured.
>
I am not sure how you are will reliably know that there has been a run
missed because of a time change! There could be numerous scenarios of time
changes that you would have to provide decissions on whether or not the job
should run.
John|||Well, I know that a run has been missed and that it hasn't run again simply
by the fact that the scheduler shows the "Last Run Status(Start Date)" field
shows the 11th and the "Next Run Date" shows the 12th and it is already the
20th, no history of the run since 11th.
the problem isn't so much that it missed it, but that it didn't hit the next
scheduled time to run.
The system doesn't necessarily have to be smart enough to look back and see
when the last time it ran. If it is on a recurring schedule, say every 4
hours, it doesn't need to know that it didn't run at noon, only that it needs
to run at 4 and then 8, etc. but I would hope it is smart enough to know
that if it's "Next Run Date" is somehow an earlier date than the current
time, that it recovers or at least throws an error.
The thing is, if a job fails once, it still runs the next time it is
scheduled to run. How is that any different from missing a run time? It is
just odd to me that it would work in one instance, but not the other.
"John Bell" wrote:
> I am not sure how you are will reliably know that there has been a run
> missed because of a time change! There could be numerous scenarios of time
> changes that you would have to provide decissions on whether or not the job
> should run.
> John
the time change the other week, the system clock would reset itself every
day. I've seen it go an hour ahead and an hour behind. During this time,
some of the jobs got out of synch.
Let's say we have a few jobs that run every 4 hours. one of the clock
changes happened in the hour before it was to run, so afterward, the current
time is now passed when the job was scheduled to run. Since the time for
it's next scheduled run has already passed, the job just sits there and never
runs again.
Why does SQL Server not see that a jobs scheduled time has passed, and just
continue with the next run in the schedule?Hi
"Granola Pete" wrote:
> We just noticed a problem with the SQL Server Agent's Job Scheduler. During
> the time change the other week, the system clock would reset itself every
> day. I've seen it go an hour ahead and an hour behind. During this time,
> some of the jobs got out of synch.
> Let's say we have a few jobs that run every 4 hours. one of the clock
> changes happened in the hour before it was to run, so afterward, the current
> time is now passed when the job was scheduled to run. Since the time for
> it's next scheduled run has already passed, the job just sits there and never
> runs again.
> Why does SQL Server not see that a jobs scheduled time has passed, and just
> continue with the next run in the schedule?
Is the system time being effected and where/how is the time being
synchronised to?
John|||Yes the system clock is what was being affected. From about Monday the 12th
until about Wed 14th or Thurs 15th, the clock would reset itself each morning
to a different time. It is synching itself to "time.windows.com". It has
stabilized itself now.
Having the time switch near the time when a scheduled job is supposed to run
doesn't seem much of a problem.
It is more troubling that the Agent Job Scheduler couldn't recover the
schedule after "missing" a run at a certain time. Granted, I should have
been checking the jobs, but there is usually no need unless I get
notification that an error has occured.
"John Bell" wrote:
> Hi
> "Granola Pete" wrote:
> > We just noticed a problem with the SQL Server Agent's Job Scheduler. During
> > the time change the other week, the system clock would reset itself every
> > day. I've seen it go an hour ahead and an hour behind. During this time,
> > some of the jobs got out of synch.
> >
> > Let's say we have a few jobs that run every 4 hours. one of the clock
> > changes happened in the hour before it was to run, so afterward, the current
> > time is now passed when the job was scheduled to run. Since the time for
> > it's next scheduled run has already passed, the job just sits there and never
> > runs again.
> >
> > Why does SQL Server not see that a jobs scheduled time has passed, and just
> > continue with the next run in the schedule?
> Is the system time being effected and where/how is the time being
> synchronised to?
> John|||Hi
"Granola Pete" wrote:
> Yes the system clock is what was being affected. From about Monday the 12th
> until about Wed 14th or Thurs 15th, the clock would reset itself each morning
> to a different time. It is synching itself to "time.windows.com". It has
> stabilized itself now.
> Having the time switch near the time when a scheduled job is supposed to run
> doesn't seem much of a problem.
> It is more troubling that the Agent Job Scheduler couldn't recover the
> schedule after "missing" a run at a certain time. Granted, I should have
> been checking the jobs, but there is usually no need unless I get
> notification that an error has occured.
>
I am not sure how you are will reliably know that there has been a run
missed because of a time change! There could be numerous scenarios of time
changes that you would have to provide decissions on whether or not the job
should run.
John|||Well, I know that a run has been missed and that it hasn't run again simply
by the fact that the scheduler shows the "Last Run Status(Start Date)" field
shows the 11th and the "Next Run Date" shows the 12th and it is already the
20th, no history of the run since 11th.
the problem isn't so much that it missed it, but that it didn't hit the next
scheduled time to run.
The system doesn't necessarily have to be smart enough to look back and see
when the last time it ran. If it is on a recurring schedule, say every 4
hours, it doesn't need to know that it didn't run at noon, only that it needs
to run at 4 and then 8, etc. but I would hope it is smart enough to know
that if it's "Next Run Date" is somehow an earlier date than the current
time, that it recovers or at least throws an error.
The thing is, if a job fails once, it still runs the next time it is
scheduled to run. How is that any different from missing a run time? It is
just odd to me that it would work in one instance, but not the other.
"John Bell" wrote:
> I am not sure how you are will reliably know that there has been a run
> missed because of a time change! There could be numerous scenarios of time
> changes that you would have to provide decissions on whether or not the job
> should run.
> John
Wednesday, March 7, 2012
enterprise manager for SQL 2000
Hello,
I have been using SQL 7 for some time and so have the
Enterprise manager to match. I have just started work on a
remote SQL server, which runs SQL 2000 - and so my
Enterprise manager can't communicate with it.
I have looked everywhere, but can't see a way of
controlling the remote server without upgrading my SQL
server to version 2000. This seems a bit of an overkill
when all I want to do is create and import a few tables on
the remote server.
Do I really have to pay for a whole system upgrade, even
though I don't want to use SQL 2000 here, just so I can
import some tables? I can't seem to locate an alternative
Microsoft solution.
Thanks.
DCIf you upgrade your CLient Utilites to SQL2k you will be able to communicate
with the SQL7 and SQL2K boxes. It's backward compatible.
--
HTH
Ryan Waight, MCDBA, MCSE
"david cox" <davidcox@.mail.com> wrote in message
news:044401c37d08$f422d640$a001280a@.phx.gbl...
> Hello,
> I have been using SQL 7 for some time and so have the
> Enterprise manager to match. I have just started work on a
> remote SQL server, which runs SQL 2000 - and so my
> Enterprise manager can't communicate with it.
> I have looked everywhere, but can't see a way of
> controlling the remote server without upgrading my SQL
> server to version 2000. This seems a bit of an overkill
> when all I want to do is create and import a few tables on
> the remote server.
> Do I really have to pay for a whole system upgrade, even
> though I don't want to use SQL 2000 here, just so I can
> import some tables? I can't seem to locate an alternative
> Microsoft solution.
> Thanks.
> DC
I have been using SQL 7 for some time and so have the
Enterprise manager to match. I have just started work on a
remote SQL server, which runs SQL 2000 - and so my
Enterprise manager can't communicate with it.
I have looked everywhere, but can't see a way of
controlling the remote server without upgrading my SQL
server to version 2000. This seems a bit of an overkill
when all I want to do is create and import a few tables on
the remote server.
Do I really have to pay for a whole system upgrade, even
though I don't want to use SQL 2000 here, just so I can
import some tables? I can't seem to locate an alternative
Microsoft solution.
Thanks.
DCIf you upgrade your CLient Utilites to SQL2k you will be able to communicate
with the SQL7 and SQL2K boxes. It's backward compatible.
--
HTH
Ryan Waight, MCDBA, MCSE
"david cox" <davidcox@.mail.com> wrote in message
news:044401c37d08$f422d640$a001280a@.phx.gbl...
> Hello,
> I have been using SQL 7 for some time and so have the
> Enterprise manager to match. I have just started work on a
> remote SQL server, which runs SQL 2000 - and so my
> Enterprise manager can't communicate with it.
> I have looked everywhere, but can't see a way of
> controlling the remote server without upgrading my SQL
> server to version 2000. This seems a bit of an overkill
> when all I want to do is create and import a few tables on
> the remote server.
> Do I really have to pay for a whole system upgrade, even
> though I don't want to use SQL 2000 here, just so I can
> import some tables? I can't seem to locate an alternative
> Microsoft solution.
> Thanks.
> DC
Enterprise manager fails to start
When I try to run SQL Server Enterprise Mgr, but each time, it just fails to start and I get the error box:
Microsoft Management Console has encountered a problem and needs to close. We are sorry for the inconvenience.
You can look at the data before it sends it to MS, but it really doesn't help much. Some of the info is:
AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
ModVer: 5.1.2600.2180 Offset: 0001f07e
I have uninstalled and reinstalled, but nothing helps. The MMC runs on several other snap ins, including Computer Mgmt and then looking at SQL Server, but the problem is that I need to view some remote SQL Servers.
--
Joel Z
Maybe the snap-in has become corrupt or damaged.
Try renaming the existing SQL Server Enterprise Manager.MSC
file.
Then copy the SQL Server Enterprise Manager.MSC file from
the your SQL Server CD to the same location.
-Sue
On Wed, 2 Mar 2005 19:24:52 -0600, "Joel Zinn"
<Joelz@.zinn-4.com> wrote:
>When I try to run SQL Server Enterprise Mgr, but each time, it just fails to start and I get the error box:
>Microsoft Management Console has encountered a problem and needs to close. We are sorry for the inconvenience.
>You can look at the data before it sends it to MS, but it really doesn't help much. Some of the info is:
>AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
>ModVer: 5.1.2600.2180 Offset: 0001f07e
>
>I have uninstalled and reinstalled, but nothing helps. The MMC runs on several other snap ins, including Computer Mgmt and then looking at SQL Server, but the problem is that I need to view some remote SQL Servers.
|||In addition to Sue's advice, you could try reinstalling the MMC, scroll down this page for the MMC 1.2 download. http://www.microsoft.com/windows2000...anagement/mmc/
Steve
"Joel Zinn" <Joelz@.zinn-4.com> wrote in message news:uqiWO$4HFHA.3844@.TK2MSFTNGP14.phx.gbl...
When I try to run SQL Server Enterprise Mgr, but each time, it just fails to start and I get the error box:
Microsoft Management Console has encountered a problem and needs to close. We are sorry for the inconvenience.
You can look at the data before it sends it to MS, but it really doesn't help much. Some of the info is:
AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
ModVer: 5.1.2600.2180 Offset: 0001f07e
I have uninstalled and reinstalled, but nothing helps. The MMC runs on several other snap ins, including Computer Mgmt and then looking at SQL Server, but the problem is that I need to view some remote SQL Servers.
--
Joel Z
|||I have recently encountered this same error and I was able to fix it. It happens to be an error with the MMC application data file for enterprise manager in your user profile.
From windows explorer, browse to the "MMC" folder under C:\Documents and Settings\[user_profile]\Applicaiton Data\Microsoft\ (This is a hidden folder and to be able to view it you must show hidden files and folders in the "Tools" --> "Folder Options" --> "View" settings). There should be a file named "SQL Server Enterprise Manager". You can either delete or rename this file (I prefer the latter). MMC will re-create this file the next time you access Enterprise Manager and should then be working properly.
j.
Microsoft Management Console has encountered a problem and needs to close. We are sorry for the inconvenience.
You can look at the data before it sends it to MS, but it really doesn't help much. Some of the info is:
AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
ModVer: 5.1.2600.2180 Offset: 0001f07e
I have uninstalled and reinstalled, but nothing helps. The MMC runs on several other snap ins, including Computer Mgmt and then looking at SQL Server, but the problem is that I need to view some remote SQL Servers.
--
Joel Z
Maybe the snap-in has become corrupt or damaged.
Try renaming the existing SQL Server Enterprise Manager.MSC
file.
Then copy the SQL Server Enterprise Manager.MSC file from
the your SQL Server CD to the same location.
-Sue
On Wed, 2 Mar 2005 19:24:52 -0600, "Joel Zinn"
<Joelz@.zinn-4.com> wrote:
>When I try to run SQL Server Enterprise Mgr, but each time, it just fails to start and I get the error box:
>Microsoft Management Console has encountered a problem and needs to close. We are sorry for the inconvenience.
>You can look at the data before it sends it to MS, but it really doesn't help much. Some of the info is:
>AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
>ModVer: 5.1.2600.2180 Offset: 0001f07e
>
>I have uninstalled and reinstalled, but nothing helps. The MMC runs on several other snap ins, including Computer Mgmt and then looking at SQL Server, but the problem is that I need to view some remote SQL Servers.
|||In addition to Sue's advice, you could try reinstalling the MMC, scroll down this page for the MMC 1.2 download. http://www.microsoft.com/windows2000...anagement/mmc/
Steve
"Joel Zinn" <Joelz@.zinn-4.com> wrote in message news:uqiWO$4HFHA.3844@.TK2MSFTNGP14.phx.gbl...
When I try to run SQL Server Enterprise Mgr, but each time, it just fails to start and I get the error box:
Microsoft Management Console has encountered a problem and needs to close. We are sorry for the inconvenience.
You can look at the data before it sends it to MS, but it really doesn't help much. Some of the info is:
AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
ModVer: 5.1.2600.2180 Offset: 0001f07e
I have uninstalled and reinstalled, but nothing helps. The MMC runs on several other snap ins, including Computer Mgmt and then looking at SQL Server, but the problem is that I need to view some remote SQL Servers.
--
Joel Z
|||I have recently encountered this same error and I was able to fix it. It happens to be an error with the MMC application data file for enterprise manager in your user profile.
From windows explorer, browse to the "MMC" folder under C:\Documents and Settings\[user_profile]\Applicaiton Data\Microsoft\ (This is a hidden folder and to be able to view it you must show hidden files and folders in the "Tools" --> "Folder Options" --> "View" settings). There should be a file named "SQL Server Enterprise Manager". You can either delete or rename this file (I prefer the latter). MMC will re-create this file the next time you access Enterprise Manager and should then be working properly.
j.
Friday, February 24, 2012
Enterprise manager catastrophic failure
I am using Enterprise Manager 2K on 2k professional; some time ago I ran into the problem of enterprise manager returning "Catastropic Failure" when trying to open a table in EM. I couldn't find any help on the problem and reinstalling SQL did not seem to fix the problem, so I rebuilt my system. I have since run into the same problem 2 more times, and it seems to occur after I install quicktime, which then requires me to rebuild my system again in order to get the open table feature of EM to work.
Has anyone else encountered this?Originally posted by matt_ward61
I am using Enterprise Manager 2K on 2k professional; some time ago I ran into the problem of enterprise manager returning "Catastropic Failure" when trying to open a table in EM. I couldn't find any help on the problem and reinstalling SQL did not seem to fix the problem, so I rebuilt my system. I have since run into the same problem 2 more times, and it seems to occur after I install quicktime, which then requires me to rebuild my system again in order to get the open table feature of EM to work.
Has anyone else encountered this?|||Hmm.. never had this error before. Probably you can try patching it with the latest service pack.|||Originally posted by tswern
Hi,
I also faced the same problem with windows 2000 advanced server/windows 95 and sql2000 personal edition.
managed to get over it after installing latest MDAC from microsoft site..
try it out.
Has anyone else encountered this?Originally posted by matt_ward61
I am using Enterprise Manager 2K on 2k professional; some time ago I ran into the problem of enterprise manager returning "Catastropic Failure" when trying to open a table in EM. I couldn't find any help on the problem and reinstalling SQL did not seem to fix the problem, so I rebuilt my system. I have since run into the same problem 2 more times, and it seems to occur after I install quicktime, which then requires me to rebuild my system again in order to get the open table feature of EM to work.
Has anyone else encountered this?|||Hmm.. never had this error before. Probably you can try patching it with the latest service pack.|||Originally posted by tswern
Hi,
I also faced the same problem with windows 2000 advanced server/windows 95 and sql2000 personal edition.
managed to get over it after installing latest MDAC from microsoft site..
try it out.
Friday, February 17, 2012
Enterprise Manager - problem
I have a problem with Enterprise Manager - when I refresh list of tables or
databases it hangs (is not responding) for long time - about 10-30 minutes.
What is more important during my refreshement users are unable to work
normally - it hangs entire server.
Some other details:
1. I am only dbo of one database with no administrative privilges.
2. There are no problems with Query Analyzer
3. Problem is related to one particular server - I don't have these
difficulties with my local instance of SQL Server.
Is there any solution of this problem?
Cheers.Hi,
EM is a flaky toool it does so many things behind scens more recemended
method is to use QA instead of EM , you have to ensure latest service pack
and mdac version . and please refer article :
http://vyaskn.tripod.com/sql_enterp...er_or_t-sql.htm
HTH
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Mr Curious" wrote:
> I have a problem with Enterprise Manager - when I refresh list of tables o
r
> databases it hangs (is not responding) for long time - about 10-30 minutes
.
> What is more important during my refreshement users are unable to work
> normally - it hangs entire server.
> Some other details:
> 1. I am only dbo of one database with no administrative privilges.
> 2. There are no problems with Query Analyzer
> 3. Problem is related to one particular server - I don't have these
> difficulties with my local instance of SQL Server.
>
> Is there any solution of this problem?
> Cheers.
>
>
databases it hangs (is not responding) for long time - about 10-30 minutes.
What is more important during my refreshement users are unable to work
normally - it hangs entire server.
Some other details:
1. I am only dbo of one database with no administrative privilges.
2. There are no problems with Query Analyzer
3. Problem is related to one particular server - I don't have these
difficulties with my local instance of SQL Server.
Is there any solution of this problem?
Cheers.Hi,
EM is a flaky toool it does so many things behind scens more recemended
method is to use QA instead of EM , you have to ensure latest service pack
and mdac version . and please refer article :
http://vyaskn.tripod.com/sql_enterp...er_or_t-sql.htm
HTH
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Mr Curious" wrote:
> I have a problem with Enterprise Manager - when I refresh list of tables o
r
> databases it hangs (is not responding) for long time - about 10-30 minutes
.
> What is more important during my refreshement users are unable to work
> normally - it hangs entire server.
> Some other details:
> 1. I am only dbo of one database with no administrative privilges.
> 2. There are no problems with Query Analyzer
> 3. Problem is related to one particular server - I don't have these
> difficulties with my local instance of SQL Server.
>
> Is there any solution of this problem?
> Cheers.
>
>
Enterprise Manager - How secure is it?
I connect to my clients SQL databases via Enterprise Manager. Most of the time the SQL server resides at a web host. A colleague recently told me that this is a huge security hole and I should be using Remote Desktop instead.
I would appreciate other input, opinions, and guidance on this issue.Actually both have problems ... they should both have a secure layer, but none has it ...
You can secure your remote SQL server more by putting a firewall before it that will only allow connections on port 1433 (SQL Server port) coming from certain IP addresses|||Another way to make it more secure is to configure the DB as a named instance, and change the network port to the DB.. This can be done through Enterprise manager.
Enterprise Manager
I've got SQL Server 2000 tools-only installed on my desktop and have a
bunch of servers registered within Enterprise Manager. Every time I
connect to one of my registered servers then right-click and select
Properties, Enterprise Manager closes on me. I never receive an error,
it just closes. As far as I know, I've applied all the same service
packs and hotfixes to my tools-only install as we have on each of the
servers so versions should be the same.
What can I do to resolve this?
Toni
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I have not experienced this error. Are the servers SQL7 (not that this
should matter)? If you have not applied SQL Server 2000 SP3 on your client
system you might want to do that. It will update a few binaries. Perhaps
this will help solve your problem.
Keith
"Toni" <teibner@.nospam.allina.com> wrote in message
news:%239749jDuEHA.2596@.TK2MSFTNGP15.phx.gbl...
> I've got SQL Server 2000 tools-only installed on my desktop and have a
> bunch of servers registered within Enterprise Manager. Every time I
> connect to one of my registered servers then right-click and select
> Properties, Enterprise Manager closes on me. I never receive an error,
> it just closes. As far as I know, I've applied all the same service
> packs and hotfixes to my tools-only install as we have on each of the
> servers so versions should be the same.
> What can I do to resolve this?
> Toni
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||The registered servers are both SQL 7 and SQL 2000. I've already
applied the latest patches (sp3a + ms03-031 and KB826161). Any other
ideas (other than just deal with it or call Microsoft)?
Thanks.
Toni
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
bunch of servers registered within Enterprise Manager. Every time I
connect to one of my registered servers then right-click and select
Properties, Enterprise Manager closes on me. I never receive an error,
it just closes. As far as I know, I've applied all the same service
packs and hotfixes to my tools-only install as we have on each of the
servers so versions should be the same.
What can I do to resolve this?
Toni
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I have not experienced this error. Are the servers SQL7 (not that this
should matter)? If you have not applied SQL Server 2000 SP3 on your client
system you might want to do that. It will update a few binaries. Perhaps
this will help solve your problem.
Keith
"Toni" <teibner@.nospam.allina.com> wrote in message
news:%239749jDuEHA.2596@.TK2MSFTNGP15.phx.gbl...
> I've got SQL Server 2000 tools-only installed on my desktop and have a
> bunch of servers registered within Enterprise Manager. Every time I
> connect to one of my registered servers then right-click and select
> Properties, Enterprise Manager closes on me. I never receive an error,
> it just closes. As far as I know, I've applied all the same service
> packs and hotfixes to my tools-only install as we have on each of the
> servers so versions should be the same.
> What can I do to resolve this?
> Toni
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||The registered servers are both SQL 7 and SQL 2000. I've already
applied the latest patches (sp3a + ms03-031 and KB826161). Any other
ideas (other than just deal with it or call Microsoft)?
Thanks.
Toni
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)