Hi! I have an SQL server installation with a 6.5GB database online at a particular location. I need to move the Database to another location which is a 1000 Miles away.
I have an additional physical Server at the other location which I can use to Sync the database from the original location. Can anyone please guide me to the best strategy to sync the database from the original location to the new location with minimum downtime??
I may be put on a project involving the migration of a SQL Server 2000 database from one physical location to another. I've never done something like this so any guidance would be appreciated.
My plan is to: 1. Backup the live database. 2. Do a restoration at the new location. 3. Set up transactional replication between the two databases. 4. Update records to point to the new db.
Are there any problems with doing it this way? Is there a better solution? I am trying to do this without any downtime, or as little as possible.
Hello all,We are in the process of upgrading our SQL physical server (with SS2k). Inthe process we will change the OS form NT4 to W2K. What is the best way tocopy all my databases and SQL logins, roles, jobs, alerts, etc. from myactual (old) SQL Server to my new one?Thanks for your time.Yannick
I need to bulk insert very large amount of data into several MSSQLtables.The first Data model definition used identities to mantain relationshipbetween those tables but we found that natural keys (compound) arebetter forbulk insert (there is no need to obtain the identity first)My question is, changing the identities to natural keys (in some tablesinorder of 4, 5 attributes) will enlarge my database storage?I think MSSQL implements relationships with pointers (or hashcodes), sothestorage size will be similar, right?Regards,
I've recently started working with a public sector organisation who have 4 clustered sql instances that has 80% of it's db mirrored.
Looking at the transaction log - it seems that a transaction log backup is a good idea as the log is 4x larger than the data file.But I'm not allowed access to the physical server to check onto which drive I can create the trn. No RDP, no vmware - let's be honest I'm not even allowed to launch cmd line Also the Server Manager informs me "We will need to carefully look at database backups if you guys want to start doing these backups on box, as that will break our off box backup routine (it will screw the transaction chain)."
I don't understand how backing up the transaction log could break the "transaction chain"?
Re: Best Practices (security): Should SQL Server (2005) *not* be installed on the same physical HD as the Windows OS (Server 2003 R2) ?
Hi,
We're setting up some new servers, and today I'm looking into best practices for the SQL Server Setup portion of it.
The servers have include 2 x 250G HD, and from what I've read, where IIS is concerned, it should not be installed on the drive that has the OS on it, for security reasons. I was wondering if the installation of SQL Server should be on the non-OS drive as well ?
Hi All, Is it possbile to define connection string for web and database server which is running on different machine. Note( Not same LAN). E.g (My Web Server is in London and Database server in Sydney). Please can any one help me.?? Thanks in advance...
Hello! What is the best way to make a copy of an existing sql server database to another (physical) server? Plan to make a full backup of another sql server database to another server. I've read about detach and attach and copying the datafiles and log files but some say it is prone to data loss? Is this true?
And another thing, what if the existing sql server can't affor downtime for me to copy db files etc.?
Hi,We have a situation where we want to move our current databaseserver to a different hardware and rename the server.If we change the Physical server name, do we have to go thru the wholeprocess of changing it in sql server by running sp_dropserver,sp_addserver?Can we have an alias for the server name in DNS and can sql serverresolve the server name internally by going thru DNS?For eg: Our current database server name is FFSQL-PRD01. We have itregistered in EM as FFSQL-PRD01. Now we renamed the server toSTLSQL-PRD01, and added an entry in DNS for STLSQL-PRD01 with alias ofFFSQL-PRD01( the same old name as alias). After doing this when I goto EM and click on FFSQL-PRD01 would it give me an error? or can itresolve the server name by going to DNS.When you install SQl server the default instance has to be the physicalserver name, Why? Is the physical server name stored in Masterdatabase( SYSSERVERS table)?Thanks for your help.Geetha
I want to compare the filepath column in table with physical drive files and get the details of files which in table and not in physical and viceversa...
We have a server running SQL Server 2000 Standard Edition on a Windows 2003 Standard Edition Server. Can we install SQL Server 2005 Standard Edition on the same box? I'm assuming that so long as the instance names are different that it should not be a problem.
I am trying to figure out the best method for transferring SQL 2005 databases from 2 different physical servers to a new server running windows server 2008 64bit.I own a fully registered copy of Microsoft SQL 2005 32bit Standard Edition. However all of my SQL databases together are only 4GB in size thereby making 2008 SQL Express an option.
Here is the breakdown of the servers:
1) (Old Server1) Windows 2003 Server 32bit - SQL Express 2005 32bit 2) (Old Server2) Windows 2003 Server 32bit - SQL Server 2005 32bit Standard 3) (New Server) Windows 2008 Server 64bit - (Not sure which version to install)
**The objective is to migrate 2 SQL databases from Old Server1 and 1 SQL database from Old Server 2 to the New Server. What version should I install on the new server??? Do I go with 2008 express or install the 2005 Standard Edition?
Pending your response to which version to install, what are the correct steps to migrate (which I have never done before) the databases from both of these servers to the new server? I think this particular situation is unique in that I am transferring from both SQL Express and Standard from 2 different physical servers to a 2008 server that is 64bit.
I've been trying to get a definitive answer to this question but alas I have conflicting and patchy answers so far from other sources. I have an index that, lets say, requires 10GB of data space to rebuild..This index resides on a filegroup that spans 2 files on two seperate drives (i.e. a mdf and ndf)
When I rebuild this index how will each of these datafiles grow as the rebuild proceeds to completion? Lets for the time being remove the caveats of any other activity hitting the example index/database in question.My tests seem to show that only the mdf will grows (or the file with the lowest id in the that filegroup) provided there is enough space available in that particular file to complete the operation. The secondary ndf dat file doesnt grow at all if the mdf has enough space.
Is expected behavior? i.e. the index will be rebuilt in a contiguous manner relative to the files contained with the filegroup i.e. fileid 1 will grow till limit reached then next fileid grows etc?
I have a an asp.net application running under IIS. this application is using two folders, the virtual directory under C:Inetpubwwwroot and the application phisical folder at C:. I want to manage this applications .mdf database using microsoft sql server management studio express(iam running sql express with advanced services) which means i have to attach the database to Ms sql server managemet studio express tool. What i dont know is if i should attach the .mdf file in the physical folder's App_Data folder at C:myapplicationFolderApp_data or the .mdf file in the virtual directory under C:InetpubwwwrootMyapplicationFolderApp_Data I dont know which of the two i should attach. Where exactly is the running database, the .mdf file in the physical folder or the .mdf file in the virtual directory under wwwroot.
1. Do SQL server versions 6.5 and 7.0 co-exist with each other on the same physical server[OS : WinNT 4.0 SP6]. 2. Can I access the databases of different versions of SQL Server [Version 6.5 and 7.0] at the same time on a single server.
hi, We have machine where SQL 2005 server is installed.Atleast 3 web applications are running on it with data size 22GB in all. We need to migrate all data/tables/groups/users from this server to another server.On target server, SQL server 2005 will be installed.After that this migration activity needs to be carried out.what are options available to migrate to target server? Microsoft migration tool? Any already existing stored procedure etc?which is preferred solution in such case?
We have sql server 7 Sqlserver ServicePack SP3 Sort Order = 32 BuildNumber 7.00.961
on Windows NT,Now we are planning to upgrade operating system from win NT machine to windows 2000. Please let me know what and all precausion do i need to take what and what all backup should be done apart from user database. How do i take care of the users,logins,roles, DTS Job and Replication.
Please help me in this and also any links if u have on this topic
Soon I shall have to migrate 2 medium sized databases from SQL server 7 to 2005. Any words of wisdom, “how to�, “do and don’t� would be greatly appreciated.
Here are the details: SQL 7.0 SP4, on Win2000 SQL 2005SP1,on Win2003
Sql 2005 needs to be installed on a new server (Win 2003), which will also be used as a web server (IIS6). I was thinking to go with a clean install for sql 2005 first, and after that to migrate the databases.
When i tried to migrate to SQL Server 2005, it is working fine in the SQL Server 2005 installed in Windows 2003 Server. System tables(syscolumns, sysobjects etc)are created in "Database->Tables->SystemTable".
But when i tried to run in SQL Server 2005 installed in Windows XP, I'm facing the following problems.
1."The object 'CK_SavedSear_LastL_4B422AD5' is dependent on column'LastLoadedTime'
"ALTER TABLE DROP COLUMN LastLoadedTime failed because one or more objects access this column"
2.Moreover none of the tables had been created in "Database->Tables->SystemTable".
In both XP and 2003 Server, While installing, i have choosen same options.
Please anybody could help me to resolve this issue.
I'm migrating 15 user databases from one server to another. The current production server is Windows 2000 Server SP4 and SQL Server 2000 Standard Edition SP4. The new production server is Windows 2003 Server and SQL Server 2000 Enterprise Edition SP4. The new server does not have the same directory structure as the current server.
I plan to detach the database, move the .mdb and .ldb files to the new server and then attach the database again. I'm not sure what to do with the master and msdb databases. Do I need to bring over the master? I know I need the msdb for all the job information. Since these are system databases, do I need to follow a different process? I want to get all these databases over to the new server so I can begin some parallel testing prior to the final cutover.
For anyone that has gone through this process, is there anything that I need to pay special attention to? Any issues moving from Windows 2000 to Windows 2003 or SQL Server 2000 Standard to SQL Server Enterprise Edition?
When i tried to migrate to SQL Server 2005, it is working fine in the SQL Server 2005 installed in Windows 2003 Server. System tables(syscolumns, sysobjects etc)are created in "Database->Tables->SystemTable".
But when i tried to run in SQL Server 2005 installed in Windows XP, I'm facing the following problems.
1."The object 'CK_SavedSear_LastL_4B422AD5' is dependent on column'LastLoadedTime'
"ALTER TABLE DROP COLUMN LastLoadedTime failed because one or more objects access this column"
2.Moreover none of the tables had been created in "Database->Tables->SystemTable".
In both XP and 2003 Server, While installing, i have choosen same options.
Please anybody could help me to resolve this issue.
Scenario Recently moved a SQL2000 database to SQL2005. Collation on SQL 2000 database server was SQL_Latin1_General_CP1_CI_AS Colaltion on SQL 2005 database server is Latin1_General_CI_AS
After restoring the SQL 2000 database on SQL 2005 we observed that the database collation was SQL_Latin1_General_CP1_CI_AS. We have altered the database collation to Latin1_General_CI_AS. We understand this will work for all new objects created on the database but existing objects (prior to the collation change) will continue to have the 'SQL_Latin1_General_CP1_CI_AS' collation.
What is the best method to change the collation of the older columns to 'Latin1_General_CI_AS' - 1) Run ALTER TABLE ALTER COLUMN <colname> <datatype> COLLATE Latin1_General_CI_AS <nullability> on each varchar/char column
or
2) For each table BCP out data DROP TABLE RECREATE TABLE (taking the new collation Latin1_General_CI_AS) BCP in data
I had to to relocate the database log file and I issued an Alter database command but by mistake I put a space in the file name as below. The space is at the beginning file name. Now I am unable get the database loaded to SQL Server. The database has 2 replications configured, so deleting and re-attaching the database means the replication needs to be re-configured. Is there an alternative way to issue a command to update the database FILENAME ? Not sure if this can be edited in master database (sys files).
ALTER DATABASE [User_DB] MODIFY FILE (NAME = User_DB_log, FILENAME = 'I:SQLLogs User_DB_log.ldf') GO
Hi... I was hoping if someone could share me some thoughts with the issue that I am having at the moment.
Problem: When I run the package in my local machine and update local SS DB/table - new records writes OK in the table. BUT when I changed my destination meaning write record into another physical SS DB/table there is no INSERT data occurs. AND SO when I move/copy over that same package into another server (e.g. server that do not write record earlier) and run it locally IT WORKS fine too.
What I am trying to do is very simple - Add new records in a SS table using SSIS . I only care for new rows and not even changed rows. Here is my logic - 1. Create Ole DB source to RemoteSERVER - using SELECT stmt 2. I have LoopUp component that will look for NEW records - Directs all rows that don't find match and redirect rows (error output). 3. Since I don't care for any rows that is matched in my lookup - I do nothing or I trash the rows 4. I send the error rows (NEW rows) into OleDB destination
RESULTS when I run the package locally and destination table is also local - WORKS FINE; But when I run the package locally and destination table is in another Sserver (remote) - now rows is written.
The package is run thru BIDS manually so there is no sucurity restrictions attached to it.
I am not sure what I am missing. And I do not see error in my package either. It is not failing.
hi, i need some help here,i made a simple data driven website in my development PC, at first, i used MS Access for my data base then i migrate it to sql server express 2005, and it works fine when i try to run it in my development PC with my IIS. but of course i will be deploying it to a real server, in our office were i will deploy my data driven site, we have a PC server Win Server 2003 with SQL Server 2000 Enterprise (im not pretty sure by the name but i know its not a free version, its something like a 2000 sql version with a word enterprise at the end).so my question is, i am developing an ASPdotNET site originally used SQL server 2005 express,how can i migrate my site to the Win Server 2003 and my database from SQL Server 2005 express to SQL server 2000 enterprisewill it work?? if not, what are the possible solution that i can do in cases like mine?i used Visual Web Developer 2008 Express Ed. in making my sites, and its DOES NOT allow databases in SQL Server 2000!!!!!it says "can't recognize the database"i hope you can help me with this.Thanks-SALAMAT PO....=)
