Comments
Sort by recent activity
Steve -
So the next question, how do I install it on SSMS 2005?
Just grab a toolbelt download and install SQL Prompt? / comments
Steve -
So the next question, how do I install it on SSMS 2005?
Just grab a toolbelt download and install SQL Prompt?
I'm also in a pickle here.
I have SQL Server 2005 EE servers and SQL Server 2008 EE servers.
I installed SQL client for 2008 on my PC and installed SQL Prompt on it.
However, that client gets snarky about opening up the properties on Jobs running on SQL Server 2005 servers.
I got tired of having to deal with it an so I re-installed the SQL Client for 2005.
So, in short, I have both SSMS 2008 and SSMS 2005 running on my PC.
SQL Prompt is still on my toolbar for the SSMS 2008, but not on SSMS 2005.
I have the SQL Prompt license as part of the toolbelt.
So I'm wondering, is this license sufficient to cover both instances of SSMS on my PC. Seems like it should be, but I'm asking because I don't see a way to install it into SSMS 2005.
Thanks in advance for any information you can provide.
Randy Volters / comments
I'm also in a pickle here.
I have SQL Server 2005 EE servers and SQL Server 2008 EE servers.
I installed SQL client for 2008 on my PC and installed SQL Prompt on it.
However, that client gets snark...
Ok, I figured it out. NO ISSUE WITH SQL COMPARE; issue is with the dummy that created a table that was identical to the table that SQL COMPARE had problems with... namely me.
:oops: / comments
Ok, I figured it out. NO ISSUE WITH SQL COMPARE; issue is with the dummy that created a table that was identical to the table that SQL COMPARE had problems with... namely me.
:oops:
Here is the offending part of the statement...
I dropped the table, then when I try to create it again, I get the same error as reported at the top of the thread.
It is coming from the constraint on the [emp-id] column, but if the table was dropped, how could the object DF_jc-time-sh_emp-id_20080818125445337 still exist? More importantly, how can I drop it?
CREATE TABLE [dbo].[jc-time-sh]
(
[emp-id] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL CONSTRAINT [DF_jc-time-sh_emp-id_20080818125445337] DEFAULT (''), / comments
Here is the offending part of the statement...
I dropped the table, then when I try to create it again, I get the same error as reported at the top of the thread.
It is coming from the constraint o...
OK, I'm stumped, not in contraint column usage either. / comments
OK, I'm stumped, not in contraint column usage either.
I was looking at table constraints for a column constraint; sorry / comments
I was looking at table constraints for a column constraint; sorry
typed it in again and this time it took. Weird. / comments
typed it in again and this time it took. Weird.
Chris -
Thanks; yes I agree with your points. Since I was just getting the users a sandbox to test in, I wasn't concerned with 'open' transactions; but after talking with the testers these are precisely the transactions I should have been concerned about.
So I assume I should fetch the last full backup, which I write nightly after close of business, then say yes to backing up the tail. But then what?
I think (but would like you to confirm) that I restore the full database, but leave it non-operational, then after that is done I restore the tail tran log and make it operational? Would that be correct? / comments
Chris -
Thanks; yes I agree with your points. Since I was just getting the users a sandbox to test in, I wasn't concerned with 'open' transactions; but after talking with the testers these are pre...
I think I figured out what step I forgot.
I'll post back here if I run into the problem again.
(backup the tran log first, then run the full backup, then restore from the full backup) / comments
I think I figured out what step I forgot.
I'll post back here if I run into the problem again.
(backup the tran log first, then run the full backup, then restore from the full backup)
downloading now; thanks for the tip. [image] / comments
downloading now; thanks for the tip.