Tag Info

New answers tagged

0

We have a similar situation and we had to create a larger script to resolve deletion in a proper manner. Note: Another issue you will run into with large delete operations (one or many transactions), is that your transaction logs will grow really fast during the runtime of the delete. So, be prepared for that in terms of disc space. It may be required ...


0

After further investigation, I found the answer. I ran Exec sp_delete_log_shipping_primary_secondary @Primary_database = N'DATABASE_NAME' ,@secondary_server = N'SECONDARY_SERVER_NAME' ,@secondary_database = N'SECONDARY_DATABASE_NAME' To delete all reference to that server. followed by EXEC sp_delete_log_shipping_primary_database @database = ...


1

If something is still setup on the secondary server you need to run sp_delete_log_shipping_secondary_database there. You can clear the log shipping configuration on the primary by executing sp_delete_log_shipping_primary_secondary USE master; GO EXEC master.dbo.sp_delete_log_shipping_primary_secondary @primary_database = N'<PrimaryDatabase>' ...


0

A view and individual SQL logins would be appropriate if each patient accessed the database directly using an ad-hoc query tool, like Access. However, in the case of a front-end application, I suggest performing patient authentication in the app code (perhaps with individual user credentials stored securely in a database) and then just use the patient ...


1

You need to know who the user is and that information needs to be accessible through the view. CREATE VIEW dbo.tPatientForUser AS SELECT patient_id, name, address, gender, loginame FROM tPatient WHERE loginame = SUSER_SNAME(); Or, depending on your application you might need: WHERE loginame = ORIGINAL_LOGIN(); This can help you filter the rows to ...


1

The destination path for the LSCopy job has to be an UNC Path for all practical purposes, to make things simpler to debug I would reccomend not to use the default \d$ shares as you will have to change the permissions on them but connecting to \localhost\c$ is a network connection. Now the error ***Error: Not enough server storage is available to process ...


-2

I also had the same problem and here is how I fixed it: Don’t enable Hyper-V Dynamic Memory for your virtual machine but set it static with a value of e.g. 8GB RAM


2

If you want to be sure that you're backups are going to tape, you need to periodically recall the tapes and restore the backups. We recall tapes once every three months to do this, it seems like a lot of effort but it is not overkill if you value having offsite backups.


3

You are running SQL Server build 9.00.5294.00 that is more current than SP4 which is 9.00.5000. Your server has already been updated. (http://sqlserverbuilds.blogspot.com/) (Build 7601: Service Pack 1) is the version of the operating system.


9

when I try to use Management Studio to attach to the .mdf file There's not really a gentle way to say this: Stop doing that. The GUI is full of bugs and bad defaults; more importantly, unless you take a screencast, we have no way to identify exactly what steps you're taking as you point and click your way through the GUI. Log in as a system ...



Top 50 recent answers are included