I don't if this is just my installation but...

I've just moved my workstation to Win 7 Ent (x86) and installed SQL 2000
Dev + SP4. Whenever I attempt to create a new table via Enterprise
Manager I get an error with the MMC snap-in message. The event viewer
shows the following:


Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp:
0x4a5bc3f1
Faulting module name: msdt70.dll, version: 7.10.5087.0, time stamp:
0x42488cbe
Exception code: 0xc0000005
Fault offset: 0x0022cbaa
Faulting process id: 0xd80
Faulting application start time: 0x01ca2c7c5b9c25c8
Faulting application path: C:\Windows\System32\mmc.exe
Faulting module path: C:\Program Files\Common Files\Microsoft
Shared\MSDesigners98\msdt70.dll
Report Id: b1d161b8-986f-11de-83b9-001d923730dc

I couldn't get any help on this from the MS problem reporter. Has anyone
had the same issue as me? (I've tried removing and reinstalling SQL to no
joy)

TIA
Andy P

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

For what it's worth, it's not working for me either, though I'm getting
different errors.
I was able to create tables using SQL Server 2008 Management Studio.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"Andy P" <dev (AT) null (DOT) com> wrote

For what it's worth, it's not working for me either, though I'm getting
different errors.
I was able to create tables using SQL Server 2008 Management Studio.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"Andy P" <dev (AT) null (DOT) com> wrote

Andy P (dev (AT) null (DOT) com) writes:
SQL 2000 is not supported on Vista, so I guess it's not supported
on Windows 7.

Then again, if the Table Designer dies, I consider that a good thing.
That is a total piece of crap. (And it exactly the same piece of crap
in SSMS 2005/2008.)


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erland,

I had asked about the SQL2005 SP2 Client tools on Windows 7 so can I assume
the Table Designer for SQL2005 SP2 might die on Windows 7?

Thanks

Chris

"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

Thanks for the replies guys. At least I know its not me.

I've used SQL 2005 + 2008 and both work fine. Thing is, I actually quite
like Enterprise Manager (and we're still running SQL 2000 as our main
DB). I just like the way you can run a query then copy and paste straight
into Excel (including columns headings...!) rather than having to export
it first. If you're having to play around with data you can't beat it.
Pity they didn't keep that in the later versions.

Use 2008 Management Studio. Run a query in grid mode. Click the top left
corner so the entire grid is selected, right-click the top left left corner,
and choose "Copy with Headers"... Then paste into Excel. Voila! Kiss your
10-year old tool goodbye.


On 9/4/09 8:45 AM, in article op.uzqgd0i2p7u9xv (AT) unusable2 (DOT) freecom.local,
"Andy P" <dev (AT) null (DOT) com> wrote:

Cheers for the advice, I'd never spotted that.

But I'm still not kissing anyone's tool :-D

On Fri, 04 Sep 2009 16:08:35 +0100, Aaron Bertrand
<moc.liamg (AT) dnartreb (DOT) noraa> wrote:

Aaron,

If we cannot use SQL2008 Client tools on Windows 7 what other functions
might fail because we are still on SQL2005 SP2?

Thanks

Chris

"Aaron Bertrand" <moc.liamg (AT) dnartreb (DOT) noraa> wrote

Why cant you use 2008 client tools on Windows 7?
Why can't you apply SP3 to your 2005 client tools on Windows 7?

I don't know of all the functions that will fail if you insist on staying at
SP2. I just simply wouldn't do it. There were plenty of fixes to
maintenance plans after SP2, for example. So if you use those, you are
using them at your own risk. Obviously you don't get any of the feature
enhancements in 2008; I don't think there were any feature changes between
SP2 and the current builds of the 2005 version.

If you want a full category of "things that might go wrong if I decide to do
it this way" you will probably have to comb the individual fixes in post-SP2
CUs, SP3, and post-SP3 Cus to find the ones that affect the tools, and deem
if they affect you. I don't keep such a list off the top of my head because
I see no reason to stay on an antiquated version of the client tools...