Wednesday, September 10, 2014
Monday, September 8, 2014
How to check sql server is running which bit (32 or 64 bit) version
by using @@version :
Open SQL Server Management Studio>right click on the DB Server> select New Query
select @@version
Result:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (Intel X86) Apr 22 2011 11:57:00 Copyright (c) Microsoft Corporation Developer Edition on Windows NT 6.1 <X64> (Build 7600: ) (WOW64)
Server Name:
select @@servername
Service Name:
select @@servicename
Open SQL Server Management Studio>right click on the DB Server> select New Query
select @@version
Result:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (Intel X86) Apr 22 2011 11:57:00 Copyright (c) Microsoft Corporation Developer Edition on Windows NT 6.1 <X64> (Build 7600: ) (WOW64)
Server Name:
select @@servername
Service Name:
select @@servicename
Thursday, September 4, 2014
Collection Classes
In AX collection classes have been designed for storing objects.
The classes are implemented in C++ to achieve the maximum performance (they are system classes).
collection classes are extended with Object class.
Array: Similar to the X++ language array type except that it can hold values of any single type, including objects and records. Objects are accessed in a specific order.
http://msdn.microsoft.com/EN-US/library/array.aspx
List: Contains any number of elements that are accessed sequentially.
Lists are structures that can contain values of any X++ type.
All the values in the list must be of the same type.
http://msdn.microsoft.com/EN-US/library/list.aspx
Map: The Map class allows you to associate one value (the key) with another value.
Both the key and value can be any valid X++ type, including objects.
The types of the key and the value are specified in the declaration of the map.
The way in which maps are implemented means that access to the values is very fast.
http://msdn.microsoft.com/EN-US/library/map.aspx
Struct: A struct holds several values of any X++ type, to group the information about a specific entity.
http://msdn.microsoft.com/EN-US/library/struct.aspx
Set:The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered.
http://msdn.microsoft.com/EN-US/library/set.aspx
Changes to the Collection Classes in Dynamics AX 2012
http://blogs.msdn.com/b/x/archive/2011/09/07/changes-to-the-collection-classes-in-dynamics-ax-2012.aspx
The classes are implemented in C++ to achieve the maximum performance (they are system classes).
collection classes are extended with Object class.
Array: Similar to the X++ language array type except that it can hold values of any single type, including objects and records. Objects are accessed in a specific order.
http://msdn.microsoft.com/EN-US/library/array.aspx
List: Contains any number of elements that are accessed sequentially.
Lists are structures that can contain values of any X++ type.
All the values in the list must be of the same type.
http://msdn.microsoft.com/EN-US/library/list.aspx
Map: The Map class allows you to associate one value (the key) with another value.
Both the key and value can be any valid X++ type, including objects.
The types of the key and the value are specified in the declaration of the map.
The way in which maps are implemented means that access to the values is very fast.
http://msdn.microsoft.com/EN-US/library/map.aspx
Struct: A struct holds several values of any X++ type, to group the information about a specific entity.
http://msdn.microsoft.com/EN-US/library/struct.aspx
Set:The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered.
http://msdn.microsoft.com/EN-US/library/set.aspx
Changes to the Collection Classes in Dynamics AX 2012
http://blogs.msdn.com/b/x/archive/2011/09/07/changes-to-the-collection-classes-in-dynamics-ax-2012.aspx
Tuesday, September 2, 2014
AOSAuthorzation property on Tables
The AOSAuthorization table property enables you to specify which data access operations must undergo user permission checking.
The four fundamental data access operations are create, read, update, and delete.
No permission checking is done when the AOSAuthorization property is set to None.
Ex: Suppose AOSAuthorization is set to CreateDelete on a given table.
In this case, create and delete operations would be allowed to execute only if the Application Object Server (AOS) can confirm that the user has the appropriate permissions.
Update and read operations would execute without checking user permissions, because they are not mentioned in the chosen AOSAuthorization value.
The AOSAuthorization property also applies to views.
Ex: For example, suppose view Vew2 reads data from table Tab3. You have no read permission to either Vew2 or Tab3. The AOSAuthorization value on Vew2 is None, but on Tab3 it is CreateReadUpdateDelete. When you try to read from Vew2 the outcome will be a successful retrieval of data.
The four fundamental data access operations are create, read, update, and delete.
- None (Default)
- CreateDelete
- UpdateDelete
- CreateUpdateDelete
- CreateReadUpdateDelete
No permission checking is done when the AOSAuthorization property is set to None.
Ex: Suppose AOSAuthorization is set to CreateDelete on a given table.
In this case, create and delete operations would be allowed to execute only if the Application Object Server (AOS) can confirm that the user has the appropriate permissions.
Update and read operations would execute without checking user permissions, because they are not mentioned in the chosen AOSAuthorization value.
The AOSAuthorization property also applies to views.
Ex: For example, suppose view Vew2 reads data from table Tab3. You have no read permission to either Vew2 or Tab3. The AOSAuthorization value on Vew2 is None, but on Tab3 it is CreateReadUpdateDelete. When you try to read from Vew2 the outcome will be a successful retrieval of data.
Monday, September 1, 2014
TableGroup
Table groups provide a method for categorizing tables according to the type of data they contain.
Use:When exporting data, you can use table groups to filter records.
For example, if you wanted to specify that customers should be exported but customer transactions should not. The table group that a table belongs to is defined by the TableGroup property of the table.
The groups available are defined by the system Enum TableGroup.
Parameter:
The table contains data primarily used as parameters or setup information for one of the main tables (a table that has a TableGroup property of Main).
The table typically contains only one record per company.
Ex: CustParameter, VendParameter
Group:
The table contains data primarily used to categorize one of the main tables (a table that has a TableGroup property of Main).
There is a one-to-many relationship between a Group table and a Main table.
Ex: CustGroup, VendGroup
Main:
The table is one of the principal tables in the application and contains data for a central business object. The table typically holds static, base information.
There is a one-to-many relationship between a Main table and a Transaction table.
Ex: CustTable VendTable
Transaction, Transaction header, and Transaction line
The table contains transaction data. The table is typically not used for data entry directly.
Worksheet, Worksheet header, and Worksheet line
Miscellaneous:
The table does not fit in any of the other categories. This is the default value for a new table.
Ex: TableExpImpDef
Framework :
Tables that are used by the underlying Microsoft Dynamics AX frameworks, such as Application Integration Framework (AIF). These tables are created during installation and are not associated with configuration keys.
Reference : Tables that contain reference data.
Use:When exporting data, you can use table groups to filter records.
For example, if you wanted to specify that customers should be exported but customer transactions should not. The table group that a table belongs to is defined by the TableGroup property of the table.
The groups available are defined by the system Enum TableGroup.
Parameter:
The table contains data primarily used as parameters or setup information for one of the main tables (a table that has a TableGroup property of Main).
The table typically contains only one record per company.
Ex: CustParameter, VendParameter
Group:
The table contains data primarily used to categorize one of the main tables (a table that has a TableGroup property of Main).
There is a one-to-many relationship between a Group table and a Main table.
Ex: CustGroup, VendGroup
Main:
The table is one of the principal tables in the application and contains data for a central business object. The table typically holds static, base information.
There is a one-to-many relationship between a Main table and a Transaction table.
Ex: CustTable VendTable
Transaction, Transaction header, and Transaction line
The table contains transaction data. The table is typically not used for data entry directly.
The tables in the Transaction header table group categorize the tables in the Transaction line table group.
There is a one-to-many relationship between a Transaction header table and Transaction line tables.
Ex: CustTrans, VendTransWorksheet, Worksheet header, and Worksheet line
Tables that contain information that is validated and made into transactions.
Unlike the data that is contained in the tables in the Transaction table groups, data in the Worksheet table groups is temporary.
There is a one-to-many relationship between a Transaction header table and Transaction line tables.
Miscellaneous:
The table does not fit in any of the other categories. This is the default value for a new table.
Ex: TableExpImpDef
Framework :
Tables that are used by the underlying Microsoft Dynamics AX frameworks, such as Application Integration Framework (AIF). These tables are created during installation and are not associated with configuration keys.
Reference : Tables that contain reference data.
Monday, August 25, 2014
Full Text Indexes on Tables
Ax 2012 provides full text functionality that enables Ax to search the business data over a large volume of text data or documents.
we can create full text indexes on tables of type Main and Group.
Before we use full text functionality in application we must configure SQL Server full text.
How to create a Full Text Index:
http://msdn.microsoft.com/EN-US/library/gg845129.aspx
How to use :
http://msdn.microsoft.com/EN-US/library/gg879757.aspx
we can create full text indexes on tables of type Main and Group.
Before we use full text functionality in application we must configure SQL Server full text.
How to create a Full Text Index:
http://msdn.microsoft.com/EN-US/library/gg845129.aspx
How to use :
http://msdn.microsoft.com/EN-US/library/gg879757.aspx
Subscribe to:
Posts (Atom)
update_recordset with joins
update_recordset with joins update_recordSet storeTransfer setting TransactionId = transfertable.TransferId join transfert...
-
void clicked() { EcoResProductMaster ecoResProductMaster; EcoResProductIdentifier ecoResProductIdent...
-
Network Requirements: Microsoft Dynamics AX can operate on networks that use Internet Protocol Version 4 ( IPv4 ) or Internet Protocol Ve...
-
index : An index is a table-specific database structure that speeds the retrieval of rows from a table. Uses : Indexes are used to impro...