I have just installed SQL 2005 client tools and management studio to register SQL 2000 databases. Although it registers the servers successfully , I can't see any activity monitor on the SQL 2000 registered server . Is it something more that I have to install to see what's happening ?
I have one database at an ISP running on a SQL 2000 server. Under Windows XP Pro, I installed SQL 2000 administrative tools then I could use the database manager as well as the query tool to manage my database.
I have upgraded my machine to Windows Vista Ultimate. SQL 2000 client services won't install under Windows Vista.
Under Windows Vista, I was able to create an ODBC component that connected successfully to the SQL 2000 remote database, but I no longer have a transaction tool or a gui to manage the tables.
My goals are simple: I want to be able to view/add/drop tables and data using some sort of GUI. I would also like to have some sort of SQL transaction client. I don't need to do any high level database management, just view/change/add/delete tables in the one database that I own on that server.
My isp is NOT going to upgrade their SQL. I do not own Microsoft Access or Microsoft Excel. What FREE software options do I have, given my goals?
I currently use Enterprise Manager 8.0 with several SQL 2000 servers. I'm ready to work with my first SQL Server v 2005. Can I use EM 8.0 along side the new Management Console until I'm through the learning curve? I understand you cannot register a 2005 server with EM 8.0, but I assume you can register a 2000 server from the new Management Console without any problem.
Looking for a way to manage reports on both 2000 and 2005. Over the past couple years many reports were created/modified by different people (some no longer available) and we are working on consolidating eveything on a "new improved, bigger, better" 2005 server. I know some reports are duplicated or nearly duplicated on the two systems and are in several different projects/solutions. I want to find a way to collect/consolidate a list of all the projects/solutions, reports, date created/modified, data sources, etc. to help determine how best to procede. I looked through the forum and other documentation but couldn't find a method to do this. Basically I need a report on my reports. Thanks, al.
I have a question about how to efficiently develop on a development version of a database and get those changes over to the production database without loosing live data, etc.?
Here is how we are trying it:
1 Export production database to temp database(exact copy) 2 Delete production database 3 Export development database (definition only, no data) to new database with production database's name 4 Export production (temp) database (data only) over to new production shell
We are having truncate errors due to FK constraints.
Scenario: 1. Access to database objects is based on database roles. 2. Application administrators handle the assignment of users to database roles. Application administrators are first line managers, typically; they are not DBA's and not Help Desk staff.
Question: What products are available to simplify the management of user access to databases in the aforementioned scenario?
I have to manage many SQL Server databases on several servers. How can I manage the jobs, backups and the space on the disc without going to each and every server and database and job? Is there any script to run this? It will be very helpful if you can provide me the sample script or point me to any web site where I can get the info/script for this. Thanks in advance...
Hello, I have SQL Server 2000 and 2005 running on the same server. My current system is in SQL Server 2000 and the new system is in SQL Server 2005. My users will be using SQL Server 2000 for the most part, But for the part the processes that have been migrated to 2005, they will be using SQL Server 2005 as well. The database schema is different on both servers eventhough the data will be similar in most respects. Is there is a way through which any data that is inserted/updated in SQL Server 2000 via content Management System/ manually/ via a batch job, the data is automatically populated in SQL Server 2005 tables or vice versa? Please advice at the earliest. Thanks.
I have a windows 2003 server which has SQL 2005 Express with advanced services installed on it. Then a few weeks back the company purchased SQL server Standard Edition which comes with SQL Server Management Studio (which has more features than SQL Server Management Studio Express currently installed on the server where sql express is running)I have been trying to schedule a maintanance plan on the SQLExpress Instance database from the SQL Server Management Studio that came with the standard version of sql but i have not been able to have all SQL Server Management Studio functionality available when connected to the SQLExpress instance. So is there a way i can connect to the Express Instance from management studio(that comes with the standard edition of sql) and have all its functions available when working with a SQL express database. Or i must upgrade the express database?
I have to merge the data from two databases, one is in SQL Server 2005 format, one is in 2000. The merged data will then reside on a SQL Server 2000 platform. Is there an easy way to do this through Management Studio or Enterprise Manager? Or will we have to export the data from the 2005 database to a flat file and import it into a new 2000 database. And then do the merge?
I just restored my SQL server 2000 database on the SQL server 2005. after this i ran the Service broker sample ("Hello World") on this database by changing the AdventureWorks name to the new database name. The "setup.sql" runs fine. When i run the "SendMessage.sql" i was not getting any rows in the output (The message was not getting inserted into the queue). I checked the Service broker is enabled on this databased using the query "select is_broker_enabled from sys.databases where name = 'newdbname' " It was 1. I even tried the ALTER DATABASE SET ENABLE_BROKER. but it didnt work.
When i tried the sample on a newly created database it worked fine.
Is there any solution to make the restored database to work for service broker.
I've got about 2 months worth of daily databases created in SQL Express 2005 for a pilot project, which the client is converting to a purchase. Unfortunately they're using SQL Server 2000 and I can't figure out how to migrate the databases to the older version. All my searching turns up how to do it in the expected direction.
Any pointers to how or where to search appreciated.
I don't know if this is the right forum to post this question, but here it goes.
We have restored into sql 2005 the database backups made in sql 2000. We connect with trusted connection and application roles, and when trying to execute a transaction to another database (with the guest user), we get a permission error.
Does anyone know if, apart from restoring the databases, we should do something else to get the guest user working the same way as with sql 2000 in the restored databases?
I have moved my databases to 2000 to instance of 2005 on the same server. Now i set databases offline in 2000 as i did upgrade use backup & recovery method.
& my connection string Password=test;Persist Security Info=True;User ID=test;Initial Catalog=databasename;Data Source=ipaddress
i was using above connection string to connect when using 2000 databases form applications in the production machine
I get the following error when i am running my applications now after moving to 2005
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
IS it because i have two server on one server or What do i need to do in order to fix this....tried several thing by searching nothing worked out..
Hi, I just start using MSSQL server 2005, I already install vss studio 2005 so SQL server 2005 is already installed by default (express edition).
But unlike SQL server 2000, I coultn't find any tools similiar to "sql entreprise manager". I was able to create a new database only from server explorer tools in VSS. But pretty strange that this database act like a microsoft access database (creating a database file on my app_data folder). (I am sorry I am new in SQL server 2005 ExpressEdition ).
My question : 1. is that (above) really how mssql server 2005 works? 2. how to create a new user for this database? (example user: sa password: "admin")
I don't have any idea about upgrading databases.I am been given this task. It would be great if you let me know what are all the things to be considered upgrading the sql server 2000 databases to sql server 2005.
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?
Trying to transfer databases from MSDE to SQL. When I use SQLEnterprise Manager - DTS - import or export, it works for the firstdatabase, but then fails for the others. I select the to and fromdatabases using DTS - Import - 'MS OLE DB Provider for SQL Server',then select 'Copy objects and data between SQL Servers'. It failswith the generic error message: 'Copy objects failed', nothingfurther. I tried to just copy data, and it doesn't work totally. Ontwo databases, it said that it copied everything, but when I go inunder Enterprise manager, some of the tables are incomplete, i.e. nodata, table shows up in the list, but if you try to look at it, itsays that it is missing or empty. Also, one table was not evencopied. In the other two cases, I get errors, does not copy alltables. I get errors, like insert fails, but the column it referencesfor the table does not even exist in that table. Any suggestionswould be appreciated.
Does anybody know of a way to rollback SQL Server 2005 databases back to SQL Server 2000? Is there a way of doing it without resorting to Copy Database Wizard? I love to find a way of attaching a SS 2005 database to a SS 2000 instance without any issues.
I recently upgraded to SS 2005 and I am very unhappy with the SS 2005 and I want to rollback to SS 2000, which was a lot more stable. I am having several major issues that are affecting my whole company's day-to-day operations and the managers are not happy. Some of the issues include night time batch running very sluggish for no apparent reason. This is a biggest problem because it only occurs once or so a week and causes a disturbance with the daily activities when the night time processing isn€™t completed on time. The rest of the time, the batch processing runs great, even a little better then on SS 2000. I don't believe it is a matter of my application needing to be retuned because if that was the case, then why isn't it running sluggish every night? Also, it's never the same day that the sluggish behavior occurs. If it was occurring on the same night, then I would have something to investigate within our application, but it doesn't. Another issue that I am having involves a night time job that restores a copy of the production database to the Data Warehouse server to be used for updating the data warehouse. Again, most of the time it runs great (~2 1/2 hours), but once or twice a week, it goes stupid and takes 6 1/2 hours for no apparent reason. Again, it is not happening the same day either, which could give me something to invesigate. On SS 2000, this same job ran flawlessly. Never I did I run into situation that the database restoration took that long to run. Even another issue involves a SQL Server Agent Job that was put into suspended state. What's a suspended state and how can I get it out of suspended state? I can find no information about suspended state in BOL. I did a Google and nothing came up. If this suspended state was put in for security reasons, great, but then tell me how I can remove the suspended state. I am also not happy with the fact that I can't get accurate information about the queries that are actively running at that particular moment. In SS 2000, when I noticed high CPU usage on the server, I would run the sp_who2 active stored proc and it would show me all the active thread and how much CPU it was consuming. I would then find the running threads with the highest CPU numbers and investigate the query and see if we could improve it. Now in SS 2005, I get in the same situation and run the sp_who2 stored proc, and there is no smoking gun. All of the active threads are showing very little CPU usage, which I am very suspect of. What the heck happen to sp_who2? I looked at some of the other ways of looking at running processes (i.e... sys.sysprocesses) and they don't appear to be giving the information that I need.
I am very unhappy and I just want to roll back to SS 2000 and wait a couple of years before I upgrade to SS 2005.
We would like to install Sql 2005 Enterprise Edition (including database engine, reporting service, integration service and analysis service) as a sepearte instance on a server which already has Sql 2000 with reporting services and analysis services. We do not want to disturb the existing sql 2000 setup.
If we do that then what will happen to my earlier sql 2000 reporting service? Will it be upgraded to sql 2005 reporting service? I heard that reporting services are instance unaware application. Where will be the default reporting service database available?
We have a three tier application running on two tiers. 1&2 running onone server and a seperate server for the databases. On the databaseserver we are running Windows 2000 Server with 3Gb of RAM and Dual1.8GHz Xeon Processors and SQL Standard 2000.The memory for the SQL server never seems to go above 1.8Gb. Doesanyone have some suggestions about this or does anyone have someinformation on how many Db's can be run on one server. Most of themare relatively small with low activity.Thanks a lot..
I am preparing to move from sql7 to sql2000 and and considering the copy database wizard to move the databases. The thing that I am concerned with is this passage from BOL
"A database with the identical name on both source and destination servers cannot be moved or copied"
This to me says that the database name cannot be the same on source and destination servers. Yet, you would want the database name to be the same from an application point of view (developers get real nasty when you change database information on them).
Does this mean I cannot use the copy database wizard? Must I use sp_attatch_db?
Hi I need to retrive data from multiple tables which are in two databases. How do i connect to both of them at a time and query the tables with some criteria. Thank you
Microsoft listed 32,767 as the max # of databases for a SQL 2000 instance but I am curious what is the comfortable # of databases we should have before running into issues such as performance degrading etc.
I am planning on upgrading one of my SQL 7 servers to SQL 2000. This server is currently and will continue to replicate with a SQL 7 server.
I want to view our current replication jobs & schedules in plan text so I can check when I recreate the replication that I haven't missed anything. Does anyone know if this is possible?
I need to move our production database to a brand new machine on our LAN.Both machines are running SQL2K. I'd like to place the production databasein a directory on the destination machine with a slightly different pathname than the source SQL server.How can I shrink the transaction log to the minimum size before I try themove? What is the best way to move the database to the new machine? Wehave Veritus Backup Exec.Regards,Charles MacLean
We are moving all databases from a SQL version 7 server to a version 2000server. Which of the following is the preferred method?1) Detach the DB on the version 7 server, move it to the new server viaWindows Explorer and reattach it there.2) Use SQL Enterprise Mananger with the DTS Export Wizard to "copy objects &data between SQL server databases" from the version 7 server to the 2000server.With the changing of the version, I thought maybe option 2 is best. Thoughts?--Mike CzizekIowa Network Services, Inc.Join Bytes!
Just a quick question, does anyone know any major issues with Migrating Sybase Databases to SQL Server? Just wondering if their any oddities I should be aware of? Thanks nixies
I've got a question regarding attaching/restoring of DBs and wonder if anyone could help me out.
Does SQL Server 2000 provide a functionality to attach/restore DB automatically? ie, some kind of polling service to attach/restore DB that were detached previously?