We're finally making the move. We have a 120GB SQL7 DB. We have purchased a new server, and running Windows Advanced Server in 64bit mode, and our Network/DB support Company has installed SQL2005 on the new server.
The existing SQL7 instance is running on an older server.
My question is, because of the size of the SQL7 DB, can I simply detach the DB from SQL7, copy it across to the new server that SQL2005 is installed on, and attach the SQL7 DB into the SQL2005 environment?
I'm not worried about transaction files moving across, as we run a real time db environment, and any back up copy is useless.
I have a SQL Server 2000 box running two databases which was upgraded in error from SQL7.0 Basically we are no longer being given support as SQL2000 is not supported by the suppliers.
I therefore need to downgrade the box to SQL7.0 and was wondering if anyone had any opinions on the best method for doing this. Note that I do have a spare server to host the databases while I rebuild this server ( I am having to do a complete rebuild from scratch for other reasons ).
My thought is to transfer the databases to the spare server, rebuild the first box to SQL 7.0 and then perform a snapshot replication to transfer the data back.
Any thoughts on this would be gratefully received.
I am stepping in as our SQL 7 DBA for a platform were 7 was installed prior to my arrival. As a company, we have all versions of 7 licensed - how do I know if Standard or Enterprise version was installed on this server?
If Standard was installed - how nasty is it going to be to upgrade to Enterprise?
I'm importing floor machine data from SQL7 into SQL2005 using SSIS. I import the SQL7 data into a SQL2005 master table and then attempt to match the import data with the data in a current table for either update or insert of new machines. The SQL2005 master table was imported from a SQL2000 database. When I run the first Lookup import, it does not recognize the PK matches between the SQL7 import and SQL2005 master and imports all the SQL7 as new machines. The first Lookup branches to a second lookup that checks for changes in the SQL2005 master. When I run the package a second time, the second Lookup treats all the records as updates when it gets to the second Lookup, but should treat these as found. Any suggestions as to why this process is not working properly would be appreciated. Is there a way I can embed a picture of the process from SSIS in this post? Thanks
Hello everyone, My company is thinking of migrating from SQL Standard to Enterprise Edition. I am the dba--but not much experience in SQL. Not sure what I need to do if this projec falls onto my shoulder. Any advise will be very much appreciated. Thanks!!!
Hi All, I have just installed EM for SQL Server 2000 and so have no registered servers in the console list. We have about 50 servers which we support and so I would rather import my colleagues list rather than registering them all manually. Is there ay way to do this ? Many thanks Andy
Hi,Can someone tell me what the best way is to migrate from a SQL Server 2000Standard Edition to a SQL Server 2000 Enterprise Edition?Is this a migration possible from the setup program of the EnterpriseEdition?What are the pitfalls?Thanks in advanceTheo Linnenbank
Hi , We are using the a 4 CPU SQL Server 2000 Enterprise edition for our application , We want to migrate to SQL2005 with the compatibility level downgraded to SQL2000. If we go for the SQL2005 Standard edition is there any problem? We are not using the Failover clustering in our server.
I have a medical records system, SoapWare v4.90, that uses MSDE (SQL2000) databases. Due to the 2gb limitation, I am trying to migrate over to SQL 2005 (Standard or Express) which I have heard works fine. The SoapWare has a datamanager that allows me to log in to the MSDE instance, detach the SoapWare databases from msde (as well as do backups, etc) which I can confirm are detached.
Then I log back into a SQL2005 database instance using the datamanager and try to attach the database. This is what their pictured instructions demonstrate. However, I get the following error:
Database 'sw_charts' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.
Of course, some of the entries will be read only, since doctors have to sign off the charts and are not allowed to subsequently change them. But I should still be able to switch over to sql 2005?!?!?!?
Or... is there a way to attach the databases to SQLExpress manually?
Hi I have new bought the SQL server 2005 enterprise, but it have 2 CDs, so what are the differences between CD1 and CD2? and so which one should i install first? or is it necessary to install both two or just need to install one of them? And about my original sql 2000 database, can i just attach it's MDF file into the sql 2005 engine, or which import wizard can load the sql 2000 MDF into sql 2005? or do i need to keep the sql 2000 engine before do this? thx
Will it be possible to do an in-place upgrade from SQL 2000 Server Enterprise SP4 32 bit running on top of 64 bit Windows 2003 Enterprise , clustered, to SQL 2005 Enterprise 64 bit? The 32 bit SQL 2000 to 64 bit SQL 2005 in place upgrade seems questionable to me... Anybody tried anything like this?
Can anyone comment on the engine performance difference between SQL2005 Enterprise Edition versus Standard? I'm talking generalized performance of the engine and not admin features (parallel index operations) or scaled-storage (partitioning)
The marketing literature makes note of two things:
Enterprise can use more then 4 processors
Enhanced read-ahead and scan (super scan) (note: I cannot find anything about this 'feature') One un-noted Feature:
only Enterprise supports 'lock pages in memory'
We are in the process of migrating from SQL2000 to SQL2005 in an OLTP environment. Based on the marketing literature; I would have chosen SQL2005-standard. But based on our limited testing, we are seeing some strange differences.
Query Performance
With MaxDOP=1 and using a large batch query (select top 1500000); SQL2005-Enterprise is twice as fast as SQL2005-Standard.
(Note: this difference persists regardless of lock-pages-in-memory setting)
CPU Utilization
In addition, taskmgr shows that SQL2005-Enterprise uses a single processor at ~90%. While SQL2005-Standard shows a single processor at ~20%.
Lock Behavior
We are also seeing lock-behavior differences. A single DML statement that attempts to modify ~5000 rows will cause Table-locks on SQL2005-Standard but obtain normal row-locks on SQL2005-Enterprise.
These empirical differences make me wonder if the engine codebase is fundamentally different between the two?
I found sql2005 Enterprise cannot be installed under Simplied Chinese win 2003, the only thing i suspect is that win2003 is an envaluation copy with netframework 2.0 be installed.
How can I copy a SQL 7 database from one server to another? Please tell me all the ways because I've tried the obvious and it doesn't work. (backup and restore - won't go from one server to another, DTS transfer object Wizard - does a whole pile of errors and doesn't do stored proceedures and trigures). Thanks for help in advance. Also, what is the email address to post to the listserv and where is the FAQ for SQL7? Most of my listserv's tell you where to post right at the bottom of the digest I get - any chance you guys would do that with this list? Thanks again.
I just upgraded my SQL 2000 server to SQL2005. I forked out all that money, and now it takes 4~5 seconds for a webpage to load. You can see for yourself. It's pathetic. When I ran SQL2000, i was getting instant results on any webpage. I can't find any tool to optimize the tables or databases. And when I used caused SQL Server to use 100% cpu and 500+MB of ram. I can't have this.Can anyone give me some tips as to why SQL 2005 is so slow?
I am unable to install 32-bit SQL Server Integration Services on the server due to something that was left behind by the 64-bit version.
I've uninstalled SQL Server 2005 64-bit and when I try to install the 32-bit version of Integration Services, I get this error: "Failed to install and configure assemblies C:Program Files (x86)Microsoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error descrition: FATAL: Could not find component 'Microsoft.SqlServer.Dts.Task.MessageQueueTask.ServCompMQTask' we just installed."
I can't seem to figure out how to resolve this problem with the COM+ and I can't remember if Integration Services is required.
I have some production boxes on Win 2000 32-bits OS and some production servers have been upgraded to Win2003 64-bit OS runing SQL Server 2005. There are also a number of Win2003 32-bit OS running SQL 2005.
The issue is that when linking the 64-bit production servers to the 32-bit boxes running SQL 2005 / Win 2003 OS, the linking seems to succeed, but I am unable to see a number of entries in sys.objects. Typically, these objects are User Stored Procedures.
Moreover, the linking seemed to have worked, but data extraction does not take place between the servers. However, there are no errors. The objects (user stored procs) exist on the 64-bit side, but linking does not actually happen.
Microsoft KB has addressed this in SQL 2000 case in this KB article, but has not suggested a solution for SQL 2005.
After installing SP2 we encounter a problem with MMC. When selecting a DB we recieve a RunTime error? And the DB items/properties are not shown. Is there anyone with the same problem and knows how to fix this? I search the MS site for more information but there is nothing on it.
We are migration few database from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)
Problem :
- The performance difference observer was not much (Just 15-18%)
- The CPU Utilization goes to 100% immediately, when the software login screen appears and it sustains in between 90% to 100%
- Multi-User Access (3 or more concurrent users), the sql performance is tremendously slow.
Steps followed for Migration:
- We have used the backup and restore method to migrate the data from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server).
- We ran the DBCC DBREINDEX for each affected tables
- We executed the sp_updatestats procedure for all the tables
- Upgraded the DB compatibility version to 90
- Installed the SQL 2005 Enterprise Server (64 bit-Itanium Server) Service pack 2.
One thing that we observed, was the memory usage, on SQL 2000 the sqlservr.exe uses around 1.5 GB where as on the SQL 2005 its just 120 MB.
A normal select query on 2000 Server took 11-12 sec, having 10 lac records, and the same query on 2005 took 1 min (3-5 sec CPU process taken by sqlservr and rest by the Sever Management Studio.
The only differance noted was that on 2000 the entire data was displayed at one go where as in 2005 the data was displayed at the 1st sec, and was filling the rest in the buffer, and to finally display entire data it took 1 min.
Also
when we run this query
select * from sys.dm_os_sys_info
one column os_priority_class shows a value = 32 ? what does this means.
In the MSSQLSERVER SERVICES, properties, there is a parameter displaying value
Advanced > Running Under 64 bit OS = No ? what does this means.
Could anyone pls suggest as to how to increase the sqlservr.exe memory area, and also how the enhance the performance.
I am going to install SQL7.0 on the current NT4.0 with SQL6.5 on it by uninstalling SQL6.5 first and then installing (not upgrading through Wizard) SQL7.0.
Here are the questions I need help with: 1. Should I convert the database after the installation of SQL7.0 or directly restore the SQL6.5 databases backup? 2. If I need to convert the databases, How and in what way? 3. Which way is better upgrade or installation?
Current system 2 x 500mhz pIII 512MB ram, System mirrored and data raid 5 30GB made from 3 disks. All server is running in CA TNG. an Asset management DB and Software Delivery database. But the poor server runns most of the time at 100% 65% being used by SqlServer process. Does/Can anyone recommend any tweaks upgrades that may let the server take a breath in and out ie will more memory speed thing up faster processors or more disk.
