Comments
Sort by recent activity
Ben,
Glad my post helped some. I agree with David that you should go the Git model as that is what almost all development shops are using now and TFS has a Git mode that most TFS shops are moving to.
I would recommend playing with the combination of SQL Source Control and Database Projects. It isn't perfect, but it can work. Here's the latest documentation on using the 2 together. I have played with it on the side, but haven't used it as my process yet. / comments
Ben,
Glad my post helped some. I agree with David that you should go the Git model as that is what almost all development shops are using now and TFS has a Git mode that most TFS shops are moving ...
Ben,
The only thing I don't think is pretty normal for working with SSDT Database Projects is the not putting in Source Control right away. I do work in a disconnected model similar to how you describe. My process currently using SSDT is to:
Create Database Project and develop initial objects in SSDT
Publish to a development (usually local) SQL Server
Make changes & unit test on the development server
Push changes to Database Project from Dev server
Publish from Database Project to QA
Promotion of code is always from the database project, so no new changes should be made anywhere but development.
It isn't ideal and I do like the integration of SQL Source Control into SSMS. You can use both SSDT database projects and SQL Source Control, but there are some things that aren't supported when you do both.
The reason I use Database Projects in SSDT instead of SQL Source Control is because in a database project the database settings are also part of the project and under source control, while SQL Source Control only includes the schema and things like SET options and collation definitely affect the way you have to code.
-Jack / comments
Ben,
The only thing I don't think is pretty normal for working with SSDT Database Projects is the not putting in Source Control right away. I do work in a disconnected model similar to how you des...
I won't be attending this year because training dollars have gone to attending SQLSkills training in October. / comments
I won't be attending this year because training dollars have gone to attending SQLSkills training in October.
David Atkinson wrote:
What would you say a sensible limit was? We'd rather avoid adding options if at all possible.
David Atkinson
Red Gate Software
Actually 150 is probably a good choice for display. Could paging be implemented? Even a a message saying 150 of N displayed would be better because there is nothing in the application that tells you that there are more than what is being displayed.
In my case I was searching for references to a second database because there are those who want to move those functions into the current database. Most procedures and functions have references to this database so I wanted to get a number and generate a list. I can do it using T-SQL, but SQL Search could have been perfect, if it returned all the rows (at least a count) and if I had a way to export to csv or excel. So I'd suggest keeping the display limit to 150 and adding a total found count and a way to export all results. / comments
David Atkinson wrote:
What would you say a sensible limit was? We'd rather avoid adding options if at all possible.
David Atkinson
Red Gate Software
Actually 150 is probably a good choice for ...
I just ran up against this limit as well and was going to start a thread about it.
I'd love to see this be configurable as I have a database with over 1000 sp's and I'm trying to identify a call to another database within the sp's and I hit the 150 limit. / comments
I just ran up against this limit as well and was going to start a thread about it.
I'd love to see this be configurable as I have a database with over 1000 sp's and I'm trying to identify a call to...
I am having the same problem when I start a job and then close the job progress window. I have also sent at least one error report in.
Microsoft SQL Server Management Studio 10.0.4000.0
Microsoft Analysis Services Client Tools 10.0.4000.0
Microsoft Data Access Components (MDAC) 6.1.7600.16385
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 8.0.7600.16385
Microsoft .NET Framework 2.0.50727.4952
Operating System 6.1.7600 / comments
I am having the same problem when I start a job and then close the job progress window. I have also sent at least one error report in.
Microsoft SQL Server Management Studio 10.0.4000.0
Micro...
I'm experiencing similar slowness problems with SQLPrompt 5. For me it appears to happen when I have a long SQL script open, particularly with CTE's and or temp tables in the script. It also happens in Visual Studio 10.
Here are some errors in the SQLPrompt log from today:
29 Dec 2010 20:53:31,489 [1] INFO RedGate.SqlPrompt.Engine.LogService - Starting new SQL Prompt editor session
29 Dec 2010 20:58:00,290 [9] ERROR RedGate.SqlPrompt.Engine.LogService - LogService caught unhandled exception in AppDomain: 'Thread was being aborted.'
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
at System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
at RedGate.SQLPrompt.CommonUI.Controls.SpinnyThing.SpinnyWidget.?
/ comments
I'm experiencing similar slowness problems with SQLPrompt 5. For me it appears to happen when I have a long SQL script open, particularly with CTE's and or temp tables in the script. It also happ...
Brian,
I will still send the error logs, but knowing where to look helped me solve the problem. I had chosen in the beginning to encrypt the connection to the SQL Server and it worked at the beginning, but changing the credentials apparently caused this to fail as I know get a certificate chaining error. By not encrypting the connection I SQL Response now connects properly. / comments
Brian,
I will still send the error logs, but knowing where to look helped me solve the problem. I had chosen in the beginning to encrypt the connection to the SQL Server and it worked at the begin...
Yes, I restarted the alert repository service and I rebooted the PC (my workstation) that it is installed on. / comments
Yes, I restarted the alert repository service and I rebooted the PC (my workstation) that it is installed on.
Indications are that when I click Test Credentials I still get the Incorrect User Name or Password error and I am regularly getting SQL Server Unreachable Alerts when I know the SQL Server IS reachable. I am also not receiving alerts when I know I should be receiving them. For example I specifically set up a job that will fail and I am not getting the job failed alert.
Lastly, I ran a profiler trace for 2 days and never saw any activity from SQLResponse on the SQL Server and I assume I should have seen something as it checks for problems. It is possible I was missing an evnet, but unlikely I think.
I know the account has sysadmin access because I originally set up SQLResponse using this account and it worked fine. The problem started when I tried experimenting with a SQL Server login to see if I could make SQL Response work with a non-SA login and then changed back. / comments
Indications are that when I click Test Credentials I still get the Incorrect User Name or Password error and I am regularly getting SQL Server Unreachable Alerts when I know the SQL Server IS reach...