Viewing 15 posts - 1,471 through 1,485 (of 6,035 total)
S Hodkinson - Saturday, May 13, 2017 1:37 AMGosh this seems terribly relevant after yesterday's attack
Indeed.
How One Simple Trick Just Put Out...
May 15, 2017 at 8:07 am
Policies can destroy creative thought if applied too mechanically. In a complex system, such as a database, best-practices so often blur into 'it depends'.
What set of policies are...
May 15, 2017 at 7:50 am
May 12, 2017 at 11:43 am
It's a lot easier to automate a process when it's been well defined (ie: the functional requirements don't change) and when the underlying physical environment is stable (ie: you don't...
May 11, 2017 at 6:37 am
May 11, 2017 at 6:11 am
You're posting in a SQL Server 2008 forum. A lot has changed in the area of availability, replication, and disaster recovery features between versions 2012-2014-2016. Confirm that you're production environment...
May 10, 2017 at 7:46 am
As the DBA, about the only influence you have this situation (poorly constructed SQL coming from an application) is to insure that both [some_table].[some_id] and [some_other_table].[some_other_id] are indexed. If investigation...
May 10, 2017 at 7:11 am
May 9, 2017 at 11:51 am
May 9, 2017 at 9:14 am
SELECT * FROM OPENROWSET(
‘Microsoft.ACE.OLEDB.12.0’
,‘Excel 12.0;Database=C:\Temp\OrderValues.xlsx;HDR=YES’,results)
May 9, 2017 at 8:46 am
May 9, 2017 at 8:41 am
To understand the purpose of TEMPDB, why it can occasionally increase dramatically in size, it help to know what objects are allocated in TEMPDB during peak periods of growth. For...
May 9, 2017 at 8:39 am
May 8, 2017 at 12:48 pm
The ubiquitous presence of devices is a blessing in many ways, but one consequence is that we generally spend less time deep thinking. I mean, twenty years ago those occasions...
May 8, 2017 at 6:36 am
I second the motion to use UPDATE with OUTPUT clause and thus avoid multiple statements and explicit batch transaction.
May 8, 2017 at 6:17 am
Viewing 15 posts - 1,471 through 1,485 (of 6,035 total)