Viewing 15 posts - 17,266 through 17,280 (of 22,214 total)
Have you updated the statistics recently and if so, have you tried updating with a full scan? There is a bit of a discrepancy between the estimated rows & the...
June 9, 2009 at 6:13 am
If you use the result set to show success, just prepare your code handle multiple result sets because you'll need one for the success criteria and one for the data...
June 9, 2009 at 5:34 am
Just so the next person along can understand, can you post the solution?
June 8, 2009 at 12:55 pm
May as well pile on. This absolutely should have been CHAR(1) or NCHAR(1). VARCHAR or NVARCHAR were the worst choice under any fair interpretation of the definition. The answer stated...
June 8, 2009 at 12:28 pm
Yeah, I should have mentioned that. For anything beyond a single row insert, that's the way to go.
June 8, 2009 at 12:17 pm
The correct syntax is:
ALTER DATABASE xxxx SET PARAMETERIZATION FORCED
You were just missing the SET statement.
You should still see an execution plan, regardless of whether or not it's got forced parameterization....
June 8, 2009 at 12:16 pm
Check out the forced parameterization topic in the Books Online (SQL Server's documentation). It lists all the various times that you can't use forced parameterization such as:
INSERT ... EXECUTE queries
Statements...
June 8, 2009 at 8:25 am
If you create a view with schemabinding then the base tables can't be modified in a way that would break the view. However, if the view doesn't exist and you're...
June 8, 2009 at 8:20 am
SCOPE_IDENTITY is not going to be affected negatively or positively by being called within a transaction. I would recommend the transaction though, just because it's a better way to manage...
June 8, 2009 at 7:55 am
And run consistency checks before you backup the database so that in the future you'll know that the backup was taken from a well structured db.
June 8, 2009 at 7:48 am
I'm just a bit confused by the situation. Did you have the database in full recovery but you were NOT running log backups? That could explain the excessive size of...
June 8, 2009 at 7:47 am
3 copies of the db on the same server just doesn't make any sense. If they're worried about corruption or loss, then all three on the server are exposed the...
June 8, 2009 at 7:40 am
If it can't access the folder, it's because of security. SQL Server runs under a different context than when you connect to it. Just because you can access the share...
June 8, 2009 at 7:37 am
What about using Performance Monitor to capture user connections all day long? It's the very best way I know to do this.
June 8, 2009 at 7:34 am
Good article.
You could have carried it a bit further. Including RESTORE VERIFYONLY as a part and parcel of your backup routines adds to the overall confidence you have in your...
June 8, 2009 at 5:36 am
Viewing 15 posts - 17,266 through 17,280 (of 22,214 total)