Comments
Sort by recent activity
Your constraint is actually a column constraint. If you want it to be a table constraint you need to precede it with a comma. See the BNF in BOL for Create Table.
I know that it seems a unique constraint could only be a Table level constraint but the syntax clearly allows it to be defined as either a table or column constraint.
And just to add to confusion both forms create a table level constraint object [image] .
I imagine that SQL Prompt just treats your format is as part of the column definintion. Try it by adding a perceding comma and see how the format changes.
HTH / comments
Your constraint is actually a column constraint. If you want it to be a table constraint you need to precede it with a comma. See the BNF in BOL for Create Table.
I know that it seems a unique co...
But I like the feature [image] / comments
But I like the feature
I noticed that there are some deadlocks that spill out of the window and I can't scroll to parts. I have an "e_waitPipeNewRow" deadlock with 6 threads. The upper two process blocks are off the top of the screen. If I zoom out I can see they are there but I can read the Geeked Text. When I zoom in I can't pan up to them. [image] . / comments
I noticed that there are some deadlocks that spill out of the window and I can't scroll to parts. I have an "e_waitPipeNewRow" deadlock with 6 threads. The upper two process blocks are off the to...
I have two issues related to this topic.
First, when I use SSMS 2008R2 to connect to the Compact Edition database I am prompted for a password. I have tried my Backup Agent account password, the SQL Engine Account password, and the SQL Agent password with no luck.
What is the password for this file and where/when/how is it set?
Second, when I tried to connect with SSMS 2014/2016 I don't see a entry for Compact Edition in the Connect dialog. Is this really true?
Thanks, / comments
I have two issues related to this topic.
First, when I use SSMS 2008R2 to connect to the Compact Edition database I am prompted for a password. I have tried my Backup Agent account password, the S...
I appreciate the difference between Announcement and Topic. However, the release announcements still take up a lot of real estate. Do you really need announcements for >10 prior releases? / comments
I appreciate the difference between Announcement and Topic. However, the release announcements still take up a lot of real estate. Do you really need announcements for >10 prior releases?
Thanks / comments
Thanks
Well Duh!%#. :oops:
All I had to do was read one or two sentences farther in the documentation and I would have answered my own question (plus saved a lot of time [image] )
Thanks for the assistance. / comments
Well Duh!%#. :oops:
All I had to do was read one or two sentences farther in the documentation and I would have answered my own question (plus saved a lot of time )
Thanks for the assistance.
The errors indicate memory buffer contention for the two pages. For some reason a process has been holding the two page buffers for an extended time (e.g. > 300 seconds). A long running transaction or hung process are examples.
This article "Posts Tagged ‘A time-out occurred while waiting for buffer latch’"http://mssqlwiki.com/tag/a-time-out-occurred-while-waiting-for-buffer-latch/ is pretty detailed but has a good description of the problem and has some tips for tracing it.
Generally, you will find that there is some bottleneck that is not "obvious" until you see it. In my case the backup was trying to write 200+GB from a file group while the application(s) were inserting/updating data at a high rate. The disk just could not keep up with the I/O so memory buffers were filled with pages waiting to be written.
HTH. / comments
The errors indicate memory buffer contention for the two pages. For some reason a process has been holding the two page buffers for an extended time (e.g. > 300 seconds). A long running transaction...
I would also like to have the backup and copy in two steps.
I have a number of production jobs that I have to disable prior to starting the Full Backup. I have to do this because the disk I/O contention on the data drives was significantly slowing both production processing and backup throughput. The Full Backup was taking > 24 hours. With Jobs disabled it now takes 3 - 4 hours.
As soon as the Full Backup is completed the Production Jobs can be restarted.
The file copy to off-storage can then run without impact.
Currently I have separate Backup job steps to
Disable Selected Production Jobs
Run Backup
Enable Selected Production Jobs
Copy Backups to File Server (Power Shell) / comments
I would also like to have the backup and copy in two steps.
I have a number of production jobs that I have to disable prior to starting the Full Backup. I have to do this because the disk I/O cont...
This same issue is what prompted me to start depending on scripts and the extended stored procedure to refresh QA, Dev, and Staging environments.
It is a real pain when the GUI changes even the physical file names. / comments
This same issue is what prompted me to start depending on scripts and the extended stored procedure to refresh QA, Dev, and Staging environments.
It is a real pain when the GUI changes even the phy...