Viewing 13 posts - 1 through 13 (of 13 total)
I have a suspicion that the same behavior would have been seen in SQL2016, but no proof and no reason to personally research it at the moment. BTW...we are considering...
September 24, 2019 at 1:34 pm
At this point, nearly 2 weeks after upgrading from SQL-2014 to SQL-2017, and subsequently 5 days after enabling trace flag 692, I believe I can say that the trace flag...
September 23, 2019 at 5:03 pm
Not heaps. They do have clustered indexes as primary keys.
Most are BULK inserted to.
Rebuilding the indexes does help to recapture the space, but it only starts building again, which was...
September 19, 2019 at 7:20 pm
It is entirely consistent, at least from my development machine. I have not yet tested it from our "production" web server environment (but the SQLs are the production servers).
Jim
April 30, 2011 at 12:01 pm
Good question.
I am using the manual mirror failover command (button) from the SSMS user interface.
The partner database is available immediately (or, at least, as quickly as I can do something...
April 30, 2011 at 11:23 am
First, I now noticed the "High Availability" forum...how can I get this thread moved over there?
Next...doing some more research...
Had a thought that this was perhaps being caused by connection pooling....
April 30, 2011 at 9:36 am
Wanted to follow up here...looks like you were correct in saying that it was not a deadlock (no surprise there. 🙂 )
We believe that a stored procedure is somehow...
December 13, 2010 at 2:45 am
The only thing that I can say is that I've seen it last for as much as 2 hours in the past - we typically don't tend to let it...
December 7, 2010 at 5:16 am
A PC upgrade would be great! I tend to over-extend the life of my home PC, so having a new PC, even every other year, would be a great...
April 16, 2010 at 2:44 am
I can easily answer that question. Since I have absolutely NO IDEA how I would deploy this using a script, the only way we have ever deployed was via...
October 23, 2009 at 1:02 pm
I stand corrected. I just tried this query, as written, on both SQLServer 2000 and 2005 and the table DOES get created, even in spite of the extra comma.
Jim
July 17, 2009 at 6:07 am
Actually, won't the comma after the lname column cause a syntax error? So, of those answers, "no rows will be inserted" is technically the most correct answer.
Jim
July 17, 2009 at 3:36 am
Thanks for the syntax on those statements. If I built stored procedures for each of those statements, would I put them in MSDB?
What permissions/role would a user have to...
January 24, 2009 at 12:54 pm
Viewing 13 posts - 1 through 13 (of 13 total)