Viewing 15 posts - 241 through 255 (of 501 total)
SQLDTS.com has lots of info about DTS packages. I would start there.
http://www.sqldts.com/204.aspx
You can use DTSBackup from the site also to convert packages to structured storage files.
August 26, 2010 at 5:11 pm
Create a job on your main SQL 2005 server with an Operating system(cmdExec) job step and use SQLCMD. For example:
SQLCMD -E -S SERVER\SQLEXPRESS -Q"BACKUP DATABASE <dbname> TO DISK = 'C:\dbname.bak'"
August 26, 2010 at 3:28 pm
Dan Guzman - Not the MVP (8/20/2010)
Why not just fail over to the secondary full time, so that you can upgrade the primary offline. If all goes well, fail...
August 20, 2010 at 11:19 am
That should work as long as the transaction log on the principal is large enough to hold all the transactions during the upgrade.
August 19, 2010 at 8:52 pm
You could do a backup and restore from the physical to the virtual machine or you can do a detach and attach. Either way should work fine. I prefer backup...
August 19, 2010 at 4:09 pm
You need to add trace flag 845 as a startup trace flag in order to use lock pages in memory for SQL 2005 Standard.
August 19, 2010 at 3:50 pm
RaviShankar1234 (8/18/2010)
and if I defragment the data using indexes on primary server will there would be a effect of defragmentation of secondary server also?
Yes, the secondary database's index in...
August 19, 2010 at 3:31 pm
Dan Guzman - Not the MVP (8/19/2010)
Or, did you...
August 19, 2010 at 12:44 pm
The reason for disabling the restore transaction log job on the secondary was given in the 3rd paragraph of the article.
"Once we convert the mirrored database to a log shipped...
August 19, 2010 at 11:22 am
You may have to delete the mirroring endpoint as well if there are no databases mirrored. There are various other internal tasks to SQL Server that use Service Broker also....
August 19, 2010 at 10:39 am
Is it possible that SQL was not setup on the default port of 1433? In that case, you would need to connect using <SERVERNAME>,<PORT#>
Is it a named instance? Connect using...
August 17, 2010 at 3:54 pm
Have you tried running sp_removedbreplication on database "B" once it was restored to server "B"?
August 17, 2010 at 3:40 pm
I haven't had any issue connection to SQL 2008 R2 using SSMS 2005 or 2008. However, the 2008 features are not available when using SSMS 2005 to connect.
Why not install...
August 17, 2010 at 3:30 pm
Enable filestream, remove the filestream file from the database files, remove the filestream filegroup, and disable filestream again. That should solve your issue.
August 16, 2010 at 4:23 pm
Viewing 15 posts - 241 through 255 (of 501 total)