Viewing 15 posts - 3,496 through 3,510 (of 7,187 total)
Don't do this. It just wastes resources and causes fragmentation. If your log files are getting large, then back up your transaction log more frequently. Bear in...
June 24, 2014 at 4:37 am
What you're seeing is a cardinality error, and it's why you should be careful when using the UPDATE...FROM syntax. It occurs when the value you're updating in table a...
June 23, 2014 at 4:24 am
thomashohner (6/18/2014)
Can you point me to any info about configuring the transaction log? Filling the HD sounds bad:crazy:
Search for "managing transaction logs". There's loads of stuff out there.
To add...
June 18, 2014 at 9:36 am
BWFC (6/18/2014)
June 18, 2014 at 6:12 am
Ed Wagner (6/18/2014)
On site means on site, not Azure - plain and simple.
Precisely. All on-site databases are 2012, meaning 2000 can't be the answer. And since an Azure...
June 18, 2014 at 6:03 am
Well, the best way to find out is to try it!
John
June 17, 2014 at 4:41 am
IF NOT EXISTS (
SELECT * FROM INFORMATION_SCHEMA.COLUMNS
WHERE COLUMN_NAME = 'USA_RFORIGEM '
AND TABLE_NAME = 'CONFIGURACAO'
)
ALTER...
June 17, 2014 at 4:32 am
Sean Lange (6/16/2014)
June 16, 2014 at 9:39 am
Sean Lange (6/16/2014)
As much as that really sucked it did finally force Blatter to admit that something needs to change.
Yes, he has had some pretty barmy ideas in the past,...
June 16, 2014 at 9:06 am
You can set up your own auditing on your database, for example using triggers to write to audit tables whenever any changes are made to data in any tables. ...
June 16, 2014 at 4:35 am
If you don't have any auditing set up then you're not going to be able to find out much. For DDL changes, you can try the default trace.
If you...
June 16, 2014 at 3:41 am
Probably not - it's not something that SQL Server controls. You'd be better off speaking to your AD administrator.
John
June 16, 2014 at 2:50 am
Then you'll need to explain your requirement better, please. Perhaps you could post some sample data and expected results based on that data?
Thanks
John
June 12, 2014 at 9:31 am
If all you're trying to do is return the whole result set in pages of @PageSize rows, just remove the PARTITION BY clause from your ROW_NUMBER function.
John
June 12, 2014 at 8:52 am
Viewing 15 posts - 3,496 through 3,510 (of 7,187 total)