Presumably it throws an exception and posting that exception as part of your post is helpful.
Presuming that the exception is telling you the statement is too big...
If your SQL statement is too long then SQL/C# will have a problem with it. The solution is to reduce the size. (Might note that that could indicate a database design issue as well.)
Using the database import tools (sqlldr?) might help with the problem but might not. If not or you don't want to use it then solutions.
1. Do two calls.
2. Pass in a blob and parse it to create dynamic sql.
If it was me I would presume that there is a design issue.
The thing is I am still new. Is it not good that we do more of the grunt work at the starting stages itself? And DAL coding is quite hectic. Sometimes I really feel why do we need it anyway. Thank you for eye opener atleast.
Search a topic like "Business Intelligence" and you will get an idea of what others are doing.
At a high level, you have a central database which collects data from different systems, then you have reporting tools which either you or your user community can write their own reports. Also, sometimes you can have these reports run on a scheduled basis and have their output delivered to whoever needs it.
The cost of implementing such a system can be quite high.
You might want to implement some pieces of this.
1) Build a tool which will load your data extracts (xml files) into a central database.
2) Create views or stored procedures which "normalize" your data
3) Use a reporting tool to generate the reports you need or show your users how they can connect to the central database via Excel to get their own data. (See topics like Microsoft Query)
Empower the user to access the data and you will spend less time on maintenance.
Best as I can tell from your question you are asking for something that is impossible.
SQL Server normally installs as an application. Thus it is ALWAYS visible on the client machine.
Now you could re-architect your application to use the embedded version of SQL Server (I think.) Then it would appear that only your application existed. I suspect this would require a bit of work. There are limitations to that approach.
Note as well that this has nothing to do with security. Security means something completely different.
If any user want to insert another row in that table then it is not possible message should be display....
Please Just reply the Query & CODE....
A database does not display messages, it holds data. It holds data in bulk, not in "single records". What you want does not make much sense from a data-viewpoint.
Now, this is not the place to "order" code like you do. The questions on the forums are answered by volunteers, in their free time. Put it in a object, serialize it, and stuff it in a single-column blob.
I didn't downvote you, but I think most people here won't like to do your work. You can ask questions, you can show your code and ask for help, but you have to do your work on your own. So my answer is: Definitely not!
Super solution but can't be replicated in other databases like oracle.
Identity is a near equivalent to rowid concept in Oracle but its a dynamic value i.e not a sequence generator . Hence may be Only possible in sql server.
If you change the start value of the identity seed (I'm pretty sure this can be done) and truncate the table the hard coded 1 would fail mind you it is a silly request in the first place and I suspect the OP does not even know what you are talking about.
Never underestimate the power of human stupidity
Not sure it is the right forum...
I'm using VisualStudio 2010 and trying to use schema compare tool to deploy changes from my db project to my database (SQL server 2008).
when trying to deploy the changes I made in my db project I get anexception with the following message:
"Cannot create index. Object 'v_TQ_IFCR_DATA_COVERAGE' was created with the following SET options off: 'ANSI_NULLS, QUOTED_IDENTIFIER'."
If I will go the the index properties,I see that AnsiNulls
and QuatedIdentifiers are set to project default.
When changing those settings to ON I manage to deploy all updates without any exception.
How can I change project default settings?
I have more then 200 different objects(tables,stored procedures,functions,indexes etc.) and I don't want to change the settings of each object.
In my schema compare the options if "Ignore AnsiNulls" and
"Ignore QuatedIdentifiers" where checked,so updated AnsiNulls and QuatedIdentifiers settings was not marked as needs to be updated during the schema compare.
Also,I've set AnsiNulls and QuatedIdentifiers default settings
to true in database.sqlsettings file.
How I can use case statement in where clause…..
Below query raised syntax error.
Select * from Mytable where ((EffectiveDate <= @ MyeffectiveDate AND
CASE WHEN BillingTerminationDate = NULL THEN
(terminationDate is null or BillingTerminationDate > =@ MyeffectiveDate)
ELSE BillingTerminationDate > =@ MyeffectiveDate)
WHAT EXACLY I WANT
If(BillingTerminationDate is null) then where clause should used ” (terminationDate is null or BillingTerminationDate > =@ MyeffectiveDate)” statement.
Other wise used BillingTerminationDate > =@ MyeffectiveDate statement.
Waiting for your need full reply.
Thanks in advance.
Thanks Richard Deeming.
I try above query bur not succeed.
Finally I do increase number of query lines and doing below…..
select * from Mytable where ((EffectiveDate <= @MyeffectiveDate and BillingTerminationDate isnotnulland (BillingTerminationDate > =@MyeffectiveDate)) OR IsAdjustment=1)
select * from Mytable where ((EffectiveDate <= @MyeffectiveDate and BillingTerminationDate isnulland (TerminationDate > =@MyeffectiveDate)) OR IsAdjustment=1)
Right now its working as my expactation. But having doubt that after reviewing, may or may not it will give me pain.
CASE is an expression and not an executable statement.
The general form of the predicate of a WHERE clause is expression operator expression where operator is = or <> or > or < etc.
You can use a case as one of the expressions in the predicate.
But you shouldn't need the case. Try this instead:
OR BillingTerminationDate > =@ MyeffectiveDate
and we'll see if I understood you correctly.
People say nothing is impossible, but I do nothing every day.