Migration To SQL 2005 ... How To Setup The New Enviroment
Feb 28, 2007
Hello,
I have been made the point person for our migration to SQL2005. We are a law firm with approximately 750 users. The first SQL environment we will be upgrading is our document management system (DMS). This is an intensive SQL product. After this migration we will more of to our finical system, records system and then all home grown databases.
What we would like to do is consolidate servers and scale out the new SQL environment to a farm. After some initial research it does not look like we will be able to scale out, since the data in the DMS is always changing.
Does anyone have some advice or guidance on what direction we should be looking? I have done tons a online searches and can find out information on everything to do with SQL, except this.
I was wondering what was the limitations of Sql Server 2005 standard w/ 1 calThis is the version that is given out at the launch events.We are currently developing a site, that will use Sql Databases and was wondering if the version we have now will work.Like we know for a fact that the site will recieve a decent amount of traffic. Is standard limited to certain kind of sites and so forth?Thanks,Cedric
I posted a question yesterday (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1717961&SiteID=1) that was very specific concerning problems running WCF inside SQL. I guess its quite unlikely that anyone will have had the same problem so I'd like to ask a more general question.
What is it that is different about running a .Net method contained in an UNSAFE assembly inside SQL than running it from a console application or mstest?
One difference is the identity (typically NT Authority/System) but I've discounted that by temporarily running SQLSvr under my interaction administrator account.
One gets a lot of warnings when importing system assemblies into SQL about them not being tested but is there much different about the execution environment.
I guess one difference is the assembly loading subsystem - not fusion in SQL's case. One can't access assemblies in the GAC or in probing paths. Any other differences that might give me a clue as to why I can't get my WCF channel to work?
I have SQL Server 7.0 installed on a shared disk resource in a cluster group. I am wanting to use Outlook 98 ( 97 or 2000 will also be fine if it matters) for the mail profile. Do I install Outlook on the local server drive and reference that in SQL Mail or do I install Outlook on the shared resource drive and reference it there? Any suggestions would be greatly appreciated.
Hi all, I think I have the right group, if I don't then I doapologize.My problem is that I'm trying to run a SQL script within a VBEnvironment. The actual program is WISE Installer, but I'm sure thatthe same problem arise within VB because we have also wrote an appthat is meant to run SQL scripts (But falls over the same). Basically,there are some SQL keywords that are Query Analyser only.. ie: GODoes anyone know of a list of Query only statements? The code belowfails, but since it's not as verbose as Query, all I'm getting is'INCORRECT SYNTAX NEAR THE KEYWORD "PROCEDURE". Here's what's aroundit:^^^^^^^^^^^^^^^^^^ More stuff aboveSET ANSI_NULLS OFFCREATE PROCEDURE ASP_OutstandingStaffingRequirements@stDate as datetime, @enDate as datetime, @locId as integer,@gradeCount as IntegerASCreate Table #glb_outshifts^^^^^^^^^^^^^^^^^^^ More stuff below.Any help would be great as I'm banging my head against the wall here.BTW.. I don't actually know what the SQL script does, I'm just tryingto package together a deployment solution.Many Many Thanks. Regards Mark (SQL GURU.. LOL)
Im about to start a project that will be hosted by a third party web host. What is a common way to backup your database and have the backup saved ? The data may end up being several 100 MB of user settings, text etc (blog type stuff). If the DB gets to be several 100MB, then does making a backup and ftping it offsite sound reasonable ? Does ftp bandwidth usually count against your overall bandwidth usage ?
I have SQL 2005 database mirrror enviroment with MS jdbc driver 1.1. From code, I need to get server name that current connection connect to at run time (which server that the current connection connect to: Priciple server or mirror server). Any help for that?
I need to upgrade a solution from SQL Express Advanced to Workgroup Edition because of the 4GB size limit. I'm planning on deploying the solution in an secure web enviroment were only authenticated users will be able to access the database. The actual username's and passwords would be stored in an Express database. Therefore since only named users would be accessing the database server web app, can I use the CAL license model??
I used 3 seperate web.config files - one for Development seerver, one for Certification server, and one for Production server. The only difference between these three is the within the <connectionStrings> tags. For Example: <connectionStrings><add name="strConn" connectionString="server=xxx;uid=xxxx;pwd=xxxxx;database=yyy;"/></connectionStrings> Within Development the connectionString points to the Development SQL server, Cert to cert SQL, and Prod to Prod SQL. I do not have permissions to copy new Web.Config files into Cert or Prod, so when I have a change within my web.config I have to have another group manually add these files. Is there a way to identify the domain I am curernt within and use a specific set of connections string within the web.config based off this information. If so, can anyone post an example of how to do this...
i have installed SQLEXPRESS (SQL Server 9.0.3042) on my windows ultimate laptop. of late am facing this issue of database. this database is from SQl 7.0 Desktop edition(the one that i use in my office machine with Xp SP2). As such it works fine in SQL 2000 server after attachment (for test).
i have run SQLEXPRESS as administrator to make/attach new database. i can attach the database easily and can even view tables and other stuffs inside database in administrator mode. the issue pops up when i run SQLEXPRESS in normal mode. when i try to open and view the same DB's content, error pops up stating
"The database XXX is not accessible. (Micorosoft.sqlserver.express.objectExplorer)"
i cannot access this DB via VB 6 form as it dosnt show up at all in database list when tried to connect via ADODC.
i want to make this DB accessibility as normal operation, not previliged only to administrator as application run on normal mode only.
the issue dosnt arise when i locally make a new database as it can be accessed when run in normal mode also. why does this happen to database that is attached and not to ones locally made.
pls guide me as i usually do my works at home and making whole database again will surely take lots of pain. why not it just attach then start working, not asking for preveliged mode.
I have to transfer existing DTS packages from sqlserver 2000 to sqlserver 2005, Please let me know the steps by which i can migrate all the runing DTS into SSIS into sqlserver 2005
Hi All, We are planning to move from sql server 2000 and sql server 2005. Just want to know how well is the backward compatibility and things that we should take care of before migration.
I have to migrate our existing SQL Server 2000 (standard edition) running on Windows 2000 server (32 bit) to a new windows 2003 server (64 bit) (SQL 2005 standard edition). I am thinking of doing this migratin after hours (or may be on weekend so a
I have planned the following steps (in order).
1. Install SQL Server 2005 on new server.(windows authenticatin and a SQL server will be running on a separate domain account)
2. Download SQL server upgrade advisor on current SQL Server 2000 (windows 2000) and run a report.
3. Back up (Full) SQL Server 2000
4. Script logins and schedule tasks on SQL 2000
5. Restore database on SQL 2005
6. Create jobs by runing Jobs scripit on SQL 2005
7. Create users and passwords by running the exported script file. Please refer to: How to transfer logins and passwords between instances of SQL Server http://support.microsoft.com/kb/246133/en-us
I am aware that I might face issues of db compatibility level, statistics out of date so I need to update statistics and may be redindex all my tables
PLEASE LET ME Know if I am missing something obvious? Not sure about our existing DTS packages? Any information. Right now I am just thiking of running all my existing 2000 DTS in 2005 as legacy
Note: Rob, Tara, Michael Valentine Jones, Mladen or Nigel , if you cam provide some input from your wealth of experience on this matter. I would sincerely appreciate it.
HiWe are going to upgrade from SQL 2002 to 2005. We have approx. 100mrows of data on the main table and hand of stored procs and views.What we had in mind was that we would dts the data out, script thestored procs and view out and import the it back into SQL 2005.Is there smarter way of doing this?The key thing is that the data must be cleanThanks
I got a SqlServer 6.5 that i want to migrate to SqlSever2005. Does someone knows if is possible to migrate directly with an one-step operation without encountering compatibility or any other types of problems?
We are currently on SQL Server 2000. We have another server that has SQL SERVER 2005. The exisiting SQL SERVER 2005, is a production server, used for Reports in SSRS 2005 In the next 2 mths, we need to migrate our dbs to SQL Server 2005. First off, I would like to TEST and ensure all the dbs/pkgs etc run fine in 2005 before I go live . I need to know how do I get started with TESTING this, i.e. how do I move the dbs from existing 2000 server to sql server 2005?
Looking a preparing a SQL 2000 to SQL 2005 Migration Plan to include the following points. It will be a side-by-side migration where the current environment will run in parallel with the new.
1. Assessment of current SQL 2000 environment. (Hardware, Databases, SQL components such as DTS) 2. Seqence for Steps to perform duing the migration 3. Required resources 4. TimelinesAnyone have such as plan?
I am trying to migrate Databases from MS SQL 2000 (server A) to MS sql 2005 (server B).
The problem i have when i use database copy wizard is that it gives an error and the login will not be migrated .
I tried backup and restore of the databases as well as detach and attach.All cases the logins will have a problem.
For example say for database intranet all the tables stored procedures etc gets migrated but under security >>users (say intrauser) i double click user and the the login name wont appear .and when i try to close the window it says login name must be specified(SQLmanagerUI)
Not that I am expecting anything to be done about this, but why did MS make the SQL 2005 Upgrade Advisor so unfriendly and slow for people that are doing a simple migration? Our organization is migrating everything from SQL 2000 to SQL 2005 one database at a time, and I have the responsibility of running the advisor and checking if there are any MIGRATION ISSUES. We are not concerned with the DTS Packages at this time, because we are doing a side-by-side migration. I do not need the Advisor to check the DTS packages (and even though I tell the Advisor not to, it still does), nor do I need it to check the SQL Server for Upgrade Issues every time I need to check a different database. The worst problem is that I cannot save the reports in a custom location for each database and strip out the useless information that I do not require.
Why can't we get a MIGRATION WIZARD that ONLY checks the Database for problems when doing a side-by-side migration? This would probably save me 1-3 minutes per database and we have about well over the 400 mark with production databases.
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Greetings, I am using SQL Server 2005 and I want a clue if there is some good built-in support to do the following. I want to transfer all the data from one source database to another destination database having same number to tables and schema like source database. I also want to ensure that the old data on the destination database should be secure too. I have an idea that this can be done through SSIS in coding but can anyone give me a guide, tip, link, sample code that can be helpful. Thanx a million in advance. Regards
Hi all, i was just thrown into SQL stuff at my job. For now I need to complete a migration, but soon i'm being sent to training to make sure that I can do this easier later. Heres my question
I backed up the database, then restored it to the new server. That worked fine. I couldn't log in...so i did some searching and found out about the sp_change_users_login command, I got my login fixed and I can log in. Now, I have about 1000 other users to change and I don't want to do those manually. Noone is using this database, so if needed, I could back it up and restore it differnetly if needed or If someone can give me a .sql file to run to fix all usernames and tell me how to run a .sql (i'm that new to it) that would be REALLY appreciated. Anyway, thanks in advance, looking forward to SQL administration.
OK so I'm just the Network Admin here, but our DBA's are off doing other stuff. So I thought I may inquire here about how the easiest way to migrate from SQL Server 2000 to 2005? The first server I'd like to migrate is just databases with a few users, no DTS packages or anything like that... The only problem is that there are several hundred db's, so moving them one at a time is not an option. Has anyone here had successful experience with doing this? Thanks in advance for your help! -Andrew
and it seems really straight forward. does this tutorial cover everything i need to do for data migration? do i need to watch out for anything? if anyone knows of a better tutorial please let me know. thanks for the help.
I have Restored database from SQL server 2000 to SQL server 2005 and found that Full Text catalogs are not Populated.
I tried using, exec sp_fulltext_catalog 'CatalogName', 'start_full' and it showed the message "Warning: Request to start a full-text index population on table or indexed view 'dbo.Corpora' is ignored because a population is currently active for this table or indexed view."
Please let me know on "How to Repopulate all the Full text catalogs"
Hi all, I am Migrating a database from sybase to sql server 2000. I Have already created objects in sql server 2000. I have to only populate it with the data. I have decided to genrate insert script from the aquadata tool and run the script againgt sql server database. It works fine except for few table which have 1,50,000 and 9,00,000 rows. It shows insufficent memory error when i try to run the script with 1,50,000 and the script with 9,00,000 doesn't open in management studio. Please help.
Hi all. I'll say from the get go that I'm no SQL guru. I'm primarily a web dev who has been given the data jobs kind of by default so I'm definitely no DBA.
Anyway, having established my noobness, I have encountered an issue. The employer recently decided to upgrade our databases from 2000 to 2005 and I have been tasked to migrate the data from old to new. I have discovered the Import/Export Wizard and got it to move all the data in a dev database we use...but there was one problem. It seems that the tables in 2000 that had columns designated as identity columns do not have the identity attribute when they arrive in 2005.
I haven't figured a way to alter them to give them that attribute once they're in 2005 so I'm wondering if there's something I can do/change in the import process that would retain the identity property of the columns if I were to re-import them.
This is my first migration attempt so dumping it and starting over is no great loss...but any help would be most appreciated.
