Tag Info

New answers tagged

0

According the error message posted in the comments this is a faulty disk that cannot serve write requests (at a certain location).


0

Instead of just replacing the Database can they not script the changes (schema/data) and run the changes on the existing db at your site?


2

Converting my comment to answer (read the comments in the script) : if you are using the same backup file name (ICT.bak) every time you backup, its better to use INIT. This way the previous file gets overwritten. USE master -- here no need to use the name of the database that you are backing up. Other RDBMS like SybaseASE will thorw an error saying that ...


1

I've got a couple of blog posts on this, the process is fairly simple: Using SQL Configuration manager, stop the SQL Server instance Open a command window In the command window, start the instance executable in maintenance mode In a second command window, open SQLCMD Restore master from within the SQLCMD window Using SQL configuration manager, restart ...


2

Start SQL Server with the -m parameter, specifying the application name allowed to take the only available connection. For instance, to allow sqlcmd to take the connection: sqlservr -m"sqlcmd" If you want to work with SQL Server Management Studio, use this: sqlservr -m"Microsoft SQL Server Management Studio - Query" Remember that the "Connect..." ...


0

Check for any external connections connecting on the same port # using netstat. Sometimes application services that automatically connect to the instance keep connecting even if you've declared a maintenance window like this. Once identified, disable them at the source, or temporarily block them by firewall rule, change in port # or disabling the external ...


1

Make sure the SQL Server Agent service is turned off before switching the server in single user mode because when you start an instance of SQL Server in single-user mode and if you have not stopped SQL Server Agent service before hand SQL Server Agent might connect first and prevent you from connecting as a second user. The same has been documented by ...


0

If you are trying to restore db from a server to another server and db is not exist on restore server, you can try method below. That problem may occur depends on this reason; DB files could be locate on different disk names which is not exist on restore server. To solve the problem on restore server; create a db and db files which are attached with the ...


0

I know this is a little bit late. but you seem to have a similar process like ours. where you need to pull backup from live and restore to test database. Please check the below script that automates the whole process. at the end of the script published you will find a xml configuration data. copy it and place it in a separate .xml file. ...


4

Unfortunately no, you can't exclude anything from a backup. If you are talking about Windows Logins then it probably isn't that big a deal. The SIDs won't match anything on their network (very unlikely anyway) so all they will have is the usernames without any of the permissions associated. SQL Logins of course will work fine as long as they create a ...


2

The basic answer is: No. Do you have a record of the 18-20 digit value somewhere? In another location in your database, on a piece of paper on you desk, etc? If so then use the source information to correct your error. You have not indicated which database software you are using, which can make a difference for many issues.



Top 50 recent answers are included