|
|
|
|
|
|
|
|
|
|
|
|
| SQL Server 2008 : Full-Text Search Troubleshooting |
| After you create full-text catalogs and indexes that you can query, you have to maintain them. The catalogs and indexes maintain themselves, but you need to focus on backing up and restoring them as well as tuning your search solution for optimal performance |
|
|
|
|
|
| SQL Azure : Security - Access Control |
| So far, you've spent a lot of time encrypting and hashing values for increased confidentiality and integrity. However, another important aspect of the CIA triad is access control. |
|
|
|
| SQL Server 2008 : Full-Text Searches (part 2) |
| SQL Server 2008 FTS supports the proximity predicate, which allows you to search on tokens that are close, or near, to each other. Near is defined as within 50 words. Words separated by more than 50 words do not show up in a CONTAINS or CONTAINSTABLE search |
|
|
|
| SQL Azure : Securing Your Data (part 3) - Certificates |
| Hashing isn't nearly as complicated as you've seen so far. And although you can store the values you've encrypted so far in the database, in this example you hash all the columns of the rows (except the ID value) to make sure they're unchanged |
|
| SQL Azure : Securing Your Data (part 2) - Hashing |
| Hashing isn't nearly as complicated as you've seen so far. And although you can store the values you've encrypted so far in the database, in this example you hash all the columns of the rows (except the ID value) to make sure they're unchanged |
|
| SQL Azure : Securing Your Data (part 1) - Encryption |
| As mentioned previously, data encryption isn't available. Why? Because SQL Azure doesn't support X.509 certificates yet. Certificates are necessary for many encryption-related features, such as Transparent Data Encryption (TDE), column-level encryption, and certain T-SQL commands, such as FOR ENCRYPTION and SIGNBYCERT.
|
|
| SQL Azure : Security - Overview |
| Confidentiality is the ability to ensure that data can be accessed only by authorized users. It's about protecting your data from prying eyes or from inadvertent leakage by using multiple technologies |
|
|
|
| Setting Up a Full-Text Index (part 3) - Diagnostics |
| After you create catalogs and indexes, you occasionally need to get information about your catalogs, tables, and indexes. So that you can do this, Microsoft has supplied the sp_help_fulltext_tables and sp_help_fulltext_columns stored procedures and the system view sys.fulltext_catalogs. |
|
| Setting Up a Full-Text Index (part 2) - Full-Text Indexing of BLOBs and XML |
| SQL Server 2008 can natively index content columns of the char, nchar, varchar, nvarchar, text, and xml data types. If you want to index binary large objects, you need to store them in the image or varbinary(max) column and associate with the image column a column that will contain the extension the document would have if it were stored in the filesystem. |
|
|
|
| Implementing SQL Server 2008 Full-Text Catalogs |
| In SQL Server 2005 and previous versions, full-text catalogs were containers for your full-text indexes. In SQL Server 2008, they are really virtual containers on which you can tag various settings and have these settings apply to all indexes placed in that catalog or rebuild all indexes in a catalog at one time. |
|
| How SQL Server FTS Works |
| As mentioned previously, in SQL Server 2008, the catalogs are now stored inside the full-text engine. This redesign has resulted in many architectural changes in SQL Server 2008 Full-Text Search. |
|
|
|
|
|
|
|
| SQL Azure : Creating Databases, Logins, and Users (part 1) |
| When you create databases in a non-Azure environment, you have to know and specify a lot in the CREATE statement. For example, you must provide the path and physical object names of the database and log files, as well as the database size and optionally the maximum size and file growth |
|
| SQL Azure : Azure Server Administration (part 3) - Databases |
| This protection mechanism is the SQL Azure firewall, which prevents restricted access to all your databases until you physically specify which computers have permission. Access to your SQL Azure databases is based on the originating IP address that makes a request. |
|
|
|
|
|
