I'm rewriting an old application that has a MSDE database as backend. I'm estimating if upgrade the old db to SQL2005 or SQL2005 Express edition, so I'm trying to migrate it to different istances running on different servers. In order to manage servers, I'm using MSQL Management Studio of the SQL2005 evaluation edition. As first step, I have detached the MSDE .mdf file, and attached it to SQL Express server.
QUESTION 1: Is this the right procedure to migrate the db on SQL Express?
QUESTION 2: All seems to work, but in MSQL Management Studio if I point on a stored procedure of the migrated db in SQL Express and right-click, in the context menu doesn't appear the item: 'Execute stored procedure...'. This item instead appears also if I connect to the old MSDE database, and it's very nice during testing....
QUESTION 3: How to grant access in SQL Express server to the old users of the migrated db?
Recently we have migrated our application from MSDE 2000 to SQL Server Express 2005(SP 1). This has significantly reduced the performance of our Windows.NET application which is developed using C#.
For example : While logging in to the application two databases are being attached.
Time taken in MSDE: 16 secs
Time taken in SQL Server Express 2005 : 58 secs Also note performance is degraded for normal screens where data is retrived from database using inline queries.
Questions:
1) Is there any special(optimum) configuration(installation parameters) while installing the SQL Server Express 2005 setup?
2) Is there any query optimization to be done w.r.t SQL Server Express 2005 ?
We highly appreciate any help towards resolving the above problem. Regards, Sasi
I am migrating from MSDE to Sql Server Comapct Edition.I want to how will it affect the code and how large the changes will be. For example will i need to change only the connection string or if some of the methods used by MSDE or not available in the CE version. Any information and ideas reagrding this will be useful.
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?
I have a developer who built an application using the SSE 2005 December CTP and I would like to bring the db's into the official SSE 2005 released version. I have attempted the following:
1. Create the db's in the released version, detach and re-attach the CTP db's. I got an error telling me they were incompatible.
2. Installed CTP version on one server, backed up the db's and then attempted to restore the db's on another server running the official released version of SSE 2005. Got an error attempting that too.
3. Installed the Management Studio for SS 2005 Developer edition thinking that I could connect to the two seperate instances of each server and like I could in EM 2000 run the transfer wizard to move the db's and data from one server to the next. Problem with this is that I can't get an object browser connection established. I have TCP/IP all config'd correctly, too.
Any other ideas where I can go with this at this time?
Hi, I have an ASPNETDB.MDF (asp.net membership/profile db) that was generated for SQL Express, it has user information I need to keep. I have SQLExpress and full SQL Server 2005 running on the server. I want to remove SQL Express from the server. So can I simply do a backup of the SQL Express membership db and restore it to full SQL and change the connection string in my app or do i need to run the membership wizard on full sql and then do the backup / restore? Or is there another way. Thanks
Hey y'all, I'm looking to migrate several databases on SQL 7 and SQL 2000 to a new SQL 2005 box. Has anyone done such a migration? What would you recommend as a good methodology for it? Also, should I expect stored procedures, triggers, indexes, other complementary stuff to break? I'd love to hear about your migration experiences.
We are planning on upgrading a SQL 7 Server to 2005 SP1. I ran the Update Advisor and one of the issues listed was that the Database Maintenance Plan would not work in Server 2005. The Advisor mentions a tool to use but not which one, which is my first question.
I went online and found some documentation regarding copying the database etc., however, when attempting to copy from the SQL 2000 (DB in SQL 7) to 2005 (I have SQL 2000 and 2005 on my machine) when I try and connect to the 2005 box, its listed as one of the instances but will not connect.
For grins and kicks I backed the database up in the 2000 environment and restored it on a test machine which is in 2005. The Advisor was correct, I am unable to create a Database Maintenance Plan, which I find odd. The Database shows up under the databases but will not show up in the list of db's to create a plan for. So, I attempted to create the jobs and alerts manually.
There has to be an easier way to do this, can anyone help?
I have a SQL7 server that runs one database for our company. The rest of the datastore is on a SQL2005 server. How best can I transfer the SQL7 database to SQL2005?????
Hi,I move my website to our production server who use SQL 2005 instead of SQL Express.The website was, of course, developped with SQL Express.Where can i find the steps that i need to configure the SQL 2005 server for working with my SQL Express database.Thanks
I'm in need of migrating DB's from a SQL 2000 server to a new SQL 2005 server. Has anyone had any success in this or does anyone know of a process which would be best for this situation?
Here's my setup...
SQL2000 SERVER....OS - Server 2000 MDF's/LDF's reside on D:MSSQLData Backups reside on D:MSSQLBackup
SQL2005 SERVER....OS - Server 2003 MDF's/LDF's reside on E:MSSQLData Backups reside on E:MSSQLBackup
Any information on how to get these DB from 2000 to 2005 will be greatly appreciated.
Hi, since havenot done migration yet, my company is planning to migrate from sql 2000 to sql 2005 server. and i am in group for capacity planning. can anybody suggest me the steps i should be really taking in order to migrate to 2005, if anyone has done the it in real world with database up to 50g. thanks Derek
Guys! Very very junior in this migration part. Hope the seniors can help out....PLEASE!!!!!! Don't get me wrong asking you guys to spoon feed me. I have read a lot of articles and even BOL and also not to forget read millions of books on this. But just wanted to make sure that I am in the right path and want to do this without any problem. That's why I have decided to ask the Gurus here who have done this in past.
I have this machine now:
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: )
Migrating to this machine:
Microsoft SQL Server 2005 - (X64) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
I have these in the SQL Server 2000 box: 1. Databases, tables (of course) 2. Views 3. Securities(Logins, Roles, Password) 4. DTS packages 5. Jobs 6. Replications 7. Linked Servers 8. Stored Procedures
Every article is different. I was confused at a point of time. Please show me the right way guys!
Yesterday I started this topic and I came step by step higher and now I have finalized my steps to migrate.
Seniors and Gurus and who has done this before, please review and correct me where I am wrong and/or add some tips for me to have this one going on successfully! Thanking all of you guys in advance! Here is what I have:
Before Migrating: 1. Install Service Packs, Security Patches and Hot Fixes 2. Install DTS Designer Tool from Microsoft to prevent conflict and failure of migrating current DTS packages to SQL Server 2005 3. Backup EACH and EVERY Database and double check the .bak files whether it exist and backup was successful 4. Just before migrating, reboot the server to clarify that the SQL Server Services and SQL Server Agent is working When you are ready to migrate: 5. Make sure there are no users trying to connect to the OLD AND the NEW SQL Server. Inform them well in advance about the downtime. Shutdown any applications or websites that might be accessing the SQL Server. 6. Stop the SQL Server, SQL Agent and MS Search Services on the NEW SQL Server If downtime is not possible: 7. For ever changing OLTP database, by the time you restore the backup onto the new server, the old server would have received more changes. To avoid this problem, you need to resort to log shipping. Log shipping is nothing but an automated process of backup and restore. The following steps will explain the process of log shipping (Note that SQL Server 2000 Enterprise Edition provides inbuilt logs hipping. We don't need that for this purpose. We can simply create a job that backs up and restores the databases 8. Create a job on the old server, with two steps. The first steps backs up the transaction log of the OLTP database. The second step restores this transaction log backup file onto the new server, using WITH STANDBY or WITH NORECOVERY option of the RESTORE command. Schedule this job to run every 10 minutes or 15 minutes, depending on the volume of transactions your OLTP database receives 9. This job will take care of shipping all new transactions since the full database backup, to the database on the new server. Let this job run until you can afford some downtime on your production database (that is, mid-night, or early morning, or a planned maintenance window) 10. Now to be doubly sure, no new transactions are coming in, set the database in 'single user' or 'dbo use only' mode. Take one last transaction log backup of the production OLTP database, and restore it onto the database on new server. This time use the WITH RECOVERY option of the RESTORE command 11. Run UPDATE_STATISTIC on User Database to reorganize all indexes Considerations: 12. Security - The security model changed along with object ownership, but users that own objects will be turned into schemas and all of the object and role permissions will come over. These you will want to look over afterwards, but they should be ok. 13. Unless you have hundreds of them, it is always better to re-create them after upgrading. You cannot detach an MSDB database on a 2000 server and attach it on a 2005 server and have it work. Fortunate in this, we can script out the jobs from SQL Server 2000 and run it on the new SQL Server 2005 14. Typically you will have to re-create your replication too. Again, the good news is that you can generate the scripts for replication on a 2000 server and execute them on a 2005 server and it will create the appropriate articles and publications 15. For DTS packages, it is always recommended to use the Package Migration wizard to do this so that less or no problems will be encountered. Consider about the jobs previously set. 16. Logins can be created by using sp_hexadecimal and sp_revlogin2005
Help. I have been tasked with upgrading a 2000 instance to 2005.I have actually done this before, but it was a long time ago, and Ididn't do it alone. Now, the sitation is little different, and I needto know the EXACT steps to take.Does anyone have a FAQ or link that outlines migration steps? I foundone on sql server central, but it isn't very detailed.One of the important things I need to know is, how do I create arollback plan if I am upgrading from 2000 to 2005 on the same server(instance)?Also, why can't I seem to find a comprehensive list of TO DO's whenupgrading? Doesn't microsoft provide this? You would think so. I willrun upgrade advisor first, but isn't there also documentationsomewhere?I seem to recall lots of permissions issues that arose with 2005.HELPThanks
Hello guys, I have vry basic question. I'm migrating from 2000 to 2005. MY question is do we have to recode all packages or just migrating of old 2000 DTS is fine. If so, then I can see only small icon of DTS package in 2005, whihc is not showing the details of DTS. Kindly, explain me what do i really do, migrating old one or re-creating new in 2005. Thanks in Advance
The SQL ERRORLOG shows: Error is 3414, Severity 21, State 2 and says: "An error occurred during recovery, preventing the database 'model' (database ID 3) from restarting." Just prior to this, I get a warning: "did not see LP_CKPT_END".
Any thoughts why this might be and how I can fix this?
Has anyone had experience of migrating from 2000 to 2005 on the same box , and maintaining the SERVERNAMEINSTANCE_NAME. What are some effective ways of migrating and retaining the same servername/instance name ?
The issue revolves around minimising the use of extra boxes , as I would like to do the migration on the same server and keep the name the same .
Jack Vamvas -------------------- Search IT jobs from multiple sources- http://www.ITjobfeed.com
Hi, I have a database on a SQL Server 2000, and would like to migrate it to a new server machine that has SQL Server 2005. has anyone already tried this, and can you please provide the steps to follow.
We are migrating from SQL Server 2000 to 2005. We currently use ADO.Net to make connection to sql server. I just want to know after migration to sql server 2005 do we have to make any changes in code in the way we make connection to use ADO.Net2 which is part of sql server 2005. ??
I am working on a migration project of my database(lets name it DB1), from SQL 2000 to SQL 2005. I have some DTS packages in my SQL 2000 database which also needs to be migrated to SSIS. These DTS packages currently interacts with other database(lets name it DB2) which is also in SQL 2000 and which does the data transmission. The real issue is that the other database(DB2) also has some DTS packages which also communicates with DB1 (the db to be upgraded) and so when i migrate my DB1 to SQL 2005, i will have to change my DB2 packages also (although the change will be minor). Now considering that in future I might also migrate my DB2 to SQL 2005 I wanted to know what will be the right approach to follow. One is to modify the DTS packages of DB2 to accmodate the change in connection and the other is to migrate the DTS packages of DB2 also to SSIS.
Hi guys We are in the process of moving from SQL Server 2000 to 2005. In this process in general I have noticed that performance is better as a result of the move but in a couple of specific cases performance is about 10 time worse as a result of the move and i am wondering if anyone can tell me why.
1) Should I be noticing that calling functions from within a where clause are slower in 2005.
2) Has the and/or logic processing been changed between the different versions.
3) Why does this segment of code run really slow in 2005 but really fast in 2000 (note, i know that its not nice looking but it is pre-existing code from before we came on board and there are more examples of these so its a bit of a change to go through and fix it all up to what it should be but i need to know why before i can move on and as i said i know its not nice and one should expect it to be slow but i specially need to know why it would run fine in 2000 and not on 2005):
..... AND (Deleted = 0) AND (DATEDIFF(d, dbo.GetStartOfDate(ReviewedDate), dbo.GetStartOfDate(GETDATE())) = 3) OR (ProgressPointId = 32) AND (Deleted = 0) AND (DATEDIFF(d, dbo.GetStartOfDate(ReviewedDate), dbo.GetStartOfDate(GETDATE())) = 3) OR (ProgressPointId = 30) AND (Deleted = 0) AND (DATEDIFF(d, dbo.GetStartOfDate(ReviewedDate), dbo.GetStartOfDate(GETDATE())) = 3) ....
I am migrating a database from Oracle to SQL Server 2005. I have a problem when migrating code from PL-SQL (oracle labguage) to T-SQL (sql server language). My problem is: there is pseudo-column in oracle called level that return the level from a register in a tree view of a select (a parent-child relationship). I would want to know how to translate that level column to T-SQL. Thanks!
so as you can see i want to migrate from My SQL 5.0 to MS SQL Express. Is there any free tool provided by microsoft or something else i could to use to migrate my databases. I need this cause old web page was developed on PHP and now it's redeveloped on ASP.NET and i have very strange issues with ASP.NET and MySQL Lots of incompatibility and performace degradation, so i would like to try out MS SQL i think it must be better.
I created a web site using the "personal web site" starter kit with Visual Studio 2005. It created an ASPNET MDF file as well as a Personal.MDF in my App_Data directory.
I want to migrate this site to a production server that does not have SQL Express, but does have a full version of SQL Server 2005.
How do I migrate both the database format (tables and SPs) as well as the data to the SQL Server?
I can't find anything that looks like Enterprise Manager or Query Analyzer on my system, and installing the "native client tools" doesn't do anything except install configuration utilities (no clients).
Inside of Visual Studio 2005, I can bring up both databases (one from the MDF file(s) and one using a connection string to the server), but there doesn't appear to be any way to copy from one to the other.
I'm trying to migrate MS Access 2003 query into SQL Server 2005 view. I'm getting error for the following query.
ERROR: Incorrect syntax near the keyword 'LEFT'
MS-Access query: SELECT tbl.*, tblP.ParticipantLastName, tblP.ParticipantFirstName, tblP.ParticipantAmount, tblP.SocialSecurityNumber, tblP.Comment FROM tbl LEFT JOIN tblP ON tbl.AutoNumber = tblP.RecordNumber WHERE ToBeProcessed='YES' and [Cancel]=0;
SQL Server View: CREATE VIEW dbo.[qryReport] AS /* * Generated by SQL Server Migration Assistant for Access. * Contact accssma@microsoft.com or visit http://www.microsoft.com/sql/migration for more information. */
SELECT tbl.*, tblP.ParticipantLastName, tblP.ParticipantFirstName, tblP.ParticipantAmount, tblP.SocialSecurityNumber, tblP.Comment FROM tbl AS LEFT JOIN tblP ON tbl.AutoNumber = tblP.RecordNumber WHERE (ToBeProcessed = 'YES' AND [Cancel] = 0)
I have a database created on SQL Server 2005 and now I would like to migrate the table structure to a SQL Server 2005 Mobile database. Generating the scripts and running them against the mobile database generates a lot of error that I suppose are caused by not supported features or keywords on the mobile engine.
I would like to know what are the best procedure for doing such migration. Note that this has nothing to do with replicating, since the SQL Server 2005 database will be "discontinued" after the migration.
I want to move my sql express DB to a sql 2005 server located at a service provider. I can detach or back, but I am limited on attaching or restoring the DB because the servers are on two limted/seperated networks.
Is scripting an idea? I have SQL manager 2005 running.
