Comments
Sort by recent activity
SQL Compare is for comparing schema objects, so that's what you want for comparing stored procedures. SQL Data Compare is for comparing data, ie the data in tables. If you're looking for resources for learning how to use Redgate Tools, https://www.red-gate.com/hub/university/ is a good place to start.
/ comments
SQL Compare is for comparing schema objects, so that's what you want for comparing stored procedures.SQL Data Compare is for comparing data, ie the data in tables.If you're looking for resources fo...
Hi, searching in indexes is not currently supported I'm afraid. / comments
Hi, searching in indexes is not currently supported I'm afraid.
Hi - what are you comparing to get that diff? Scripts folder to database? / comments
Hi - what are you comparing to get that diff? Scripts folder to database?
Hi - do you have permissions enabled in SQL Clone? / comments
Hi - do you have permissions enabled in SQL Clone?
Yes, installing a SQL Clone Agent on the same machine as the SQL Clone Server is a normal an supported configuration. / comments
Yes, installing a SQL Clone Agent on the same machine as the SQL Clone Server is a normal an supported configuration.
Hi, when image scripts are running, the image database is attached with a temporary name, starting with SqlCloneTemp_. SQL Clone can't attach as the name of the image, because that database might already exist. You'll need to use DB_NAME() to get the temporary database name. Here's a script that sets the recovery mode to simple, that I've tested in SQL Clone: declare @dbname sysname = DB_NAME();<br>declare @sql nvarchar(180) = 'ALTER DATABASE [' + @dbname + '] SET RECOVERY SIMPLE;';<br>exec sp_executesql @sql;(The temporary database name chosen by SQL Clone is always alphanumeric, so won't require escaping.) / comments
Hi, when image scripts are running, the image database is attached with a temporary name, starting with SqlCloneTemp_. SQL Clone can't attach as the name of the image, because that database might a...
Ah - if you're trying to remove all the users, you'll need to exclude the SQL Clone temporary user. That user will be removed by SQL Clone at the end of the script, and won't be present in the image, so you don't need to remove it yourself. The script can't remove that user because the script is running as that user, and you can't remove the user you're running as. / comments
Ah - if you're trying to remove all the users, you'll need to exclude the SQL Clone temporary user. That user will be removed by SQL Clone at the end of the script, and won't be present in the imag...
What's the result of the script when it's run from SSMS? Are you able to share the script?
/ comments
What's the result of the script when it's run from SSMS?Are you able to share the script?
Most of the disk access to the clones will hit the image file. If the image is stored on the network, then the network connection might be the limiting factor. As for RAM - from SQL Server's point of view, clone databases are just normal databases, so you'll need as much RAM as you would need if in that case.
/ comments
Most of the disk access to the clones will hit the image file. If the image is stored on the network, then the network connection might be the limiting factor.As for RAM - from SQL Server's point o...
Hmm, unfortunately those stack traces don't actually say what the agent was trying to do when it failed [image] Is that the entire log file? / comments
Hmm, unfortunately those stack traces don't actually say what the agent was trying to do when it failed Is that the entire log file?