How can we help you today? How can we help you today?
TonyStrileckis
Activity overview Badges (0) Posts (0) Comments (4)

Activity overview

Latest activity by TonyStrileckis

Alex,  Thanks for getting back to me.  Yes, this is still an issue.  I have SQL Source Control version 7.0.50.9962, having just updated to this version last week. I don't see where there is anything different with this DB as to the others on this same server. Is there anything in the SQL Source Control logs that I should be looking for?  Or that I can send you?   Thanks,  Tony / comments
  1. Community
  2. SQL Source Control
  3. SSMS crashes when checking for changes in Source Control 7.0
Alex, Thanks for getting back to me.  Yes, this is still an issue.  I have SQL Source Control version 7.0.50.9962, having just updated to this version last week.I don't see where there is anything ...
0 votes
Alex,  While checking on the number of database objects, I noticed that this database has a user-defined table type that is used in a function.  Don't know if they exist in any of our other databases.  Would that cause any problems when checking in changes?  And if so, how do I work around that? Thanks,  Tony / comments
  1. Community
  2. SQL Source Control
  3. SSMS crashes when checking for changes in Source Control 7.0
Alex, While checking on the number of database objects, I noticed that this database has a user-defined table type that is used in a function.  Don't know if they exist in any of our other database...
0 votes
Alex,  I am using SSMS ver 17.9 on Windows Server 2012 R2.  SQL Server is installed, but not running on the server where I'm running Redgate SQL Source Control.   This database has: 311 CHECK constraints, 23 Default constraints 3 FOREIGN KEY constraints 550 PRIMARY KEY or UNIQUE constraints 25 Scalar functions 5102 Stored procedures 67 System tables 7 Table functions 35 Triggers 559 User tables 20 Views For a total of 6702 objects.  And this database is running on SQL Server 2012 SP3. Unfortunately, I cannot share this database. Thank you,  Tony / comments
  1. Community
  2. SQL Source Control
  3. SSMS crashes when checking for changes in Source Control 7.0
Alex, I am using SSMS ver 17.9 on Windows Server 2012 R2.  SQL Server is installed, but not running on the server where I'm running Redgate SQL Source Control.  This database has: 311 CHECK constra...
0 votes
Alex, Thanks for your response. I checked the link you provided and here are the answers to the steps on that page: I am already on SSMS 17.9  I'm not linking any static data tables.  I have already tried unlinking and re-linking (twice)  And the "Decrypt encrypted objects" option is already unchecked  Last option was that I unchecked the two options of "Indicate changed objects...every x seconds" and "Check for changes to static data", and then restarted SSMS. After restarting SSMS, I tried again with that database, but it still crashes.  I tried setting the logging option to "All", and a lot gets written to the logs, but nothing gets written to the logs after I select the server and database to check.  I tried setting the logging option to "Debug", but again it doesn't capture anything relating to the crash. Here's what gets written to the logs after setting the logging option to "Debug" (or to "All"), but it gets written as soon as I open SSMS, before I have selected a server or database to check in (and the same gets written to Event Viewer):  System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host Nothing else gets written to the logs after SSMS times out. And Event Viewer just has the SSMS crash message. Faulting application name: Ssms.exe, version: 2017.140.17285.0, time stamp: 0x5b7c378f Faulting module name: clr.dll, version: 4.7.3062.0, time stamp: 0x5ab95217 Exception code: 0xc00000fd Fault offset: 0x00157b77 Faulting process id: 0x37ac Faulting application start time: 0x01d574992055fb96 Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: e6c70cf5-e08d-11e9-80d4-005056b43df2 Faulting package full name: Faulting package-relative application ID: Thank you,  Tony / comments
  1. Community
  2. SQL Source Control
  3. SSMS crashes when checking for changes in Source Control 7.0
Alex, Thanks for your response. I checked the link you provided and here are the answers to the steps on that page: I am already on SSMS 17.9  I'm not linking any static data tables.  I have alrea...
0 votes
Total activity
5
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1