|
Eddy Vluggen wrote: If the original data can be reconstructed from that resulting data, you'll be
able to reverse that process.
Bullshit - you cannot reverse the result of a calculation - nevertheless you can have a calculation of other colums ...
Eddy Vluggen wrote: Not according to the theories of Codd.
You will at least violate 2NF ...
Eddy Vluggen wrote: 1) Allowed by whom? If it's my responsibility, then I'll model as I think is
correct - if it were something that could simply be "decided" once and
for all, they'd put it in a servicepack and be done with it.
Ok, it's YOUR decision, but HERE we're talking about NORMALIZED databases !!!
Eddy Vluggen wrote: 2) Has nothing to do with speed.
Let's assume it's somethig like SUM( SQRT( PI * DRM) )
Depending on your indices and the sort of query this can be a REALLY time consuming operation, and in such a case a denormalization would be valid (=accepted), but colA +colB isn't such a case, 'cause it's cheap to calc.
Eddy Vluggen wrote: 3) Whether a column is calculated doesn't say anything about the fact "when"
it's going to be calculated.
See my response above
Eddy Vluggen wrote: That would be modeled as a calculated column in the conceptual model.
The relational model from Codd don't know 'calculated column', as this is AGAINST the model by itself ...
|
|
|
|
|
Klaus-Werner Konrad wrote: bullsh*t - you cannot reverse the result of a calculation - nevertheless you can have a calculation of other colums ...
From mp/h to m/s and back.
Klaus-Werner Konrad wrote: You will at least violate 2NF ...
Second normal form is about finding the complete key. It doesn't make statements on atomicity of facts.
Klaus-Werner Konrad wrote: Ok, it's YOUR decision, but HERE we're talking about NORMALIZED databases !!!
I know. Stop shouting.
Klaus-Werner Konrad wrote: Let's assume it's somethig like SUM( SQRT( PI * DRM) )
Depending on your indices and the sort of query this can be a REALLY time consuming operation, and in such a case a denormalization would be valid (=accepted), but colA +colB isn't such a case, 'cause it's cheap to calc.
Let me repeat that; Normalization has nothing to do with speed. It's about creating a theoretical correct model.
A wise man might decide to optimize by denormalizing when implementing the physical layer.
Klaus-Werner Konrad wrote: The relational model from Codd don't know 'calculated column', as this is AGAINST the model by itself ...
Name the rule that it breaks.
I are Troll 
|
|
|
|
|
Eddy Vluggen wrote:
Klaus-Werner Konrad wrote: bullsh*t - you cannot reverse the
result of a calculation - nevertheless you can have a calculation of other
colums ...
From mp/h to m/s and back.
This is not a calculation - it's a conversion, and every conversion can be reverted !
Eddy Vluggen wrote:
Klaus-Werner Konrad wrote: You will at least violate 2NF
...
Second normal form is about finding the complete key. It
doesn't make statements on atomicity of facts.
Wikipedia:
"No non-prime attribute in the table is functionally dependent on a proper subset of a candidate key"
Eddy Vluggen wrote:
Klaus-Werner Konrad wrote: Ok, it's YOUR decision, but HERE
we're talking about NORMALIZED databases !!!
I know. Stop
shouting.
Sorry - I'm just old fashioned (You've ever connected via a 300baud accoustic modem ? No Internet, no HTML, no chance to enhance your msg than put *stars* or _underlines_ around it ?)
And - *just* in _these_ days I prefer plain text messages, 'cause evertything else can carry some unwanted payload ...
Eddy Vluggen wrote:
Klaus-Werner Konrad wrote: Let's assume it's somethig like
SUM( SQRT( PI * DRM) )
Depending on your indices and the sort of query this
can be a REALLY time consuming operation, and in such a case a denormalization
would be valid (=accepted), but colA +colB isn't such a case, 'cause it's cheap
to calc.
Let me repeat that; Normalization has nothing to do
with speed. It's about creating a theoretical correct model.
A wise man
might decide to optimize by denormalizing when implementing the physical layer.
So you repeat my statement (see underlined portions of my original post) ...
Eddy Vluggen wrote:
Klaus-Werner Konrad wrote: The relational model from Codd
don't know 'calculated column', as this is AGAINST the model by itself
...
Name the rule that it breaks.
As said before: NF2
|
|
|
|
|
Klaus-Werner Konrad wrote: This is not a calculation - it's a conversion, and every conversion can be reverted !
A conversion is a specific type of calculation. A multiplication with a constant is another example; not a conversion, but still reversible.
Klaus-Werner Konrad wrote: So you repeat my statement (see underlined portions of my original post) ...
No, I did not repeat you, but you're correct to state that in such a case it would be defend able to denormalize.
Klaus-Werner Konrad wrote: As said before: NF2
I was looking for argumentation. As said before, it doesn't. All non-atomic facts have been removed before it can be called 1NF. The 2NF rule states that the fact that's described (possibly the result of a calculation) should be identifyable with the same key that you use to identify the tupel.
Take a "Departments" table - it may very well have a fact that states how many employees it currently harbors. The 2NF rule states that the "count" fact belong to the object that we use to identify a single tupel in departments-table. It's the key that gives the fact a context.
The fact "32" as a "count" would lose context (and no longer be information) if we cannot link it to a specific department. It's not relevant for the conceptual model how that number gets there - it may be a small operation, it may be a long operation. When describing the domain-model, we do include the information that it's information that can be deduced from other data - saves the person who has to implement the physical layer a bit time.
I are Troll
|
|
|
|
|
The relational model was developed to deal with issue of data inconsistency and data redundancy.
Calculated columns are redundant and also they can cause data inconsistency problems; if the values used in the calculation are changed, the calculate column will be inconsistent/incorrect.
|
|
|
|
|
If the original values change then, there will be data inconsistency (i.e. the calculated columns will not be correct).
|
|
|
|
|
SilimSayo wrote: If the original values change then, there will be data inconsistency (i.e. the calculated columns will not be correct).
Incorrect isn't the same as inconsistent, and up-to-date is not the same as incorrect.
I are Troll 
|
|
|
|
|
|
SilimSayo wrote: Semantics!!!!
The exact definition is important, and not just a semantical detail. And no, I do not appreciate hit&run comments, as it's a lousy way of communicating.
I are Troll
|
|
|
|
|
Suppose I have a calculated field for age computed from dob and the current date. If this field is not updated and you query someone's age, it will return incorrect results. For example, if the query returns someone's [current] age as 64 when it should have been 65, the result would be incorrect.
|
|
|
|
|
What database are you using? If you are using SQL Server, you can create computed columns. I believe other databases have similar features too. Better yet, create a View with the calculated column.
|
|
|
|
|
You are right, a view (evtl. companyied (is this right ?) with functions) is the right way on the DB side, but that was not the original question - that was about creating additional coloums in the BASE table that hold the calculated results
|
|
|
|
|
HI.
I am currently working on a database application.
I use Sql express studio to model the database and then use LINQ in c# to access it.
Whereas everything is great , the thing is that the database is on the same laptop where there is the application to access it.
Let say this laptop name is "A".
i use the connection string connString = @"server = .\sqlexpress;integrated security = true;database = Whatever";
(YES i am using Winodws authenciation)
But if i want to access database on a different Laptop from the application running on "A", what will be the connection string??
I will connect the Both Laptops through their own WIFI.
|
|
|
|
|
When connecting to remote database you replace the server name. Currently you use dot to tell that the server is local. In case of remote server you would have a connection string like:
server=servername\instancename;integrated security...
Have a look at this site: http://www.connectionstrings.com/sql-server-2005[^]
|
|
|
|
|
I guess i have to use one of the connection string mentioned:-
someting like.
Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
I want to know . how to know ip of one computer??
what is network library??
and i am using sql express studio 2008 r2 on both computers.
So where is the keyword /sqlexpress is to be used?
|
|
|
|
|
You don't have to know the IP address, you can use names instead.
\SQLEXPRESS isn't a keyword, it's the name of the SQL Server instance. For example if I have a server called Machine1 and I have two different instances of SQL Server in that server; Production and Test. Now if I want to connect to the Test-instance of SQL Server, I'd use a connection string like:
Data Source=Machine1\Test;...
Perhaps the easiest way to see locally the name of the instance is to open Control Panel and look at services. The instance name is in parenthesis on the service name.
|
|
|
|
|
oh ok..i am getting it..
so my final connection string will look something like this ?
server=computername\instancename ; integrated security = false ; database = "whatever" ; user id = sa ; Password=pass;
|
|
|
|
|
Exactly 
|
|
|
|
|
I am trying to do it from a different laptop , which is on the same network...
But it gives error when i try to connect through sql express studio.......
error 26
A network or instance-specific error occured while esablishing a connection to sql server..it might be not found or accesible................is there any other setting i am missing???
and how to make sure that both computers are properly connected over the network?
|
|
|
|
|
|
|
You're welcome Glad it got solved.
|
|
|
|
|
I had asked this question elsewhere and was advised to ask here instead.
I am wondering if anyone knows how internet connection latency and download speed affect query execution time in SQL Server Management Studio. Is that product similar to using a Data Reader instead of a Data Adapter? Is there a flag I can set to make it more like a Data Adapter? I am trying to get better performance on a remote office, especially since Disaster Recovery can be better handled from the headquarters.
I ran a test in SQL Server Management against the same database across the country. One internet connection had 4x the download speed according to speedtest.net, but a larger latency in ms. The difference is that one connection was a slow ethernet connection and the other a faster wireless connection. Same locations, multiple tests with similar results.
Somewhat surprisingly, the connection with the faster download speed took 50% longer to return a recordset in the 5-20 MB range. Is this because querying in SQL Server Management Studio is similar to executing a query with a Data Reader instead of a DataAdapter? If not, what is the issue?
|
|
|
|
|
Hi,
Don't know if SSMS is more like a data reader than a data adapter and I would guess that it depends on how are you using it. For example if you create a query and run it in a query window you'll get results you cannot modify much like with data reader. On the other hand if you open a table for editing then you can modify the results so the functionality is closer to a data adapter.
Concerning the network latency issue, there's one parameter you can define before you connect, that's affecting the speed quite a lot. If you click the options in the connect dialog, you'll find the network packet size which can be modified. If you have a latency issue, I'd guess that you could increase the packet size even to 16'383 bytes which is the maximum (instead of the default 4'096). If you like you can change this default packet size in the instance settings.
|
|
|
|
|
Thanks! I got a 2x to 6x speedup after raising the packet size to 32767. Now the query execution and transportation time is faster with the faster internet connection with slightly higher latency.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
