Tag Info

New answers tagged

4

Is your SQL Server instance existing in your local system (laptop/desktop) or in some other system (server?). If it's on server then go and look for C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup on the server


2

The only thing you're really changing by using simple recovery is you're shifting the time when you have to perform additional backup work. Instead of taking log backups throughout the process (which shouldn't be extra work, because you should already be doing that!), now you have to take a full backup at the end of the process. In the meantime, you've ...


0

Method1: The Best method to achieve this would be using Olla hallengren Backup scripts. You can find the scripts at https://ola.hallengren.com/downloads.html First thing you need to do is execute CommandExecute.sql script and then run the databasebackup.sql script. Once done you can execute below via SQL Agent job as per you're required schedule: ...


2

We want to keep old databases "alive" for some period of time but once we've gone live we don’t want staff accidentally going into old database, so taking the database offline for awhile then drop it would be the solution? Instead of making database OFFLINE, make the database "READ ONLY" using : ALTER DATABASE database_name SET READ_ONLY And monitor ...


0

In the end I couldn't get mysqldump to login as root, it kept trying to login as ODBC. Instead I added this to my my.ini file and ran the command without user/password arguments: [mysqldump] user=root password=XYZ


2

This problem occurs because the network firewall filters Kerberos traffic. To resolve this problem, configure the network firewall so that TCP port 88 and UDP port 88 are not blocked for either domain. http://support.microsoft.com/kb/938457 Sorry for just quoting... Another thing to check is to make sure that your Service Startup account for SQL ...


2

I searched on web, but could not find any such stuff which clarifies on what point should we or should we not change the compatibility level of the migrated db's. As a good practice and suggested by Microsoft you should change compatibility level of database to match with server version on which it is hosted. There are few legacy applications which ...


0

Matthew's answer is really straightforward, but has one major drawback, it's the restoration part, which can take hours on huge databases (thus increasing the replication delta). To avoid that part, one could leverage LVM snapshots. I'm assuming the following: the database data partition is a Logical Volume (version 2 to allow write operations on ...



Top 50 recent answers are included