Viewing 15 posts - 271 through 285 (of 1,584 total)
This should already be automatically logged to the SQL Server Error log. How are you executing this UPDATE statement? If you could, please post the update TSQL and...
March 24, 2014 at 12:24 pm
Best practices? It depends. Perhaps use a 3rd party software like centreon/nagios, or RedGate SQL Monitor, or Idera free admin tool (all would work).
For options 1 and 3 you...
March 24, 2014 at 12:18 pm
Alerts set up via the manager don't always set up correctly (at least in my experience) so I suggest scripting them out and ensuring you have the @shouldalert set to...
March 24, 2014 at 12:10 pm
Powershell?
What query are you attempting to run? And are you asking to restart a windows service on an external machine via TSQL?
March 24, 2014 at 8:57 am
Check that the firewall is enabled on the Windows 7 machine (by default it is). It may be blocking port 1433. Also please check the Event viewer logs and...
March 23, 2014 at 11:53 pm
Yes. If you use the queryout option and use union all to link a column list with the actual content.bcp "SELECT 'col1', 'col2', 'col3' U NION ALL SELECT col1,...
March 22, 2014 at 12:08 pm
FYI, in its simplest form
USE [DATABASE]
GO
DBCC SHRINKFILE (N'Database_log' , 0)
GO
March 21, 2014 at 5:20 pm
Please review this similar post, it will give you a script to accomplish what you want and outline some things to think about before you actually make a decision to...
March 21, 2014 at 5:13 pm
Correct. You can change the names of the database and files during the restore process
March 21, 2014 at 1:19 pm
In binary form or the actual character string of contents from within the text file?
March 21, 2014 at 12:52 pm
Installing a different instance shouldn't matter as it'd be SERVER\DEV and SERVER\QA
You could keep the same database names as well, and wouldn't need to change the database name during restores
March 21, 2014 at 12:51 pm
It is my understanding that your VLFS have gotten so high because of potential autogrowth in your transaction log(s) over time. Depending on the size of your database, 1000...
March 21, 2014 at 11:26 am
While I don't recommend or endorse this, you could add a job step that has a SELECT 1/0 in it (that never actually gets run, the prior step would report...
March 21, 2014 at 10:12 am
The only thing I can think of is to stop the job and update the status in msdb to reflect an error, but how that would actually work with the...
March 21, 2014 at 9:50 am
Great points! Also, if the query suddenly started performing poorly first you start with your execution plan, but you would also want to check to see if your statistics...
March 21, 2014 at 9:43 am
Viewing 15 posts - 271 through 285 (of 1,584 total)