|
You mean that you suggesting to use the tool and not to suggest to write script for it?
|
|
|
|
|
Sorry I was not very clear, I use the tool and the generated script. IF it fails (it automatically rolls back the transaction) I then use a subset of the objects, starting with the tables. I repeat this till I get a successful merge. I then save that script and get the next subset, repeating until I get all the changes across to the target database.
At that point I have a set of scripts that can be run sequentially to successfully update the target database. This is a pain but it is better than hand coding which is how I used to do it!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I have a method that takes a SQL query and a file name, then converts that query into an XML-based Excel file. Works great. The code gets the schema of the query, and uses the column names to generate the column headers in Excel. This, too, works great.
The problem is aliasing the columns into the headers that I want. I am using this notation:
SELECT
"First Name" = view.MeaninglessColumnNameImposedBySystem1,
"Last Name" = view.MeaninglessColumnNameImposedBySystem2,
"Address 1" = view.MeaninglessColumnNameImposedBySystem3,
...
FROM LongViewName AS view
WHERE etc=@etc
Whether I have one column or 50, the query takes several minutes to run; the more data, the longer it takes. If I were to use SELECT *, with no aliasing, I can return the data in a few seconds, regardless of how many rows are returned.
I have also tried view.MeaninglessColumnNameImposedBySystem1 AS [First Name], which does not speed up the results.
Presumably, this is an optimization issue where * lets SQL make assumptions that it cannot when each column is aliased. Any suggestions on what I can do with the query to speed things up?
|
|
|
|
|
Hi,
You can use Column Alias like as follows
SELECT V.MeaninglessColumnNameImposedBySystem1 [First Name],
V.MeaninglessColumnNameImposedBySystem2 [Last Name],
V.MeaninglessColumnNameImposedBySystem3 [Address 1],
...
FROM LongViewName AS V
WHERE etc=@etc
for best practice go for Column names without any space like FirstName, LastName, Address1 ...
Regards
GVPrabu
|
|
|
|
|
If you are returning the data to c# and then converting the datatable to Excel you could always rename the table columns after the retrieval.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I am trying to avoid that: the idea is to have one general method that will take any of nine queries to generate different files than to have nine specialist methods that each take only a single query.
|
|
|
|
|
Somewhere you are defining the column names (you want it done on the entry query definition) either in 1 or 9 query constructors, I am suggesting moving the naming to post query execution, sticking that code into 1 method is trivial. Still it is a kludge b/c the aliasing should work 
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Like I said, the aliasing is working, but it takes a very long time for the query to return. In one test case, a query with aliased columns took almost 6 minutes to return; the identical query with unaliased columns took less than a second. This kind of time difference is pretty consistent, regardless of how many columns are requested, and scales closely to the number of rows returned (the more rows, the longer the aliased query takes.)
It is very frustrating.
|
|
|
|
|
I traced the problem to a piece of code that uses SqlDataAdapter.Fill to populate a DataSet, then took to the Internet.
It turns out that there is some optimization that SQL does with queries, where it tries to import indexes from underlying tables. This works fine as long as the columns in the view match up with the columns from the tables. When you alias the query's columns, however, things can degenerate into a quagmire of competing indexes; the delay is caused by SQL trying to wait out a resolution. You can get rid of the delay by instructing SQL to abandon arithmetic operations that result in an overflow or underflow. Huh? 
The solution was to prefix the query with SET ARITHABORT ON; which tells SQL to just fly over the swamp rather than try to navigate through it. After the query, tack on ; SET ARITHABORT OFF; to reset the server variable, mainly because there is probably a reason why it set to OFF in the first place.
|
|
|
|
|
Good bit of research, thanks for posting the solution, that with parameter sniffing goes into my odd box of delays to hunt for!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi everybody!
Please can you tell me what is the best tool for creating a database from scratch?
|
|
|
|
|
Member 9611795 wrote: Please can you tell me what is the best tool for creating a database from scratch?
A computer?
If that wasn't the answer you thought you were looking for then you need to understand that you don't choose a database based on tool but rather on the functionality of the database vendor. AFTER you have chosen a database then you look for applications that allow you to manage the database application.
|
|
|
|
|
Pen and paper: figure out what you want the database to do for you and then create a structure to support that. Sketching it out with a pen and paper is the first thing I do (or whiteboard).
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
It's all about learning not working! so I want to know the tool which can help me to insert data and retrieve it and more.
is SQL server the tool that can help me? or ADO.NET?? and what is the difference between them??
|
|
|
|
|
Member 9611795 wrote: I want to know the tool which can help me to insert data and retrieve it and more.
SQL Server is where data is stored, ADO.NET is a set of objects for Creating, Reading, Updating and Deleting data.
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
|
|
|
|
|
Just Like Mark wrote, I start with the whiteboard.
When that gets to small I make the model in Oracle SQL Developer Data Modeler [^], which supports Oracle, SQL Server and DB2 out of the box, and you can make your own design rules as well.
And as an extra plus, it supports source control via Subversion.
"The ones who care enough to do it right care too much to compromise."
Matthew Faithfull
|
|
|
|
|
|
Hi Friends,
I have windows service which will execute a STORED PROCEDURE during a time period, fetches email IDs from DB and will send emails to them.
I am passing only one argument @ValidTillDays INT.
I made this service run on each day.
If its running for 3 days, then for the first day it executes perfectly.
For the second day and remaining all days it gives following error.
Procedure or function "BlaBlaBla" has too many arguments specified.
I have only one input parameter and I am passing only one too.
And if this was the case it could have given the error for the first time also.
Please help me if you find any clue .
Thanks 
By:
Hemant Thaker
|
|
|
|
|
Hemant Thaker wrote: If its running for 3 days, then for the first day it executes perfectly.
For the second day and remaining all days it gives following error.
Strange. Based on what you share, sounds like some logical error where you are considering the DayNo. Are you? Somehow, somewhere the current day is getting into picture while running the procedure and the error. Did you DEBUG and see? Check if so.
|
|
|
|
|
I suspect you are concatenating the parameter value and passing in a string! You might want to post the code used to build the procedure call.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Thanks for your responses.
Error is resolved, that was more logical.
I was creating Command object at class level, and adding parameters to it in remainderMailtimer_Elapsed().
This event will execute on timer interval.
So when it executes first time it find one parameter and runs successfully.
after 3 minutes interval it executes event for the second time and adds same parameter to it.
so now command object will have two parameters and corresponding SP has one. So it was throwing error.
I changed the code and created command object at event level.
Thanks.
By:
Hemant Thaker
|
|
|
|
|
Hi
Our ERP system has a stock master table. It consist of the fields 'warehouse', 'product' and a bunch of other fields relating to the stock item.
A product can exist in various warehouses, so it is the warehouse +product combination that is unique.
How would the primary key (if any) be set on this table?
|
|
|
|
|
A primary key (often) consists out of multiple columns. I'd suggest putting the primary key on BOTH, and to add an autoincrement-field and make that unique. Use the autoincrement-column to make relations to other tables.
ALTER TABLE dbo.MasterTable ADD CONSTRAINT PK_MasterTable
PRIMARY KEY CLUSTERED (WareHouseId, ProductId); (And call the autoincrement "MasterTableId")
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thanks Eddie, but you have totally lost me?
If I lok at the two lines:
ADD CONSTRAINT PK_MasterTable
Prevents any duplicates in MasterTable column
and
PRIMARY KEY CLUSTERED (WareHouseId, ProductId)
Stores the data physically sorted by WarehouseId then ProductID?
Or are there three Primary keys now?
If you look at the table in MSQuery, the Product is bold, so is this the primary key?
|
|
|
|
|
Richard.Berry100 wrote: Prevents any duplicates in MasterTable column
No, it doesn't; it's the part behind that which says "which type" of constraint. It's a single statement, not two separate statements.
Richard.Berry100 wrote:
PRIMARY KEY CLUSTERED (WareHouseId, ProductId)
Stores the data physically sorted by WarehouseId then ProductID?
Yup.
Richard.Berry100 wrote: Or are there three Primary keys now?
One (compound) primary key, consisting of two columns, and the name of that constraint is "PK_MasterTable".
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
