Viewing 8 posts - 16 through 24 (of 24 total)
the easiest method is to use...
"select...from sys.master_files mf cross apply sys.dm_os_volume_stats (mf.database_id, mf_file_id) vs"
then CREATE a read-only DUMMY DATABASE that has data files across all drives....
February 15, 2019 at 11:47 am
I had the same problem. I ran an index defrag process but the transaction log became full and the defrag process errored out. The transaction log remained large.
May 18, 2018 at 10:17 am
Yup deleting and adding again to the dimension usage tab solved my issue. I'm now able to save and process everything.
So a little background. I have a date...
February 2, 2018 at 11:09 am
I encountered the same issue with a report subscription where the developer created a separate dataset for each report parameter. There were close to 2 dozen parameters.
Creating or...
February 1, 2018 at 10:12 am
I actually found an easy solution to this fix since I had the same issue.
I was trying to remove the filegroup [fg_LMeterDetail_13] but got the "cannot be removed because it...
January 21, 2016 at 11:15 am
simple fix exec [database name].[object owner].[stored procedure name]
you must reference the database name in either the connection string or command text. Otherwise SQL will use the default database which...
June 17, 2015 at 2:40 pm
Yes, that error occurs when your database collation is set to case sensitive.
Msg 208, Level 16, State 1, Line 1
Invalid object name 'SYS.DM_DB_INDEX_USAGE_STATS'.
To resolve, just CTRL+SHIFT+L to convert the text...
February 25, 2015 at 1:28 pm
Thank you all. I really appreciate your feedback and will work with your suggestions.
May 11, 2009 at 3:00 pm
Viewing 8 posts - 16 through 24 (of 24 total)