Tag Info

New answers tagged

0

This is due to the fact that your windows user may not be privileged to change the authentication mode. Your local user isn't assigned to the windows group "Administrators" or has the needed permissions for this. You can read more about it here and here.


0

This could be a lot of things. Did your server crash? Have you made any changes? First of all, just for giggles: dbcc checkdb (model) dbcc checkdb (msdb) If that checks out, check the ntfs permissions for the database files. Make sure SQL Server has access to them. Also check the disk where the files live and make sure that it's healthy. If the ...


0

Old question, I know, but a way of forcing (newer, at least) SQL to release memory is to write an application allocating as much memory as it can in chunks, waiting for (say) 15 seconds (e.g. Sleep(15000)) and the freeing the allocated memory and exiting; I tried this and SQL does release the memory so the system gets back its RAM; writing code like the ...


0

Is Transactional replication with initial snapshot replication the best solution or mirroring the best solution. With database mirroring, the mirror will be offline and not queryable. If you want the replica to be queryable, you'll need to either use replication or log shipping to standby mode. As for Replication: Are there any best practices ...


0

I ran into this exact same issue, the ObjectExploer service doesn't exist in the same context on Windows server 2008, which is what i am assuming you are running (Server 2003 EOL's soon, so i am gussing you're no longer on it). I backed up the registry and did the same registry edit you found and everything went fine. One can't be certain if your ...


1

What is the login account that is running the script? You have to make sure that the login running the script, whether it is SQL Agent account or some other account has write permissions on the folder where you are copying the files to.


0

I've had this issue several times. The easiest resolution, if you are more comfortable with SSMS is to prep the restore as you did originally, but then click on the Script button in the Restore dialog. This will spit out something similar to this: RESTORE DATABASE [UAT] FROM DISK = N'd:\Database_backup\mydifferentialbackup.bak' WITH FILE = 1, MOVE ...


-1

USE master; GO DENY VIEW ANY DATABASE TO [loginname]; GO USE [your db]; GO DROP USER [loginname]; GO USE master; GO ALTER AUTHORIZATION ON DATABASE::[your db]TO [loginname]; GO


4

You can use Microsoft's log parser utility. It has the capability of dumping into a SQL database as well as having the ability to create a checkpoint file so that it only imports records it hasn't processed. It can be used either as a stand alone executable or programmatically invoked via an ActiveX control


1

You can also fetch the data direct per SQL on your target Server. If you have network access: SELECT a.* INTO <YOUR TARGET TABLE> FROM OPENROWSET('SQLNCLI', 'Server=<IP/SERVERNAME>;Trusted_Connection=yes;', 'SELECT * FROM <YOUR TABLE> ') AS a; But you must create the indexes by your self. Or you using INSERT: INSERT ...


1

there are two thinks to configure for opening SqlServer to the wild: In configuration manager: And in SSMS: Sorry my server is in french...


1

The export part has been answered over at DBA: http://dba.stackexchange.com/questions/25755/taking-a-backup-of-a-single-table-in-the-sql-server How to export one single table on SQL server has been answered numerous times on Stackoverflow too: http://stackoverflow.com/questions/680552/table-level-backup ...


0

I logged off and back on and it seems to no longer throw the error.


2

The Microsoft link given above does not address the "Local server connection" server names in maintenance plans. These queries let you check the maintenance plan connection strings. All use the msdb database. (SQL 2008, also SQL 2005 if sysssispackages is changed to sysdtspackages90) SELECT x.*, LocalServerConnectionString = cm.n.value('declare ...


-1

Looks like it's impossible by default due to three-way handshake required by MS SQL https://support.microsoft.com/en-us/kb/287932 Other database server like PostgreSQL don't require this special handling and work well via HAProxy


0

To avoid this issue add your user ( the user who is taking backup) as a user of the Backup database, and your user should have (login) access in the new instance.


-2

SELECT d.name, percent_complete, session_id, start_time, status, command, estimated_completion_time, cpu_time, total_elapsed_time FROM sys.dm_exec_requests E left join sys.databases D on e.database_id = d.database_id WHERE command in ('DbccFilesCompact','DbccSpaceReclaim')


2

We often see shortened list of differences between Express and Standard. In my opinion, when you are to the point of considering this for a "production" environment deployment, you need to fully be aware of differences. Here's the full detailed list of differences between 2008R2 Standard and 2008R2 Express from msdn: Scalability and Performance Number of ...



Top 50 recent answers are included