Viewing 15 posts - 1 through 15 (of 81 total)
Hello --
Thank-you for your reply. It turns out one of the other administrators deleted the databases in question, and neglected to tell me. I have reconfigured the...
February 1, 2019 at 7:50 am
Hello --
I double-checked the database that was the target for the integrity check, and it is the one that is the subject of this discussion.
June 12, 2017 at 6:37 am
Hello --
I created a plan via the Maintenance Wizard that would do an integrity check to the database in question. When I ran this particular check, it completed...
June 11, 2017 at 11:44 am
Hello --
When I went through the motions to restore the database I made sure to go to the Files page, and change the FileStream location to the new...
June 9, 2017 at 1:35 pm
My apologies for asking this: What log file should I reference to get the command syntax requested in your posting?
Thank-you.
June 9, 2017 at 12:50 pm
Hello --
The filestream was moved via the following steps:
1. The database was backed up, and subsequently deleted within the Studio utility.
2. The database was restored...
June 9, 2017 at 8:55 am
Hello --
Thank-you for your reply. The errors that I am seeing are the following:
Date and time: 2017-06-09 06:06:36
Command: DBCC CHECKDB ([RayStationPatientDB_502_Q1_2017]) WITH NO_INFOMSGS, ALL_ERRORMSGS,...
June 9, 2017 at 8:17 am
Hello --
It turns out the system in question had not been added to the appropriate Active Directory organizational unit prior to my logging onto it.
Once that was completed, the...
May 2, 2016 at 7:38 am
Hello --
That additional line did the trick!
This script will work well for us, and I just want to thank everyone for their help on this.
March 28, 2016 at 10:29 am
Hello --
Just so we're on the same page. The script in question is the following:
exec sp_MSForEachDB
'
USE ?;
if exists
(select table_name
from information_schema.tables
...
March 28, 2016 at 10:19 am
Hello --
I reran the script, and it did produce output. The only thing is, the names of the respective databases were not listed. Is the output based on the order...
March 28, 2016 at 9:23 am
Hello --
I inserted the syntax UNION ALL in the script, and the following errors appeared on-screen:
Msg 156, Level 15, State 1, Procedure FindPatient, Line 34
Incorrect syntax near the keyword 'UNION'.
Msg...
March 28, 2016 at 9:19 am
Hello --
Thank-you for your posting, I ran the script you posted, substituting the actual patient ID in the appropriate slot. However, the query produced the following error for
each of the...
March 25, 2016 at 12:09 pm
Hello --
I have the list of columns within the table that will be queried, and I can insert them into the script at the two TODO locations. Is this the...
March 25, 2016 at 6:33 am
Hello --
The databases in question are the following:
RayStationPatientDB_Breast_4014
RayStationPatientDB_CNS_4014
RayStationPatientDB_Emerson_4014
RayStationPatientDB_GI_4014
RayStationPatientDB_GU_4014
RayStationPatientDB_GYN_4014
RayStationPatientDB_HN_4014
RayStationPatientDB_Lymphoma_4014
RayStationPatientDB_NWH_4014
RayStationPatientDB_Other_4014
RayStationPatientDB_Pediatric_4014
RayStationPatientDB_Physics_Research_4014
RayStationPatientDB_Sarcoma_4014
RayStationPatientDB_Skullbase_4014
RayStationPatientDB_SRS_4014
RayStationPatientDB_Thoracic_4014
More than likely it will be a single query at a given time, and all the dbo.RS_Patient_6 tables are identical.
March 24, 2016 at 2:36 pm
Viewing 15 posts - 1 through 15 (of 81 total)