Showing posts with label project. Show all posts
Showing posts with label project. Show all posts

Wednesday, March 21, 2012

Lines disappear

Hello Group,
has anyone ever seen this problem. I was asked to work on an old database
from project I had not been on (when does that ever happen...) anyway I go
right to the database diagram to get a look at what I am dealing with. When
I open the diagram a strange behavior manifests itself: the lines that show
relationships between the tables all disappear!
I can see them for just a moment and then just one by one disappear. The
daughter tables all have a field that has a "record id" which has a PK. They
have a field which stores the PK of the related table.
Why is this does this?
RichIs this for SQL 2005 or a previous version? Are you connecting from a
workstation or locally?
"Rich" wrote:
> Hello Group,
> has anyone ever seen this problem. I was asked to work on an old database
> from project I had not been on (when does that ever happen...) anyway I go
> right to the database diagram to get a look at what I am dealing with. When
> I open the diagram a strange behavior manifests itself: the lines that show
> relationships between the tables all disappear!
> I can see them for just a moment and then just one by one disappear. The
> daughter tables all have a field that has a "record id" which has a PK. They
> have a field which stores the PK of the related table.
> Why is this does this?
> Rich|||Hello Edgardo,
Version = 2000
Connection = my workstation has Enterprise Manager connecting to the
database server
"Edgardo Valdez, MCTS, MCITP, MCSD, MCDBA" wrote:
> Is this for SQL 2005 or a previous version? Are you connecting from a
> workstation or locally?
> "Rich" wrote:
> > Hello Group,
> >
> > has anyone ever seen this problem. I was asked to work on an old database
> > from project I had not been on (when does that ever happen...) anyway I go
> > right to the database diagram to get a look at what I am dealing with. When
> > I open the diagram a strange behavior manifests itself: the lines that show
> > relationships between the tables all disappear!
> >
> > I can see them for just a moment and then just one by one disappear. The
> > daughter tables all have a field that has a "record id" which has a PK. They
> > have a field which stores the PK of the related table.
> >
> > Why is this does this?
> >
> > Rich|||I have some more questions:
1-. If you can connect locally to the same server, do you experience the
same behavior?
2-. Did you try connecting from another workstation?
3-. What is the Service Pack Level in the server?
"Rich" wrote:
> Hello Edgardo,
> Version = 2000
> Connection = my workstation has Enterprise Manager connecting to the
> database server
> "Edgardo Valdez, MCTS, MCITP, MCSD, MCDBA" wrote:
> > Is this for SQL 2005 or a previous version? Are you connecting from a
> > workstation or locally?
> >
> > "Rich" wrote:
> >
> > > Hello Group,
> > >
> > > has anyone ever seen this problem. I was asked to work on an old database
> > > from project I had not been on (when does that ever happen...) anyway I go
> > > right to the database diagram to get a look at what I am dealing with. When
> > > I open the diagram a strange behavior manifests itself: the lines that show
> > > relationships between the tables all disappear!
> > >
> > > I can see them for just a moment and then just one by one disappear. The
> > > daughter tables all have a field that has a "record id" which has a PK. They
> > > have a field which stores the PK of the related table.
> > >
> > > Why is this does this?
> > >
> > > Rich

Lines disappear

Hello Group,
has anyone ever seen this problem. I was asked to work on an old database
from project I had not been on (when does that ever happen...) anyway I go
right to the database diagram to get a look at what I am dealing with. When
I open the diagram a strange behavior manifests itself: the lines that show
relationships between the tables all disappear!
I can see them for just a moment and then just one by one disappear. The
daughter tables all have a field that has a "record id" which has a PK. They
have a field which stores the PK of the related table.
Why is this does this?
Rich
Is this for SQL 2005 or a previous version? Are you connecting from a
workstation or locally?
"Rich" wrote:

> Hello Group,
> has anyone ever seen this problem. I was asked to work on an old database
> from project I had not been on (when does that ever happen...) anyway I go
> right to the database diagram to get a look at what I am dealing with. When
> I open the diagram a strange behavior manifests itself: the lines that show
> relationships between the tables all disappear!
> I can see them for just a moment and then just one by one disappear. The
> daughter tables all have a field that has a "record id" which has a PK. They
> have a field which stores the PK of the related table.
> Why is this does this?
> Rich
|||I have some more questions:
1-. If you can connect locally to the same server, do you experience the
same behavior?
2-. Did you try connecting from another workstation?
3-. What is the Service Pack Level in the server?
"Rich" wrote:
[vbcol=seagreen]
> Hello Edgardo,
> Version = 2000
> Connection = my workstation has Enterprise Manager connecting to the
> database server
> "Edgardo Valdez, MCTS, MCITP, MCSD, MCDBA" wrote:

Lines disappear

Hello Group,
has anyone ever seen this problem. I was asked to work on an old database
from project I had not been on (when does that ever happen...) anyway I go
right to the database diagram to get a look at what I am dealing with. When
I open the diagram a strange behavior manifests itself: the lines that show
relationships between the tables all disappear!
I can see them for just a moment and then just one by one disappear. The
daughter tables all have a field that has a "record id" which has a PK. The
y
have a field which stores the PK of the related table.
Why is this does this?
RichIs this for SQL 2005 or a previous version? Are you connecting from a
workstation or locally?
"Rich" wrote:

> Hello Group,
> has anyone ever seen this problem. I was asked to work on an old database
> from project I had not been on (when does that ever happen...) anyway I go
> right to the database diagram to get a look at what I am dealing with. Wh
en
> I open the diagram a strange behavior manifests itself: the lines that sho
w
> relationships between the tables all disappear!
> I can see them for just a moment and then just one by one disappear. The
> daughter tables all have a field that has a "record id" which has a PK. T
hey
> have a field which stores the PK of the related table.
> Why is this does this?
> Rich|||Hello Edgardo,
Version = 2000
Connection = my workstation has Enterprise Manager connecting to the
database server
"Edgardo Valdez, MCTS, MCITP, MCSD, MCDBA" wrote:
[vbcol=seagreen]
> Is this for SQL 2005 or a previous version? Are you connecting from a
> workstation or locally?
> "Rich" wrote:
>|||I have some more questions:
1-. If you can connect locally to the same server, do you experience the
same behavior?
2-. Did you try connecting from another workstation?
3-. What is the Service Pack Level in the server?
"Rich" wrote:
[vbcol=seagreen]
> Hello Edgardo,
> Version = 2000
> Connection = my workstation has Enterprise Manager connecting to the
> database server
> "Edgardo Valdez, MCTS, MCITP, MCSD, MCDBA" wrote:
>sql

Monday, March 12, 2012

Limiting Records Returned

I'm building an Access front end (A2K2 ADP project) to view records on a SQL 2000 Server, and want to ensure the fastest performance for my users. I expect the database to grow to around 25,000 records (after that, they'll be archived), and would like opi
nions/comments on the best way to access the data. I would guess that a recordset would be fastest, but how do you set up a form to be based on a recordset instead of just hooking directly to the underlying table?
TIA,
Terry Roberts
Check the ADO and ADP references in the Microsoft Office
2000/Visual Basic Programmer's Guide:
http://msdn.microsoft.com/library/de...radobasics.asp
You can also find a list of Access resources here:
http://msdn.microsoft.com/library/en...acacclinks.asp
And...you really should considering getting the book: Access
Developer's Guide to SQL Server by
Mary Chipman and Andy Baron.
-Sue
On Mon, 10 May 2004 09:11:08 -0700, "Terry Roberts"
<anonymous@.discussions.microsoft.com> wrote:

>I'm building an Access front end (A2K2 ADP project) to view records on a SQL 2000 Server, and want to ensure the fastest performance for my users. I expect the database to grow to around 25,000 records (after that, they'll be archived), and would like op
inions/comments on the best way to access the data. I would guess that a recordset would be fastest, but how do you set up a form to be based on a recordset instead of just hooking directly to the underlying table?
>TIA,
>Terry Roberts

Friday, March 9, 2012

Limiting Records Returned

I'm building an Access front end (A2K2 ADP project) to view records on a SQL
2000 Server, and want to ensure the fastest performance for my users. I exp
ect the database to grow to around 25,000 records (after that, they'll be ar
chived), and would like opi
nions/comments on the best way to access the data. I would guess that a reco
rdset would be fastest, but how do you set up a form to be based on a record
set instead of just hooking directly to the underlying table?
TIA,
Terry RobertsCheck the ADO and ADP references in the Microsoft Office
2000/Visual Basic Programmer's Guide:
adobasics.asp" target="_blank">http://msdn.microsoft.com/library/d...
adobasics.asp
You can also find a list of Access resources here:
http://msdn.microsoft.com/library/e.../acacclinks.asp
And...you really should considering getting the book: Access
Developer's Guide to SQL Server by
Mary Chipman and Andy Baron.
-Sue
On Mon, 10 May 2004 09:11:08 -0700, "Terry Roberts"
<anonymous@.discussions.microsoft.com> wrote:

>I'm building an Access front end (A2K2 ADP project) to view records on a SQL 2000 S
erver, and want to ensure the fastest performance for my users. I expect the databas
e to grow to around 25,000 records (after that, they'll be archived), and would like
op
inions/comments on the best way to access the data. I would guess that a recordset would be
fastest, but how do you set up a form to be based on a recordset instead of just hooking dir
ectly to the underlying table?
>TIA,
>Terry Roberts

Limiting Records Returned

I'm building an Access front end (A2K2 ADP project) to view records on a SQL 2000 Server, and want to ensure the fastest performance for my users. I expect the database to grow to around 25,000 records (after that, they'll be archived), and would like opinions/comments on the best way to access the data. I would guess that a recordset would be fastest, but how do you set up a form to be based on a recordset instead of just hooking directly to the underlying table
TIA
Terry RobertsCheck the ADO and ADP references in the Microsoft Office
2000/Visual Basic Programmer's Guide:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovradobasics.asp
You can also find a list of Access resources here:
http://msdn.microsoft.com/library/en-us/dnacc2k/html/acacclinks.asp
And...you really should considering getting the book: Access
Developer's Guide to SQL Server by
Mary Chipman and Andy Baron.
-Sue
On Mon, 10 May 2004 09:11:08 -0700, "Terry Roberts"
<anonymous@.discussions.microsoft.com> wrote:
>I'm building an Access front end (A2K2 ADP project) to view records on a SQL 2000 Server, and want to ensure the fastest performance for my users. I expect the database to grow to around 25,000 records (after that, they'll be archived), and would like opinions/comments on the best way to access the data. I would guess that a recordset would be fastest, but how do you set up a form to be based on a recordset instead of just hooking directly to the underlying table?
>TIA,
>Terry Roberts

Wednesday, March 7, 2012

Limited number of assemblies available in Visual Studio SQL Server Projects

Hi,

When starting a SQL Server Project in Visual Studio, there are a very limited number of assemblies available to reference. Does anyone know why?

Specifically I would like to use "Microsoft.AnalysisServices.AdomdClient". Does anyone know how I could do that?

Best Regards,

Johan ?hln,
IFS

Hi,

if you want more than these one, you have to register them in the GAC to see them in VS. The ones listed were intensivly tested by Microsoft not to produce any memory leaks being threadsafe etc. Additional (custom) resources have to be listed first for the computer and marked with the security policy level they need. "Doing the stack walk" while registering them at deployment time, SQL Server makes sure that called ressources reflect the at most the security settings of the registered assembly.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Jens,

Thanks for your answer.

Microsoft.AnalysisServices.AdomdClient is already registered in the GAC, but I don't see it in Visual Studio. What else do I have to do to be able to reference it?

From what I can see it has unrestricted permissions in .NET Runtime Security Policy.

Best Regards,

Johan ?hln

|||

Hi Johan,

As the previous person mentions, the assemblies that are available to references in a sql server project are restricted. I think what this person meant to say is that these system assemblies are loaded from the GAC by sql server, yet this has nothing to do with when you wish to use an unsupported system assembly.

Note here about my terminology, system assembly = .Net BCL, user assembly = custom assembly.

You are wishing to reference an unsupported system assembly in sql server, this can be attempted (I say this because depending upon what the individual assembly tries to do, even in unsafe it will not be allowed to run when called upon and it's corresponding app. domain will be unloaded).

To do this, first run a create assembly statement referencing the adomd client assembly. Second, create a new regular class library project and add your reference to the adomd client libary. Then build the class in VS. Next, run the create assembly statement for your newly created class.

*You may have to set lower permission sets on the adomd client depending upon its attributes etc. There is a concept known as Host Protection Attributes (HPAs) which help sql server in determing which managed libaries should be allowed to execute within the hosted clr context. Basically, you may have to set the adomd client to unsafe it is "threatening" enough. But again, even with unsafe, sql server will only allow so much to occur aka you cannot kill sqlservr.exe from sqlclr code.

Hope this helps,

Derek

|||

Two additional points:

1. Actually, VS has a nice feature where if the assembly you're looking for is already registered in your SQL Server database, then you can reference it directly from your VS Database Project, even if it is a custom assembly or one that is not on the supported system assemblies list. It should show up normally under "Add Reference".

2. There are extremely few things that do not work in unsafe permission set, and the restrictions that are in place weren't done with reliability in mind. There are a number of ways to effectively kill your SQL Server process when running under unsafe, if you wanted to.

Steven

|||Noted on the unsafe being able to kill sqlservr. I did find that HPAs are only used in safe and unsafe perm buckets.|||i meant safe and external access :)|||

Thank you for your answers.

It seems impossible to reference AdomdClient from a SQL Server assembly:

It cannot be added using CreateAssembly|||

Johan ?hln wrote:

It seems impossible to reference AdomdClient from a SQL Server assembly:

It cannot be added using CreateAssembly

|||

TITLE: Microsoft SQL Server Management Studio Express

Create failed for SqlAssembly 'Microsoft.AnalysisServices.AdomdClient'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+SqlAssembly&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

CREATE ASSEMBLY failed because type 'ShilohSchemas' in safe assembly 'Microsoft.AnalysisServices.AdomdClient' has a static field 'shilohSchemas'. Attributes of static fields in safe assemblies must be marked readonly in Visual C#, ReadOnly in Visual Basic, or initonly in Visual C++ and intermediate language.
Warning: The SQL Server client assembly 'microsoft.analysisservices.adomdclient, version=9.0.242.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment. (Microsoft SQL Server, Error: 6211)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=6211&LinkId=20476


BUTTONS:

OK

|||

I have solved this. It works if you create it as unsafe.

Thanks for your answers,

Johan

limited connections on the developer edition

hi all,

I installed sql server developer edition on

xp box. created a new ssis project and

then when i right click on control flow

then click new connections

i see only limited connection available.

how can i install the other connection option

such as oledb. etc.

thanks

joey

got it

my integration service

is running with limited rights

Friday, February 24, 2012

Limitation on Conn.Execute in classic .ASP & ADO with SQL Server

Hello,

I have a project (using classic ASP & SQL Server) which adds one execute sql statement at a time to a temporary array, and then I join that array with a chr(30) (record separator), to a string variable called strSQL. I then run the following line of code:

conn.execute(strSQL)

I was wondering if there was any limitation to how large the strSQL variable can be? Reason I ask is because thru log writes I can see all of my sql execute lines exist in the variable strSQL prior to running the "conn.execute(strSQL)" command; however, not all of the lines run at the time of execution. Remember, this bug only is occuring whenever I have say over 600 sql lines to execute.

My understanding is that there was no limitation on the size of the string strSQL; however, in the interest of getting the bug fixed quick enough, I decided to just run a loop for each sql statment and run "conn.execute(strSQL)" every 50 times. This, in turn, has solved the problem and I do save all of my data; however, my original bug still exists.

Does anyone know why I have to split the sql commands and execute.com every 50 times instead of just being able to do it once ?

Please let me know. Thanks in advance.It's probably your data provider that is limiting you. Which one are you using, OleDb for SQL Server (SQLOLEDB)? The batch separator for that provider is a semicolon (;) as far as I know. Maybe you'd have better luck with that? I am doubting it but it would be worth a try.

Terri|||I am using ADO thru an ASP page to connect to SQL Server. I have tried numerous separator's (comma,vertibar) with still no luck. That's why I ended up going with the chr(30).

Doing the loop and execute.conn every 50 times through the loop has seemed to definately fix the bug. I am still just curious as to why I couldn't execute the entire command immediately.

What is strange is that I can use ADO and write a general Visual Basic 6.0 application and execute the sql string just fine. Considering ADO is used in both the VB6.0 and .ASP applications you would think it would work?

Oh well, thanks for the thought. Have a good one.|||But which PROVIDER are you using? Are you using the same provider in your VB program that you are in your ASP application (ie, what does your connection string look like for both)? Is the same MDAC version on both machines?

Terri|||Terri,

Yes, MDAC 2.8 is on the web server using the .ASP & ADO connection. However, the VB Project I've created to test out this large sql string is only on my local machine. It does not use a web server or anything like that.|||Sorry forgot to mention that the execute statement is the same in both.

Execute.Conn sqlstr

Where "sqlstr" is representing the hundreds and hundreds of insert statements I need to execute.|||But which PROVIDER are you using? What does the Conn.ConnectionString look like?

Terri|||the connection string looks like:

"DRIVER=SQL Server;SERVER=ServerName;User ID=UserID;PASSWORD=PASSWORD;DATABASE=Database"

I hope this is what you are referring too. Sorry for the confusion.|||You're using the ODBC provider. Use the OleDB provider instead and see if it makes a difference, with semicolons (;) separating your commands.

Your connection string would look like this:


"Provider=sqloledb;Data Source=ServerName;Initial Catalog=Database;User Id=UserID;Password=PASSWORD;"

Seehttp://www.connectionstrings.com for more help on connection strings.

Terri