Monday, March 26, 2012
minvalue and maxvalue in sequence
I try to create a sequence with following requirements:
create a sequence that will generate integers starting with the value 9. Each value should be three less than the previous value generated. The lowest possible balue the sequence should be allowed to generate is -1, and it should not be allowed to cycle.
I think values generated by this sequence are 9, 6, 3, 0
my sql statement goes like this:
SQL> create sequence MY_FIRST_SEQUENCE
2 increment by -3
3 start with 9
4 minvalue -1
5 nocycle;
create sequence MY_FIRST_SEQUENCE
*
ERROR at line 1:
ORA-04004: MINVALUE must be less than MAXVALUE
I don't know what's the maxvalue in this squence. Should it be 9 if that's the case. why do I get a error message?
Plase give me some suggestio on how can I make this sequence work. Thanks!
sjgrad03
12-03Even without knowing anything about sequences, if this is a DESCENDING sequence and it STARTS WITH 9, then it is logical that its MAXIMUM VALUE is 9.
Your statement will be executed properly if you add MAXVALUE n, where n >= START_WITH_value. If it is not clear enough, here's an example:
CREATE SEQUENCE my_seq
START WITH 9
MAXVALUE 9
MINVALUE -1
INCREMENT BY -3;
or
CREATE SEQUENCE my_seq
START WITH 9
MAXVALUE 1000
MINVALUE -1
INCREMENT BY -3;
NOCYCLE is the default and it is not necessary to specify it.
Read more about creating Oracle sequences here (http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6015.htm).
Friday, March 23, 2012
Minimum Setup Requirements for SQL 2005 Replication.
2 Remote Laptops running SQL Server 2005 Express databases with the ability
to synchronize with each other. Also they should be able to synch with a
server hosting a SQL Database whci is accessible from 2 other Desktop PCs.
What are the SQL CAL Licensing issues that would apply to this scenario.
Regards
Unfortunately SQL Server Express can only be a subscriber to all types of
replication. All subscriptions must be created through RMO or replication
stored procedures.
Regarding your desktop pc's - If they are running workgroup edition they can
have up to 25 merge subscribers, but 5 transactional subscribers. In regards
to licensing anything which accesses the desktop must have a license, which
can be a CAL or a server per processor license (which will not make a whole
lot of sense).
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Stuart Lowe" <StuartLowe@.discussions.microsoft.com> wrote in message
news:6C1471E6-61F1-4BF2-AAA8-16E67A29A967@.microsoft.com...
> What are the minimum setup requirements to support the following.
> 2 Remote Laptops running SQL Server 2005 Express databases with the
> ability
> to synchronize with each other. Also they should be able to synch with a
> server hosting a SQL Database whci is accessible from 2 other Desktop PCs.
> What are the SQL CAL Licensing issues that would apply to this scenario.
> Regards
sql
Minimum Requirements to issue an XMLA Command to analysis services
What are the minimum requirements (in terms of referenced assemblies) I need in .NET programming to issue and xmla command to the analysis services?
What we want to do?
We want to create and SSDS .NET Stored Procedure which inserts a value in an SSAS Dimension Table and then in the same procedure issue an SSAS XMLA Process ADD Command.
It must be an SQL Procedure because auf external requirements
The Issue
IF we reference the Namespaces "Microsoft.AnalysisServices" and "Microsoft.AnalysisServices.XMLA" we receive errors
CREATE ASSEMBLY failed because method "add_CollectionChanging" on type "Microsoft.AnalysisServices.ModelComponentCollection" in external_access assembly "Microsoft.AnalysisServices" has a synchronized attribute. Explicit synchronization is not allowed in external_access assemblies.
We are only able to allow EXTERNAL_ACCESS on the SQL Server but no UNSAFE Assemplies.
Therefor the question - what is the minimum possibility to issue an XMLA Command?
- what is the SQL Agent Job Step Analysis Services Command using?
- Could XMLA Commandes be executed through an Analysis Services 9.0 OLEDB Connection (by OLEDB Command)?
- Without AMO?
Thankes for your Help
HANNES
Microsoft.AnalysisServices.AdomdClient is another option for sending XMLA commands, but it also does not support partially trusted callers so you'll get the same error. Any assembly that allows you to execute arbitrary XMLA commands should require special code access permissions (or simply be marked as unsafe) since XMLA commands can change data or reviel sensitive data and thus have the potential to be dangerous for untrusted code running under a trusted user account.
What you can do is write your own assembly which uses one of these other assemblies to send the XMLA command and mark it as supporting partially trusted callers. You'll need to be very careful if you do this and limit the capabilities of this new assembly so that it cannot be used in any harmful way (since code you don't completely trust can run it.) This means it should not execute arbitrary XMLA commands or connect to arbirtrary sources. You'll need to read up on code access security if you go this route - both to get it to work and make sure you don't introduce a security weekness into your system. If you accept any parameters into the methods, also be sure you protect against XMLA injection (like SQL injection but for XMLA). This solution can work, but use extreme caution since it affects the security of your system.
Wednesday, March 21, 2012
Minimum Hardware Requirements For SQL Client
SQL client on 10 of our contractors' computer with a maximum database
size of 5GB?
Thank you very much
mike
The client machines can be pretty wimpy because the server process the T-SQL
and just returns the results the clients.
At a minimum I would want a PIII running Win2k with 256MB RAM.
Keith
"Mike" <mj1sql@.yahoo.com> wrote in message
news:9a55bd2d.0410070814.5589c64e@.posting.google.c om...
> What would be the minumum hardware (and software) requirements to have
> SQL client on 10 of our contractors' computer with a maximum database
> size of 5GB?
> Thank you very much
> mike
Friday, March 9, 2012
Migration Problem of Sql 2000 to SQL 2005
Hi all,
We migrated our database from SQL 2000 to SQL 2005. But we faced some problems, according to the requirements of our project we dont want to apply some constraints on some fields of some tables. But when we run the database script of our old database on SQL 2005, it applied many constraints which causing some serious problems in our project. There are about 100+ tables in our database and some one told me that we have to false every constraint manually. Now, my question is that is there any solution of our this problem.
Best Regards
hi,
can you please expand on
it applied many constraints which
can you post some SQL2000 DDL and how you like it to be in SQL2005?
regards
|||We need some additional information here to help, could you expand on exactly what constraints you are seeing? One thing you may want to consider is that you can just move your SQL 2000 database file (data and log) to the SQL 2005 computer and attach the file, that should result in the exact same structure.
Mike