Hello,I need some help with SQL Server 2000 SP4. I've been using thedeveloper product for a few years now on my PC with very few problems.Today when I try to start up Enterprise Manager, it crashesimmediately. I get the usual "Please tell Microsoft about this problem"dialog and if I click the 'click here' link, I'm presented with adialog that says:-------------------------------------------------Error signatureAppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exeModVer: 5.1.2600.2180 Offset:0001f07eReporting detailsThis error report includes: blah, blah, blah...-------------------------------------------------I am running Windows XP with SP2. Also installed is Visual Studio 2003,Visual Studio 2005, and SQLServer 2005 (We're in the process ofmigration).All of these products have been running OK together for at least amonth until today. I'm not sure what changed, but obviously somethinghas. I tried uninstalling and reinstalling SQLServer 2000 & it's SP4,but no luck. Enterprise Manager still crashes immediately when I try tolaunch it.Could somebody please help me out?Thanks.
Hi all, I have Sql Server 2000 installed in my home and also i have a website that works with Sql Server2000 and .Net FrameWork v1.1 ,now i want to know is it possible to connect from my home SqlServer to Host SqlServer( where my Website resides ) through Enterprise manager or Query Analizer to do some data-manipulation And how? Thanks in advance.Regards.
Is there anything significantly better in Enterprise Manager 2000 vs. the old EM from SQL Server 7.0?
If so I'd be willing to pay the $50 for the SQL Server 2000 Developer Edition to get it... if not it seems dumb to pay for anything when MSDE 2000 is free and I already have the old EM. (Although I have installed MSDE 2000 as a new instance and can't figure out how to get at it via EM.)
I have just discovered something with EM 2000. In the old days (SQL Server 7), you could right click on a table, choose OPEN TABLE -> SELECT ALL ROWS and get a nice little grid with the select results. The same is true in SQL Server 2000. One thing you cannot do is update a value in that result set, which WAS something you could do in SQL Server 7. If you try it in EM 2000, you get the error message "TRANSACTION CANNOT BE STARTED WHILE IN FIREHOSE MODE". ??????? Am I just missing something, or was Microsoft so worked up about putting XML into their product, they overlooked some of the simple things that were really appreciated (and sorely missed). If anyone can provide some insight, it would be appreciated.
Can the SQL 2000 Enterprise Manager be successfully installed and utilised on a pc that currently has SQL 7 and is used to administer other SQL 7 servers? Can the SQL 2000 Enterprise Manager be used to administer SQL 7?
Is it possible to connect to a SQL Server 7 remotely from a SQL 2000 Enterprise Manager. I have been given the alias config from my web hosting service but no joy on the connection.
I have been using my SQL 2000 Enterprise Manager for many months but it suddenly stopped working. I have uninstalled and reinstalled the software 3 times and it is still not working. When I double click on Enterprise Manager, it doesn't run. Query Analyzer works fine.
I am on Windows XP. No change in system configuration recently or any s/w upgrade, etc.
Hi,I currently (for a hobby project) am unable to use SQL Server 2005, and rather am stuck with 2000. Since the way diagrams are handled changed, the tool for 2005 doesn't allow for the creation of diagrams when using it for 2000 (work sweet for everything else though!).I do not have access to a developer version of SQL Server 2000's tools, and thus no Enterprise Manager, leading me to my question: Are there any free utilities to replace this functionality? I don't have MS Access or Visio or anything like that unfortunately :(
I've installed the client tools on my notebook, and EM normally works properly. However, sometimes Enterprise Manager will crash on me for no obvious reason(it generates errors, but this takes forever, so i kill it). It is not consistent, nor can I reproduce the error, but it happens about once a day, never at the same time. Anyone else see this? My pc has win2K professional on it.
Im having an issue with SQL Server Enterprise manager. I cannot access an MSDE DESKTOP SQL Server 2000 installation that is on the same machine as enterprise manager.
I can access the MSDE Databae from another machine fine, but when I try to register that DB locally in Enterprise manager I get this error.
PC007 - Data source name not found and no default driver specified.
I had to install sqlserver 2000 using k=dbg and skip the MDAC install as it was giving me an install error but this shouldnt have mattered as I am running XP SP2 and it has MDAC 2.8 installed by default.
When Trying to register a SQL Server using Windows Authentication, I get the following error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
When I edit the properties and make it SQL Authentication, it works fine. The SQL Server Service is starting up with a domain user account. If that makes any difference. Funny thing is, that my co-worker, can register the SQL Server in his Enterprise Manager using Windows Authentication. We are both Domain Admins and members of the servers local admin group. So, I'm not sure what to do now.
I checked under Security, Logins...and neither of us are listed under there.
I cant use the DTS editor because shows an error. So, I want to reinstall the enterprise manager without uninstall the sql server 2000, Is that possible? If the answer is yes, How can I do that?
I think that reinstalling only the Enterprise Manager the DTS editor can be fixed.
Sql Version: Sql Server 2000 SO: Windows 2003 Server
Something happened when the server fall down because of no disk space. Now everything is fine but I have a problem in de DTS (from the Enterprise Manager) editor, I cant run, modify and even make a new DTS. What can I do? Is it possible reinstall de DTS components without reinstall sqlserver 2000?
Sql Version: sqlserver2000 Enterprise SO Version: Windows 2003 Server
After running virus cleaning software on my HD, I suddenly find my Enterprise Manager snap-in missing and fail to initialize. Is the MMC erased or damaged? What should I do? Reinstall SQL Server 2000 or repair it? Please advise. Thanks.
Hi, We patched our servers last week and now, when connecting to our server remotely via Enterprise Manager (with DBO permissions), the management folder shows as empty. My guess is its permission related but, I'm not sure where to begin to correct the issue since we arenβt sure how it happened. Any help will be greatly appreciated. ~des
Hello, Yesterday I was in SQL Server 2000 Enterprise Manager and it got hung up. I couldn't get out of it without rebooting my machine. When I tried to enter Enterprise Manager again, I got an error message "MMC Cannot Open The Selected File". So I completly shut down my machine and then started it back up, but still go the same message. I stopped the services and then rebooted again,but no luck either. Today, I still cannot open Enterprise Manager. Has anyone experienced this and worked through it? I am debating as to whether or not I should uninstall SQL Server 2000 and reinstall it? Any advice? Thanks Heather
I have had a problem with Enterprise Manager connecting to SQL Server. At first this problem was experienced with one particular network user... whichever PC he logged onto, Enterprise Manager took ages to connect to SQL Server and every operation was painfully slow. Creating a new Windows NT logon fixed the problem.
I now have this same problem but only on my PC. It doesn't matter which Windows NT logon I use, using Enterprise Manager is painfully slow. I've tried creating a new Windows NT profile, checking the hard drive for errors, defragmenting the disk, reinstalling Enterprise Manager etc but nothing works.
What is strange is that connections from VB applications on my PC are fast. It is only Enterprise Manager that is slow.
I am using the latest service pack for SQL Server.
I thought it could be a problem with the Enterprise Manager registry values but don't want to start messing with them!
Has anyone else experienced this problem? Any advice would be great as I can't find any help from microsoft other than installing the latest service pack for SQL Server.
I am running an SAP installation on clustered DELL poweredge 1850's with a shared scsi disk system. I am running Windows 2000 sp4 with sql 2000 sp4. I am trying to restore a database from a .bak file on a clustered disk. When I attempt to access the disk through enterprise manager it is not there. I only get access to the E: drive (which is clustered as well)
Hi all,I need to gain access to a remote SQL Server 2000 storing my data.The remote SQL machine can only be accessed via an internet connection,that is - it is not part of my network.I know Enterprise Manager can do the job, but EM only comes bundled inMS SQL Server, which is not installed on the client machine.Please let me know which other (preferably free) tools can performsuch remote access.Thanks,Gilad Haimov
Can anyone tell me if there's a way to create new windows from thetables section of a database in Enterprise Manager such that I canlimit the tables included in that window? Ultimately, I'm looking fora solution whereby I can group tables, stored procedures, etc. intological groups that can then be displayed using different MMCconsoles. I'm looking for either a GUI-level or programatic approach.Thank you,Dax Westerman
I am working on a site's SQL Server 2000 database on a W2k3 machine . I went into Enterprise Manager and saw that their database resides on a named instance. I did not see the default instance listed so I registered that using windows authentication. I noticed that the default instance had a user database that had the same name as the user database on the named instance that I was to work on. I looked at the properties of the databases and saw that on both the default and named instances of SQL Server that the Data Files and Log Files for the user database point to the same location.
Is this a problem? Can anyone see any issues with this? Does this mean that someone can simply connect to the named or the default instance of the SQL Server and connect to the same database?
Hi Everyone,Most of our MS SQL Servers are still running on SQL 2000, but being Iwill soon be upgrading my workstation to Vista Business I'd like toinstall MS SQL 2005 Enterprise Manager to manage them all. When Itried to install MS SQL 2000 Enterprise Manager on Vista, it gave me amessage saying it's not compatible, so I'll have to use 2005 I guess.We have LOTS of DTS scripts on our SQL 2000 server, and will 2005 EMwork with these okay? Also I want to make sure SQL 2005 EnterpriseManager won't be adding to, changing, or 'upgrading' the DTS scripts oranything on the SQL 2000 servers as we still have folks using SQL 2000Enterprise Manager.Thanks for any suggestions. I'm always leery when using cross-versionsof Microsoft applications because they are often incompatible or theydo squirly things that often break stuff.Thanks --Alex
There is something very strange going on here. Tested with ADO 2.7 andMSDE/2000. At first, things look quite sensible.You have a simple SQL query, let's sayselect * from mytab where col1 = 1234Now, let's write a simple VB program to do this query back to anMSDE/2000 database on our local machine. Effectively, we'llrs.open sSQLrs.closeand do that 1,000 times. We wont bother fetching the result set, itisn't important in this example.No problem. On my machine this takes around 1.6 seconds and modifyingthe code so that the column value in the where clause changes eachtime (i.e col1 = nnnn), doesn't make a substantial difference to thistime. Well, that all seems reasonable, so moving right along...Now we do it with a stored procedurecreate procedure proctest(@id int)asselect * from mytab where col1 = @idand we now find that executingproctest nnnn1,000 times takes around 1.6 seconds whether or not the argumentchanges. So far so good. No obvious saving, but then we wouldn'texpect any. The query is very simple, after all.Well, get to the point!Now create a table-returning UDFcreate function functest(@id int) returns table asreturn(select * from mytab where col1 = @id)try calling that 1,000 times asselect * from functest(nnnn)and we get around 5.5 seconds on my machine if the argument changes,otherwise 1.6 seconds if it remains the same for each call.Hmm, looks like the query plan is discarded if the argument changes.Well, that's fair enough I guess. UDFs might well be more expensive...gotta be careful about using them. It's odd that discarding the queryplan seems to be SO expensive, but hey, waddya expect?. (perhaps theUDF is completely rebuilt, who knows)last test, then. Create an SP that calls the UDFcreate procedure proctest1(@id int)asselect * from functest(@id)Ok, here's the $64,000 question. How long will this take if @idchanges each time. The raw UDF took 5.5 seconds, remember, so thisshould be slightly slower.But... IT IS NOT.. It takes 1.6 seconds whether or not @id changes.Somehow, the UDF becomes FOUR TIMES more efficient when wrapped in anSP.My theory, which I stress is not entirely scientific, goes somethinglike this:-I deduce that SQL Server decides to reuse the query plan in thiscircumstance but does NOT when the UDF is called directly. This iscounter-intuitive but it may be because SQL Server's query parser istuned for conventional SQL i.e it can saywell, I've gotselect * from mytab WHERE [something or other]and now I've gotselect * from mytab WHERE [something else]so I can probably re-use the query plan from last time. (I don't knowif it is this clever, but it does seem to know when twotextually-different queries have some degree of commonality)Whereas withselect * from UDF(arg1)andselect * from UDF(arg2)it goes... hmm, mebbe not.... I better not risk it.But withsp_something arg1andsp_something arg2it goes... yup, i'll just go call it... and because the SP was alreadycompiled, the internal call to the UDF already has a query plan.Anyway, that's the theory. For more complex UDFs, by the way, theperformance increase can be a lot more substantial. On a big complexUDF with a bunch of joins, I measured a tenfold increase inperformance just by wrapping it in an SP, as above.Obviously, wrapping a UDF in an SP isn't generally a good thing; theidea of UDFs is to allow the column list and where clause to filterthe rowset of the UDF, but if you are repeatedly calling the UDF withthe same where clause and column list, this will make it a *lot*faster.
On one of our machines, all of the SQL Server 2000components except for the main Server component (SQL Servercore) itself were installed (Management tools, etc) a while agoand everything was running fine. Now I go and add/install theServer component and then Service Pack 3a.It seems that Service Manager won't start up (I get an hourglass cursor)and now I find that Enterprise Manager won't run as well. No errormessages appeared and I don't think I saw anything unusual inthe log file.However, I can use Enterprise Manager on a differentmachine and connect to the database (so the databaseitself seems to be running).Any suggestions as to what the problem might be and how tofix it? I like to see if I can repair this without havingto do a reinstall.Thanks.PF
IF someone can assist me. Everytime I load up enterprise manager the service manager turns off. And the enterprise manager can't connect to the local database. But everytime i turn it back on and try to connect again it shuts it off and around and around we go. Help would be appreciated. Thanks.
When I proposed start to use SQL Server 2005 for new VS 2005 web sites, one of my co-workers responded that we will update the old SQL Server 2000 databases to SQL Server 2005 when we are ready to use 2005 SQL Server.
Questions: 1. Any expected problems to upgrade old 2000 databases to new 2005 SQL Server? 2. I have installed both 2005/Management Studio Express and 2000/Enterprise Manager in my PC. Any expected problems when running both 2000 and 2005 SQL Server at the same database server? 3. What is the best configuration for running SQL Server 2005 when we have old 2000 databases? Upgade or not upgrade?
I am trying to 'load' a copy of a SQLServer 2000 database to SQLServer 2005 Express (on another host). The copy was provided by someone else - it came to me as a MDF file only, no LDF file.
I have tried to Attach the database and it fails with a failure to load the LDF. Is there any way to bypass this issue without the LDF or do I have to have that?
The provider of the database says I can create a new database and just point to the MDF as the data source but I can't seem to find a way to do that? I am using SQL Server Management Studio Express.
I have an app that uses a sqlserver 2000 jdbc driver to connect to a sqlserver 2000.
Is it possible to do a direct replacement of sqlserver 2000 with sqlserver 2005 express just by reconfiguring the app to point to the express? The app would still be using the sqlserver 2000 jdbc driver to try and make the connection.
If that is a possibility, what can be some differences in the configuration? Previously with 2000 the config information I entered is:
server name: "machinename"( or ip). I've also tried "machiname/SQLEXPRESS"
DB name: name of db instance
port: 1433(default)
user and pass.
My attempts so far results in
"java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket."
and
"java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL."
