Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Sunday, March 25, 2012

can we automate the data mining models management?

Hi, all here,

I am having a question about automating data mining models managements. As we know in many businesses, patterns vary very frequently, therefore, the mining models created will need to be created again afterwards according to new rules appearing in the data. But can we make all these process automated like automatically assessing the mining model accuracy and automatically recreate the mining models based on predifined specifications? Would please any one here give me any idea about that?

Thanks a lot for any guidance and help for that.

With best regards,

You can set up integration services packages to reprocess/manage your models and schedule when they get run.|||Hi, Jamie, thank you very much.

Thursday, March 22, 2012

Can user view objects they only have select permission on?

I have a user that belongs to a role. This role only has select permissions
on 10 views. When I log in as this user via Management Studio I cannot see
the views however I can execute queries against them.
On another server that I did not setup, that I'm supposed to be mimicking
the same security, this same user can see the views.
Any ideas what the difference is?
Thanks!Here's the commands that I'm executing in order:
CREATE ROLE [Customers_ROLE] Authorization dbo
CREATE SCHEMA [Customers_Schema] AUTHORIZATION [Customers_Role] Deny
View
Definition to [Customers_Role]
exec sp_adduser 'phenson', 'phenson', [Customers_Role]
GRANT SELECT ON [dbo].[PT_VIEW] TO [Customers_Role]
When I log in as phenson I do not see PT_View but I can query on it. I need
to be able to see it.
"SpankyATL" wrote:

> I have a user that belongs to a role. This role only has select permissio
ns
> on 10 views. When I log in as this user via Management Studio I cannot se
e
> the views however I can execute queries against them.
> On another server that I did not setup, that I'm supposed to be mimicking
> the same security, this same user can see the views.
> Any ideas what the difference is?
> Thanks!|||I thought I'd answer my own question for those of you who come across this
some day. I need to remove the "Deny View Definition" portion and that took
care of it. The user was able to see that view and execute it but could not
see the script.
"SpankyATL" wrote:
[vbcol=seagreen]
> Here's the commands that I'm executing in order:
> CREATE ROLE [Customers_ROLE] Authorization dbo
> CREATE SCHEMA [Customers_Schema] AUTHORIZATION [Customers_Role] De
ny View
> Definition to [Customers_Role]
> exec sp_adduser 'phenson', 'phenson', [Customers_Role]
> GRANT SELECT ON [dbo].[PT_VIEW] TO [Customers_Role]
>
> When I log in as phenson I do not see PT_View but I can query on it. I ne
ed
> to be able to see it.
> "SpankyATL" wrote:
>|||SpankyATL (SpankyATL@.discussions.microsoft.com) writes:
> Here's the commands that I'm executing in order:
> CREATE ROLE [Customers_ROLE] Authorization dbo
> CREATE SCHEMA [Customers_Schema] AUTHORIZATION [Customers_Role] De
ny View
> Definition to [Customers_Role]
> exec sp_adduser 'phenson', 'phenson', [Customers_Role]
> GRANT SELECT ON [dbo].[PT_VIEW] TO [Customers_Role]
>
> When I log in as phenson I do not see PT_View but I can query on it. I
> need to be able to see it.
Why then did you do DENY VIEW DEFINITION to a role that you made phenson a
member of?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I was working from a script that was given to me. The person who developed
it mistakenly thought deny view would only deny the user from viewing the
source code.
"Erland Sommarskog" wrote:

> SpankyATL (SpankyATL@.discussions.microsoft.com) writes:
> Why then did you do DENY VIEW DEFINITION to a role that you made phenson a
> member of?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>

Wednesday, March 7, 2012

Can SQL 2008 coexist with SQL2005?

I have a SQL 2005 installed on my laptop with Windows XP Media Center Edition with the following components:

Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.1318
Operating System 5.1.2600

Is upgrade the only option or can SQL 2008 can exist with SQL2005?

Any help in instlling this would be helpful.

(Jayaram Krishnaswamy@.discussions.microsoft.com) writes: > I have a SQL 2005 installed on my laptop with Windows XP Media Center > Edition with the following components: > > > > Microsoft SQL Server Management Studio 9.00.1399.00 > Microsoft Analysis Services Client Tools 2005.090.1399.00 > Microsoft Data Access Components (MDAC) 2000.085.1117.00 > (xpsp_sp2_rtm.040803-2158) > Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 > Microsoft Internet Explorer 6.0.2900.2180 > Microsoft .NET Framework 2.0.50727.1318 > Operating System 5.1.2600 > > > > Is upgrade the only option or can SQL 2008 can exist with SQL2005? You should be able to do a side-by-side installation, since you only have the client tools. But I strongly recommend that you install Katmai, or any other beta software, on a virtual machine, or a machine that you can afford to scrap and reformat. And do definitely not upgrade, if you want to keep the machine. By the way, I notice that you have the RTM version of the SQL 2005 tools. I would recommend that you get hold of SP2 and install that. It does bring quite a few improvements. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Thamk you very much. Could you rpovide me with links for setting up on a virtual machine?|||(Jayaram Krishnaswamy@.discussions.microsoft.com) writes: > Thamk you very much. Could you rpovide me with links for setting up on a > virtual machine? It's not difficult at all. There's two products on the market I know of, Virtual PC from Microsoft and VMware. I stick to VMware myself. You can download VMware worksation from http://www.vmware.com. The most difficult part is probably the amount for the license... Once you have it installed, you use the wizard to create a new machine. To install the OS, just insert the OS in your DVD player, and VMware will pick it up. From there, it's very much like a regular install. VMware also has a VMware Player which is free. I'm uncertain whether it's good for creating new machines. Virtual PC comes with MSDN, so financially you may find it more attractive. I never used VPC myself, but rumour has it that VMware is a little more able. A tip when you set up your virtual machine, you first install the OS, activates it, and also add other programs that you don't want to be without. Before you actually slap any beta software on it, clone the machine, and install the beta software on the clone. That is, keep a template machine, so that you don't have to install the OS for each new CTP that comes out. A second tip is to make sure that you have sufficient with memory in your host machine. 1.5 GB is a minimum, if you give 250 MB to the virtual machine. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||

Thanks for the advice. Much obliged

Friday, February 24, 2012

can some one please tell me about the server name?

this is my first time to leave messange at here . I wish someone can tell me how to sign in at sql server management studio express CTP s server name .plsssssssssssssssssssssssssssssssssssssssssssssss

This is the SSIS forum. You should try and post the the management tools forum.

Thanks,

Matt

Sunday, February 12, 2012

Can not save relationship

Hi
I am using Sqlserver 2005 and in management I created some relations.
One of them fale with the below error.
I have tried to look for unmatched data and dublicates etc, but still keep
gettitng this error message.
What do you recommend me to do?
Thank you in advance
- Unable to create relationship 'FK_Transaktionsrader_Transaktionhuvud'.
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint
"FK_Transaktionsrader_Transaktionhuvud".
The conflict occurred in database "MbaseMuseumServerNetSQL", table
"dbo.Transaktionhuvud", column 'TransaktionhuvudTransaktionsnr'.
It would help us better assist you if you could include table DDL for both
tables; without it, we cannot help you. (For help with that refer to:
http://www.aspfaq.com/5006 and to
http://classicasp.aspfaq.com/general...-answered.html )
The less 'set up' work we have to do, the more likely you are going to have
folks tackle your problem and help you. Without this effort from you, we are
just playing guessing games.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Mattias" <Mattias@.discussions.microsoft.com> wrote in message
news:3EAD7DFC-C005-4415-A17F-5FD29EF8D4A2@.microsoft.com...
> Hi
> I am using Sqlserver 2005 and in management I created some relations.
> One of them fale with the below error.
> I have tried to look for unmatched data and dublicates etc, but still keep
> gettitng this error message.
> What do you recommend me to do?
> Thank you in advance
> - Unable to create relationship 'FK_Transaktionsrader_Transaktionhuvud'.
> The ALTER TABLE statement conflicted with the FOREIGN KEY constraint
> "FK_Transaktionsrader_Transaktionhuvud".
> The conflict occurred in database "MbaseMuseumServerNetSQL", table
> "dbo.Transaktionhuvud", column 'TransaktionhuvudTransaktionsnr'.
|||Hi and thanks for your reply.
I have the DDL for both tables ready here.
Can it be attached to the post or shall I send it separatly somewhere?
I tried to use sql code you recommend to generate inserts, sample data but I
receive the error below
"Could not find stored procedure sp_generate_inserts'." What do you
recommend me to do?
Mattias
"Arnie Rowland" wrote:

> It would help us better assist you if you could include table DDL for both
> tables; without it, we cannot help you. (For help with that refer to:
> http://www.aspfaq.com/5006 and to
> http://classicasp.aspfaq.com/general...-answered.html )
>
> The less 'set up' work we have to do, the more likely you are going to have
> folks tackle your problem and help you. Without this effort from you, we are
> just playing guessing games.
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Mattias" <Mattias@.discussions.microsoft.com> wrote in message
> news:3EAD7DFC-C005-4415-A17F-5FD29EF8D4A2@.microsoft.com...
>
>
|||Please include (copy and paste) the DDL in a post.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Mattias" <Mattias@.discussions.microsoft.com> wrote in message
news:14FF1450-A7AB-4D25-BE5C-4D75B50845F7@.microsoft.com...[vbcol=seagreen]
> Hi and thanks for your reply.
> I have the DDL for both tables ready here.
> Can it be attached to the post or shall I send it separatly somewhere?
> I tried to use sql code you recommend to generate inserts, sample data but
> I
> receive the error below
> "Could not find stored procedure sp_generate_inserts'." What do you
> recommend me to do?
> Mattias
>
> "Arnie Rowland" wrote:
|||Ok here it comes!
Mattias
USE [MbaseMuseumServerNetSQL]
GO
/****** Objekt: Table [dbo].[Transaktionhuvud] Skriptdatum: 10/09/2006
16:13:57 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Transaktionhuvud](
[TransaktionhuvudTransaktionsnr] [int] IDENTITY(1,1) NOT NULL,
[Transaktionskategorinummer] [int] NULL,
[TransaktionhuvudTransaktionhuvudKontaktnr] [int] NULL,
[ForetagsregisterGRUNDNR] [int] NULL,
[TransaktionhuvudTransaktionhuvudAnstalldHandlagge snr] [int] NULL,
[TransaktionhuvudTransaktionhuvudAnstalldFramtages nr] [int] NULL,
[TransaktionhuvudTransaktionhuvudAnstalldAvsynasnr ] [int] NULL,
[TransaktionhuvudTransaktionhuvudAnstalldPackas nr] [int] NULL,
[TransaktionhuvudTransaktionhuvudAnstalldKurirn r] [int] NULL,
[UtskriftsstatusSTATUSNR] [int] NULL,
[BetalningsStatusSTATUSNR] [int] NULL,
[TransaktionhuvudRegistreringsdatum] [datetime] NULL,
[DatumPreliminarRetur] [datetime] NULL,
[UtstallningStartdatum] [datetime] NULL,
[UtstallningSlutdatum] [datetime] NULL,
[Utstallning] [nvarchar](70) COLLATE Finnish_Swedish_CI_AS NULL,
[TransaktionhuvudTransaktionhuvudKontaktTransporto rAvhamtningnr] [int] NULL,
[TransaktionhuvudTransaktionhuvudKontaktTransporto rReturnr] [int] NULL,
[TransaktionhuvudTransaktionhuvudTransportsattAvha mtningnr] [int] NULL,
[TransaktionhuvudTransaktionhuvudTransportsattRetu rnr] [int] NULL,
[TransaktionhuvudDefinitivRetur] [bit] NULL,
[TransaktionhuvudDatumDefinitivRetur] [datetime] NULL,
[TransaktionhuvudAnmarkningar] [nvarchar](max) COLLATE
Finnish_Swedish_CI_AS NULL,
PRIMARY KEY CLUSTERED
(
[TransaktionhuvudTransaktionsnr] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudKontaktTransp ortorAvhamtningnr])
REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud1] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudKontaktTransp ortorReturnr])
REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud1]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud10] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudAnstalldAvsyn asnr])
REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud10]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud11] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudAnstalldPacka snr])
REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud11]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud12] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudAnstalldKurir nr])
REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud12]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud13] FOREIGN KEY([TransaktionhuvudTransaktionhuvudKontaktnr])
REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud13]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud2] FOREIGN KEY([BetalningsStatusSTATUSNR])
REFERENCES [dbo].[BetalningsStatus] ([BetalningsStatusSTATUSNR])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud2]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud3] FOREIGN KEY([UtskriftsstatusSTATUSNR])
REFERENCES [dbo].[Utskriftsstatus] ([UtskriftsstatusSTATUSNR])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud3]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud4] FOREIGN KEY([ForetagsregisterGRUNDNR])
REFERENCES [dbo].[Foretagsregister] ([ForetagsregisterGRUNDNR])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud4]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud5] FOREIGN KEY([Transaktionskategorinummer])
REFERENCES [dbo].[Transaktionskategori] ([Transaktionskategorinummer])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud5]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud6] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudTransportsatt Avhamtningnr])
REFERENCES [dbo].[TRANSPORTSATT] ([TRANSPORTSATTNR])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud6]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud7] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudTransportsatt Returnr])
REFERENCES [dbo].[TRANSPORTSATT] ([TRANSPORTSATTNR])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud7]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud8] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudAnstalldHandl aggesnr])
REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud8]
GO
ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
[ITransaktionhuvud9] FOREIGN
KEY([TransaktionhuvudTransaktionhuvudAnstalldFramt agesnr])
REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
GO
ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud9]
USE [MbaseMuseumServerNetSQL]
GO
/****** Objekt: Table [dbo].[Transaktionsrader] Skriptdatum: 10/09/2006
16:17:38 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Transaktionsrader](
[TransaktionsraderTransaktionsraderTransaktionsrad ] [int] IDENTITY(1,1) NOT
NULL,
[TransaktionsraderTransaktionsnr] [int] NULL,
[TransaktionsraderTransaktionsraderAvgiftsnr] [int] NULL,
[TransaktionsraderTransaktionsraderAvgiftsnr2] [int] NULL,
[TransaktionsraderTransaktionsraderAvgiftsnr3] [int] NULL,
[TransaktionsraderTransaktionsraderAvgiftsnr4] [int] NULL,
[TransaktionsraderTransaktionsraderEmballagenr] [int] NULL,
[Artikelnummer] [int] NULL,
[Bildnr] [int] NULL,
[TransaktionsraderForetagsnr] [int] NULL,
[TransaktionsraderAntal] [int] NULL,
[ExaktPlacering] [nvarchar](200) COLLATE Finnish_Swedish_CI_AS NULL,
[TillfalligRetur] [bit] NOT NULL,
[DatumTillfalligRetur] [datetime] NULL,
[TransaktionsraderForsakringsvarde] [decimal](17, 6) NULL,
[TransaktionsraderDefinitivRetur] [bit] NOT NULL,
[TransaktionsraderDatumDefinitivRetur] [datetime] NULL,
[AterDeposition] [bit] NOT NULL,
[DatumHamtningUtlamning] [datetime] NOT NULL,
[Undervisningstypnr] [int] NULL,
[DatumVisningStart] [datetime] NULL,
[TidVisningStart] [datetime] NULL,
[DatumVisningSlut] [datetime] NULL,
[TidVisningSlut] [datetime] NULL,
[Amne] [nvarchar](50) COLLATE Finnish_Swedish_CI_AS NULL,
[AntalLektioner] [nvarchar](50) COLLATE Finnish_Swedish_CI_AS NULL,
[AntalPersoner] [nvarchar](50) COLLATE Finnish_Swedish_CI_AS NULL,
[VisningInstalld] [bit] NULL,
[DatumVisningInstalld] [datetime] NULL,
[VisningUtford] [bit] NULL,
[transkontaktnr] [int] NULL,
[TransraderAnstalldGuideAnstalldnr] [int] NULL,
[accessionsnummer] [nvarchar](20) COLLATE Finnish_Swedish_CI_AS NULL,
PRIMARY KEY CLUSTERED
(
[TransaktionsraderTransaktionsraderTransaktionsrad ] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[FK_Transaktionsrader_Master] FOREIGN KEY([accessionsnummer])
REFERENCES [dbo].[Master] ([MasterAccessionsnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT
[FK_Transaktionsrader_Master]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader] FOREIGN KEY([Artikelnummer])
REFERENCES [dbo].[Artiklar] ([Artikelnummer])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader10] FOREIGN KEY([transkontaktnr])
REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader10]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader2] FOREIGN
KEY([TransaktionsraderTransaktionsraderEmballagenr ])
REFERENCES [dbo].[Emballage] ([Emballagenr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader2]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader3] FOREIGN
KEY([TransaktionsraderTransaktionsraderAvgiftsnr])
REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader3]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader4] FOREIGN
KEY([TransaktionsraderTransaktionsraderAvgiftsnr2])
REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader4]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader5] FOREIGN
KEY([TransaktionsraderTransaktionsraderAvgiftsnr3])
REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader5]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader6] FOREIGN
KEY([TransaktionsraderTransaktionsraderAvgiftsnr4])
REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader6]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader7] FOREIGN KEY([Undervisningstypnr])
REFERENCES [dbo].[UNDERVISNINGSTYP] ([Undervisningstypnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader7]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader8] FOREIGN KEY([Bildnr])
REFERENCES [dbo].[Bilder] ([Bildnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader8]
GO
ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
[ITransaktionsrader9] FOREIGN KEY([TransraderAnstalldGuideAnstalldnr])
REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
GO
ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader9]
"Arnie Rowland" wrote:

> Please include (copy and paste) the DDL in a post.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Mattias" <Mattias@.discussions.microsoft.com> wrote in message
> news:14FF1450-A7AB-4D25-BE5C-4D75B50845F7@.microsoft.com...
>
>
|||Mattias,
Try this. Use your script and create the two tables on
another test server or some test database.
Then run the script to create the relationship you are
having problems creating - or use Management Studio if
that's how you were doing it.
If you can create the relationship and don't get an error
then that tells you it's likely related to the data in the
two tables violating the constraint. If you can't create the
relationship from Management Studio, hit the script button
(hopefully there is one in the GUI end...don't use that much
so I don't remember) and try just executing the script. If
you still get an error using the script and with no data,
then post the script here.
-Sue
On Mon, 9 Oct 2006 07:20:02 -0700, Mattias
<Mattias@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Ok here it comes!
>Mattias
>USE [MbaseMuseumServerNetSQL]
>GO
>/****** Objekt: Table [dbo].[Transaktionhuvud] Skriptdatum: 10/09/2006
>16:13:57 ******/
>SET ANSI_NULLS ON
>GO
>SET QUOTED_IDENTIFIER ON
>GO
>CREATE TABLE [dbo].[Transaktionhuvud](
>[TransaktionhuvudTransaktionsnr] [int] IDENTITY(1,1) NOT NULL,
>[Transaktionskategorinummer] [int] NULL,
>[TransaktionhuvudTransaktionhuvudKontaktnr] [int] NULL,
>[ForetagsregisterGRUNDNR] [int] NULL,
>[TransaktionhuvudTransaktionhuvudAnstalldHandlagge snr] [int] NULL,
>[TransaktionhuvudTransaktionhuvudAnstalldFramtages nr] [int] NULL,
>[TransaktionhuvudTransaktionhuvudAnstalldAvsynasnr ] [int] NULL,
>[TransaktionhuvudTransaktionhuvudAnstalldPackas nr] [int] NULL,
>[TransaktionhuvudTransaktionhuvudAnstalldKurirn r] [int] NULL,
>[UtskriftsstatusSTATUSNR] [int] NULL,
>[BetalningsStatusSTATUSNR] [int] NULL,
>[TransaktionhuvudRegistreringsdatum] [datetime] NULL,
>[DatumPreliminarRetur] [datetime] NULL,
>[UtstallningStartdatum] [datetime] NULL,
>[UtstallningSlutdatum] [datetime] NULL,
>[Utstallning] [nvarchar](70) COLLATE Finnish_Swedish_CI_AS NULL,
>[TransaktionhuvudTransaktionhuvudKontaktTransporto rAvhamtningnr] [int] NULL,
>[TransaktionhuvudTransaktionhuvudKontaktTransporto rReturnr] [int] NULL,
>[TransaktionhuvudTransaktionhuvudTransportsattAvha mtningnr] [int] NULL,
>[TransaktionhuvudTransaktionhuvudTransportsattRetu rnr] [int] NULL,
>[TransaktionhuvudDefinitivRetur] [bit] NULL,
>[TransaktionhuvudDatumDefinitivRetur] [datetime] NULL,
>[TransaktionhuvudAnmarkningar] [nvarchar](max) COLLATE
>Finnish_Swedish_CI_AS NULL,
>PRIMARY KEY CLUSTERED
>(
>[TransaktionhuvudTransaktionsnr] ASC
>)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
>) ON [PRIMARY]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudKontaktTrans portorAvhamtningnr])
>REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud1] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudKontaktTrans portorReturnr])
>REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud1]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud10] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudAnstalldAvsy nasnr])
>REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud10]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud11] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudAnstalldPack asnr])
>REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud11]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud12] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudAnstalldKuri rnr])
>REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud12]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud13] FOREIGN KEY([TransaktionhuvudTransaktionhuvudKontaktnr])
>REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud13]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud2] FOREIGN KEY([BetalningsStatusSTATUSNR])
>REFERENCES [dbo].[BetalningsStatus] ([BetalningsStatusSTATUSNR])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud2]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud3] FOREIGN KEY([UtskriftsstatusSTATUSNR])
>REFERENCES [dbo].[Utskriftsstatus] ([UtskriftsstatusSTATUSNR])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud3]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud4] FOREIGN KEY([ForetagsregisterGRUNDNR])
>REFERENCES [dbo].[Foretagsregister] ([ForetagsregisterGRUNDNR])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud4]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud5] FOREIGN KEY([Transaktionskategorinummer])
>REFERENCES [dbo].[Transaktionskategori] ([Transaktionskategorinummer])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud5]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud6] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudTransportsat tAvhamtningnr])
>REFERENCES [dbo].[TRANSPORTSATT] ([TRANSPORTSATTNR])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud6]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud7] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudTransportsat tReturnr])
>REFERENCES [dbo].[TRANSPORTSATT] ([TRANSPORTSATTNR])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud7]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud8] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudAnstalldHand laggesnr])
>REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud8]
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] WITH CHECK ADD CONSTRAINT
>[ITransaktionhuvud9] FOREIGN
>KEY([TransaktionhuvudTransaktionhuvudAnstalldFram tagesnr])
>REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
>GO
>ALTER TABLE [dbo].[Transaktionhuvud] CHECK CONSTRAINT [ITransaktionhuvud9]
>
>USE [MbaseMuseumServerNetSQL]
>GO
>/****** Objekt: Table [dbo].[Transaktionsrader] Skriptdatum: 10/09/2006
>16:17:38 ******/
>SET ANSI_NULLS ON
>GO
>SET QUOTED_IDENTIFIER ON
>GO
>CREATE TABLE [dbo].[Transaktionsrader](
>[TransaktionsraderTransaktionsraderTransaktionsrad ] [int] IDENTITY(1,1) NOT
>NULL,
>[TransaktionsraderTransaktionsnr] [int] NULL,
>[TransaktionsraderTransaktionsraderAvgiftsnr] [int] NULL,
>[TransaktionsraderTransaktionsraderAvgiftsnr2] [int] NULL,
>[TransaktionsraderTransaktionsraderAvgiftsnr3] [int] NULL,
>[TransaktionsraderTransaktionsraderAvgiftsnr4] [int] NULL,
>[TransaktionsraderTransaktionsraderEmballagenr] [int] NULL,
>[Artikelnummer] [int] NULL,
>[Bildnr] [int] NULL,
>[TransaktionsraderForetagsnr] [int] NULL,
>[TransaktionsraderAntal] [int] NULL,
>[ExaktPlacering] [nvarchar](200) COLLATE Finnish_Swedish_CI_AS NULL,
>[TillfalligRetur] [bit] NOT NULL,
>[DatumTillfalligRetur] [datetime] NULL,
>[TransaktionsraderForsakringsvarde] [decimal](17, 6) NULL,
>[TransaktionsraderDefinitivRetur] [bit] NOT NULL,
>[TransaktionsraderDatumDefinitivRetur] [datetime] NULL,
>[AterDeposition] [bit] NOT NULL,
>[DatumHamtningUtlamning] [datetime] NOT NULL,
>[Undervisningstypnr] [int] NULL,
>[DatumVisningStart] [datetime] NULL,
>[TidVisningStart] [datetime] NULL,
>[DatumVisningSlut] [datetime] NULL,
>[TidVisningSlut] [datetime] NULL,
>[Amne] [nvarchar](50) COLLATE Finnish_Swedish_CI_AS NULL,
>[AntalLektioner] [nvarchar](50) COLLATE Finnish_Swedish_CI_AS NULL,
>[AntalPersoner] [nvarchar](50) COLLATE Finnish_Swedish_CI_AS NULL,
>[VisningInstalld] [bit] NULL,
>[DatumVisningInstalld] [datetime] NULL,
>[VisningUtford] [bit] NULL,
>[transkontaktnr] [int] NULL,
>[TransraderAnstalldGuideAnstalldnr] [int] NULL,
>[accessionsnummer] [nvarchar](20) COLLATE Finnish_Swedish_CI_AS NULL,
>PRIMARY KEY CLUSTERED
>(
>[TransaktionsraderTransaktionsraderTransaktionsrad ] ASC
>)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
>) ON [PRIMARY]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[FK_Transaktionsrader_Master] FOREIGN KEY([accessionsnummer])
>REFERENCES [dbo].[Master] ([MasterAccessionsnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT
>[FK_Transaktionsrader_Master]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader] FOREIGN KEY([Artikelnummer])
>REFERENCES [dbo].[Artiklar] ([Artikelnummer])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader10] FOREIGN KEY([transkontaktnr])
>REFERENCES [dbo].[Kontakter] ([Kontaktnummer])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader10]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader2] FOREIGN
>KEY([TransaktionsraderTransaktionsraderEmballagen r])
>REFERENCES [dbo].[Emballage] ([Emballagenr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader2]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader3] FOREIGN
>KEY([TransaktionsraderTransaktionsraderAvgiftsn r])
>REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader3]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader4] FOREIGN
>KEY([TransaktionsraderTransaktionsraderAvgiftsnr2 ])
>REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader4]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader5] FOREIGN
>KEY([TransaktionsraderTransaktionsraderAvgiftsnr3 ])
>REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader5]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader6] FOREIGN
>KEY([TransaktionsraderTransaktionsraderAvgiftsnr4 ])
>REFERENCES [dbo].[Avgifter] ([Avgiftsnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader6]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader7] FOREIGN KEY([Undervisningstypnr])
>REFERENCES [dbo].[UNDERVISNINGSTYP] ([Undervisningstypnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader7]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader8] FOREIGN KEY([Bildnr])
>REFERENCES [dbo].[Bilder] ([Bildnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader8]
>GO
>ALTER TABLE [dbo].[Transaktionsrader] WITH CHECK ADD CONSTRAINT
>[ITransaktionsrader9] FOREIGN KEY([TransraderAnstalldGuideAnstalldnr])
>REFERENCES [dbo].[Anstallda] ([AnstalldaAnstalldnr])
>GO
>ALTER TABLE [dbo].[Transaktionsrader] CHECK CONSTRAINT [ITransaktionsrader9]
>"Arnie Rowland" wrote:

Friday, February 10, 2012

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:


Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error


Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.


I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.


Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:


Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error


Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.


I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.


Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:


Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error


Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.


I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.


Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:


Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error


Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.


I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.


Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:


Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error


Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.


I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.


Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:


Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error


Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.


I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.


Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh