What is MySQL Error Code 1005?

SQL error 1005, also known as “Can’t create table (errno: 150)”, is a MySQL error that occurs when there is a problem with a foreign key constraint. Foreign key constraints are used to establish relationships between tables in a relational database. They ensure that data integrity is maintained by preventing actions that would create inconsistent or invalid data.

Possible Causes

When you encounter SQL error 1005, MySQL is telling you that there is an issue with a foreign key constraint while trying to create or modify a table. This error can be caused by a variety of reasons, such as:

1. Incorrect syntax: The foreign key constraint might not be defined properly, leading to a syntax error in your SQL statement.
2. Data type mismatch: The data types of the columns involved in the foreign key constraint must match exactly. If there is a mismatch in data types, MySQL will throw error 1005.
3. Missing referenced table: The table referred to in the foreign key constraint might not exist in the database.
4. Incompatible foreign key constraint: The referenced table might have a foreign key constraint with incompatible attributes, such as different collation, character set, or storage engine.
5. Circular reference: A circular reference occurs when two or more tables reference each other with foreign key constraints, creating a loop. MySQL does not allow circular references, and it will result in error 1005.

Fix MySQL Error Code 1005

Now that we have a basic understanding of SQL error 1005 and its possible causes, let’s dive into the solutions to fix this issue.

1. Check for typos or errors in your table definitions: Make sure that you have correctly defined your table columns, data types, and constraints. Double-check for any misspellings, missing or extra commas, and other syntax errors in your table definitions.
2. Ensure that referenced columns and tables exist: If you are defining foreign key constraints, make sure that the referenced columns and tables actually exist in the database. If the referenced table has not been created yet, or if it has been dropped or renamed, you may encounter error code 1005.
3. Check for conflicting constraints: If you have multiple foreign key constraints in your table definitions, ensure that there are no conflicts. For example, if you have two foreign keys that reference the same column in another table, MySQL will raise error code 1005. Make sure that your constraints are properly defined and do not conflict with each other.
4. Verify data types and lengths: Make sure that the data types and lengths of the columns in your foreign key and referencing tables match exactly. Data type mismatches can result in error code 1005.
5. Disable foreign key checks: You can temporarily disable foreign key checks in MySQL by running the following command before creating or modifying tables: SET FOREIGN_KEY_CHECKS = 0;. This can help you identify and fix any issues with foreign key constraints. However, be cautious when using this approach, as it can potentially lead to inconsistent data if not used properly.
6. Check for circular references: If you have circular references in your foreign key constraints, where Table A references Table B and Table B references Table A, you will encounter error code 1005. To fix this issue, you may need to restructure your database schema to remove circular references.
7. Check for storage engine compatibility: If you are using different storage engines for your referencing and referenced tables, you may encounter error code 1005. Make sure that the storage engines are compatible, such as using InnoDB for both tables, as some storage engines do not support foreign key constraints.
8. Review MySQL error logs: Check the MySQL error logs for any additional information on the cause of the error. The error logs may provide more detailed information about the specific issue that is causing error code 1005.

By following these steps, you should be able to identify and fix the issue that is causing MySQL error code 1005. If you are still encountering issues, it may be helpful to consult the MySQL documentation or seek assistance from a knowledgeable database administrator.

Read More articles:

• How to fix SQL Error 1064: You have an error in your SQL syntax
• How to Fix SQL Server Error 207 – Invalid Column Name

The post How to Fix SQL Error 1005: A Comprehensive Guide appeared first on Techyaz.com.

In this article, we will explore what this error means, its possible causes, and provide solutions to fix it.

What is SQL Server Error 207 – Invalid Column Name?

SQL Server error 207 occurs when a column name referenced in a SQL query does not exist in the specified table or view. In other words, SQL Server is unable to find a column with the name mentioned in the query, and as a result, throws the error message “Invalid Column Name.”

Possible Causes

1. Typographical errors: One of the most common causes of error 207 is a typographical error in the SQL query. For example, misspelling a column name, using the wrong case, or forgetting to enclose the column name in square brackets, especially if the column name contains spaces or special characters.
2. Missing or renamed column: Another possible cause of error 207 is that the column may have been deleted or renamed in the table or view, but the query has not been updated accordingly. If a column is dropped or renamed, any queries that reference that column will result in error 207.
3. Scope and visibility of column: The visibility and scope of a column can also cause error 207. If a column is referenced in a query outside of its scope or visibility, SQL Server will not be able to find it, and the error will be thrown.
4. Schema changes: Changes to the schema of a table or view, such as adding, modifying, or deleting columns, can also result in SQL error 207 if the query has not been updated to reflect the changes.
5. Permissions: Another possible cause of SQL error 207 is insufficient permissions. If the user executing the query does not have the necessary permissions to access the column, SQL Server will throw the error.

Fix SQL Error 207

Now that we understand the causes of SQL Server Error 207, let’s explore some solutions to fix this issue:

1. Double-check the column name: The first step in fixing error 207 is to double-check the column name referenced in the SQL query. Make sure it is spelled correctly, using the right case, and enclosed in square brackets if needed. Pay attention to any spaces or special characters in the column name.
2. Verify column existence and visibility: Ensure that the column actually exists in the specified table or view and is visible to the user executing the query. If the column has been deleted or renamed, update the query accordingly.
3. Update the query: If the error is caused by changes to the schema of a table or view, update the query to reflect the changes. For example, if a new column has been added, make sure to include it in the SELECT, INSERT, UPDATE, or DELETE statements as needed.
4. Check permissions: Verify that the user executing the query has the necessary permissions to access the column. Make sure the user has SELECT, INSERT, UPDATE, or DELETE permissions on the table or view that contains the column.
5. Use aliases and table qualifiers: When referencing columns in a query, it is a good practice to use aliases or table qualifiers to avoid ambiguity. For example, instead of just using “SELECT column_name FROM table_name,” use “SELECT t.column_name FROM table_name AS t” or “SELECT table_name.column_name FROM table_name.”
6. Test and debug: After making any changes to the query or schema, always test and debug the query to ensure that the error has been resolved. Use SQL Server tools such as SQL
7. Use Schema Prefix: If you are referencing a table or column that belongs to a specific schema, make sure to include the schema name as a prefix in your SQL query. For example, if you have a table named “Customers” in the “Sales” schema, your query should be something like “SELECT * FROM Sales.Customers” instead of just “SELECT * FROM Customers”.
8. Resolve Ambiguous Column Names: If you encounter an ambiguous column name error, you need to specify which table the column belongs to in your SQL query. You can do this by prefixing the column name with the table name or alias in your query, e.g., “SELECT Orders.OrderID FROM Orders, Customers WHERE Orders.CustomerID = Customers.CustomerID” instead of just “SELECT OrderID FROM Orders, Customers WHERE CustomerID = Customers.CustomerID”.
9. Check Table Existence: Ensure that the table mentioned in your SQL query actually exists in the database. If not, you may need to create the table or correct the table name in your query.
10. Verify Schema Ownership: If you are referencing a table in a different schema, make sure that the schema exists and that you have the necessary permissions to access it. If not, you may need to create the schema or obtain the required permissions.

We learn about fixing SQL Server Error 207 which occurs when a SQL query references a column that does not exist in the specified table or view. This error typically results from a misspelled column name or a reference to a non-existent column in a SELECT, UPDATE, or DELETE statement. When the SQL Server query processor encounters an invalid column name, it raises SQL Error 207 and prevents the execution of the query. You can prevent this issue by following the steps given in this article.

Read More articles:

• How to fix SQL Error 1064: You have an error in your SQL syntax
• SQL Server Interview Questions & Answers on Indexes

The post How to Fix SQL Server Error 207 – Invalid Column Name appeared first on Techyaz.com.

What is SQL Error 1045?

Error 1045 is a MySQL error code that indicates a failed connection to the MySQL database server. The error message associated with SQL Error 1045 typically reads “Access denied for user ‘username’@’localhost’ (using password: YES)” or “Access denied for user ‘username’@’hostname’ (using password: YES)“.

This error occurs when a user attempts to connect to a MySQL database but does not have the proper authorization or has entered incorrect login credentials.

Possible Causes

There are several potential causes for SQL Error 1045, including:

1. Incorrect username or password: One of the most common causes of SQL Error 1045 is entering incorrect login credentials, including the username or password. It is essential to double-check and ensure that the correct username and password are entered when connecting to the MySQL database.
2. Missing or improper privileges: Another possible cause of SQL Error 1045 is the absence of the necessary privileges for the user trying to connect to the MySQL database. If the user does not have the proper privileges, they will be denied access, resulting in the error.
3. Hostname or IP address mismatch: MySQL uses hostnames or IP addresses to identify which hosts are allowed to connect to the database. If the hostname or IP address specified during the connection attempt does not match the one defined in the MySQL configuration, SQL Error 1045 may occur.
4. Firewall or security settings: Firewalls or security settings on the server hosting the MySQL database may block incoming connections, resulting in SQL Error 1045. It is essential to check the server’s firewall and security settings to ensure that they are configured correctly to allow MySQL connections.
5. MySQL server configuration issues: Incorrect configuration settings in the MySQL server can also lead to Error 1045. For example, if the MySQL server is not configured to allow remote connections, users may encounter this error when trying to connect from a remote host.

Fix SQL Error 1045

Fixing SQL Error 1045 requires identifying the root cause of the issue and taking appropriate steps to rectify it. Here are some common solutions to fix Error 1045:

Verify Your Credentials

The first step in resolving SQL Error 1045 is to verify that you are using the correct credentials to connect to your database server. Double-check the username and password you are using in your database connection settings or in your SQL command. Ensure that you are using the correct username and password combination that has the necessary privileges to access the database.

Check for Typos

Sometimes, a simple typo in your username or password can result in SQL Error 1045. Make sure that you have spelled your username and password correctly, paying attention to uppercase and lowercase letters. Also, check for any special characters or spaces that may have been mistakenly included in your credentials.

Grant Sufficient Privileges

If you are still unable to connect to the database and receive SQL Error 1045, it could be due to insufficient privileges for the user account you are using. To fix this, you can grant the necessary privileges to the user account. Log in to your database server as a privileged user, such as the root user, and execute the following SQL command:

GRANT ALL PRIVILEGES ON *.* TO 'username'@'localhost'IDENTIFIED BY 'password';

Replace ‘username’ with the actual username you are using to connect to the database and ‘password’ with the actual password for that user.

This command grants all privileges on all databases and tables to the specified user account when connecting from the localhost. If you are connecting from a remote host, you may need to replace ‘localhost’ with the appropriate hostname or IP address.

Check hostname or IP address

Verify that the hostname or IP address specified during the connection attempt matches the one defined in the MySQL configuration. If necessary, update the MySQL configuration to reflect the correct hostname or IP address

Update Your Password

If you recently changed the password for the user account you are using to connect to the database and forgot to update your connection settings, it could result in SQL Error 1045. In this case, you can simply update the password in your connection settings or in your SQL command to match the new password. If you are using a MySQL or MariaDB command-line client, you can update the password using the following SQL command:

ALTER USER 'username'@'localhost'IDENTIFIED BY 'new_password';

Replace ‘username’ with the actual username you are using and ‘new_password’ with the new password you want to set.

Check for Firewall or Network Issues

Firewall or network issues can sometimes block the connection to the database server and result in Error 1045. Make sure that the port used by your database server (default is 3306 for MySQL and MariaDB) is open in your firewall and that there are no network connectivity issues between your client and the database server.

Reinstall or Reconfigure MySQL or MariaDB

If all else fails and you are still unable to fix SQL Error 1045, you may need to reinstall or reconfigure your MySQL or MariaDB server. This should be done with caution, as it may result in data loss or other unintended consequences. Before proceeding with a reinstallation or reconfiguration, make sure to backup your database and configuration files to prevent any potential data loss.

In conclusion, SQL Error 1045 can be a frustrating issue to encounter when trying to connect to your MySQL or MariaDB database server. However, by following above steps you can fix this issue.

Read More articles on SQL errors:

• Fix the Most Common SQL Syntax Error: SQL Error 1064

The post How to Fix SQL Error 1045: Resolving Access Denied Issues appeared first on Techyaz.com.

SQL Server Error 18456, also known as the “Login failed for user” error, is a common authentication error that occurs when a user fails to log in to SQL Server. The error message associated with Error 18456 usually reads:

“Login failed for user ‘<username>’. (Microsoft SQL Server, Error: 18456)”

The error occurs when SQL Server is unable to authenticate the user trying to connect to the SQL Server instance. There are several reasons why this error may occur, including incorrect login credentials, disabled user accounts, expired passwords, or issues with SQL Server authentication settings.

How to Fix SQL Server Error 18456?

Fixing SQL Error 18456 requires identifying the root cause of the error and applying the appropriate solution. Here are some common solutions to fix SQL Error 18456:

1. Verify Login Credentials: The most basic step in fixing SQL Server Error 18456 is to verify that the login credentials, including the username and password, are correct. Make sure you are entering the correct login credentials for the SQL Server instance you are trying to connect to.
2. Enable Mixed Mode Authentication: SQL Server supports two types of authentication modes – Windows Authentication mode and Mixed Mode (Windows Authentication and SQL Server Authentication) mode. If you are using SQL Server Authentication, make sure that Mixed Mode Authentication is enabled in SQL Server. You can do this through SQL Server Management Studio (SSMS) by right-clicking on the SQL Server instance, selecting Properties, and then navigating to the Security tab.
3. Check User Account Status: Ensure that the user account you are trying to log in with is not disabled or locked out. If the user account is disabled or locked out, unlock or enable the account using SQL Server Management Studio or SQL Server command-line tools.
4. Reset Password: If you suspect that the password for the SQL Server login is incorrect or has expired, reset the password. You can do this through SQL Server Management Studio or by using the ALTER LOGIN statement in SQL Server.
5. Check SQL Server Error Logs: SQL Server logs detailed information about authentication failures in its error logs. Review the SQL Server error logs to identify any specific error messages related to Error 18456. The error logs may provide additional insights into the root cause of the issue.
6. Verify SQL Server Permissions: Ensure that the user account has the necessary permissions to log in to the SQL Server instance. Check the server-level and database-level permissions for the user account and grant the appropriate permissions if necessary.
7. Check Firewall Settings: If you are connecting to a remote SQL Server instance, verify that the appropriate ports are open in the firewall to allow communication between the client and the server. Check the firewall settings on both the client and server machines to ensure that they are not blocking the required ports.
8. Check SQL Server Version: Error 18456 can also occur if there is a version mismatch between the SQL Server client and server components. Ensure that the SQL Server client version matches the server version to avoid compatibility issues.
9. Apply SQL Server Service Packs and Cumulative Updates: Microsoft regularly releases service packs and cumulative updates for SQL Server that address known issues and provide bug fixes.

You can also read the below articles to fix SQL error 18456:

• Fix SQL Error 18456: failed to open the explicitly specified database
• Fix SQL Server Error 18456: Login failed for user ‘User_Name’.
• Fix Error 18452: Login failed. The login is from an untrusted domain

The post How to Fix SQL Server Error 18456: A Comprehensive Guide appeared first on Techyaz.com.

What is SQL Error 1064?

SQL Error 1064 is a syntax error that occurs when you execute an SQL query with incorrect syntax. It’s a common mistake that can happen to anyone, regardless of their level of expertise in SQL or MySQL. The error message typically looks something like this:

“Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘…’ at line …”

Next, we will understand why we get this SQL syntax error and what steps we can take to fix or avoid it.

Fix SQL Syntax Error 1064

This error can be frustrating, but the good news is that it’s usually easy to fix once you identify the cause. Here’s how you can go about fixing SQL Error 1064:

1. Double-check your SQL query: The first step in fixing SQL Error 1064 is to thoroughly review your SQL query. Check for any typographical errors, missing or misplaced keywords, and incorrect syntax. Make sure that all the SQL statements in your query are properly terminated with semicolons, and that you have used the correct quotation marks (single or double) for string literals.
2. Review reserved keywords: MySQL has reserved keywords that have special meanings in SQL queries. If you inadvertently use a reserved keyword as a column or table name in your query without properly escaping it, you may encounter SQL Error 1064. To fix this, either choose a different name for your column or table, or enclose the reserved keyword in backticks (`) to escape it.
3. Check for mismatched parentheses or quotes: Another common cause of SQL Error 1064 is mismatched parentheses or quotes. Make sure that all opening and closing parentheses and quotes in your query are properly balanced. If you have multiple levels of nested parentheses, it’s easy to miss a closing parenthesis, causing a syntax error. Similarly, ensure that all quotes used in your query are properly paired, whether they are single or double quotes.
4. Verify table and column names: Check that you have used the correct table and column names in your query. Make sure that the names are spelled correctly, and that they match the actual names of your database objects. If you are using aliases for table or column names, ensure that they are used consistently throughout your query.
5. Validate data types and values: If you are inserting or updating data in your MySQL database, verify that you are using the correct data types and values for your columns. For example, if you are inserting a string value into a numeric column, or vice versa, you may encounter this SQL Syntax Error 1064. Make sure that the data types of your columns match the values you are trying to insert or update.
6. Use a SQL editor or IDE: Working with a SQL editor or Integrated Development Environment (IDE) can greatly help in identifying syntax errors. These tools often provide syntax highlighting, code completion, and error checking features that can help you spot and fix SQL errors more easily.
7. Consult the MySQL documentation: If you’re still unable to identify the cause of this SQL syntax error, consult the official SQL documentation in case you are using MySQL database. MySQL has extensive documentation that provides comprehensive information on SQL syntax, reserved keywords, data types, and other topics. You can search the documentation for specific keywords or browse through the documentation to learn more about SQL syntax and best practices
8. Test your SQL query: If you are still encountering SQL error 1064, try executing your query in a controlled test environment, such as a local development server or a database sandbox, to isolate and identify the issue. You can also try breaking down your query into smaller parts and testing them individually to identify the specific portion of the query that is causing the error.

If you are unable to fix the SQL error 1064 on your own, you may need to seek assistance from a database administrator (DBA) or a knowledgeable colleague who has experience with SQL queries and SQL syntax errors.

Read More articles:

• How to Prepare for a Job Interview?
• Fix SQL Error 18456: failed to open the explicitly specified database

The post How to fix SQL Error 1064: You have an error in your SQL syntax appeared first on Techyaz.com.

Learn this article to get computer efficiency Tips in case you are less experienced user. As a relatively new computer user, you might find yourself unhappy with how you are using the device. It takes longer to carry out certain tasks than you expect, or the computer is not responding to some of your commands.

Some people can afford to learn things at their own pace, but it does not apply to everyone. For others, it is necessary to master the computer as soon as possible because it is one of the work requirements.

Having a solid foundation is a good approach to overcome this issue. If you were to focus on learning some basic things about computer efficiency and build your experience from there, the process should not take as long.

Remote Usage

Let’s start with using a computer remotely. There may be a time when you are away and want to check something on your laptop. Or, one of your coworkers might ask for access to the computer.

Figuring out how to remote connect to mac or another laptop is not that hard. You will need a tool and a device, such as a smartphone or another computer, that you will be using to access the laptop.

Of course, it is also important to grant access to third-party access to a computer and secure the connection so that it does not get intercepted by an unwanted attack. Keep that in mind.

Keyboard Shortcuts

How well one uses keyboard shortcuts is one of the best ways to determine whether they are good at computer efficiency. Sure, the overall keyboard typing speed is also a good metric, but the more shortcuts someone knows, the more well-versed they are.

The problem for newbies is that if they were to look at the list of available keyboard shortcuts for computers, the sheer number would likely overwhelm them.

Having said that, it is still worthwhile to put your finger memory to use and learn some keyboard shortcuts. Focus on sequences you find the most useful and slowly improve your repertoire from there.

Available Software

It would be a waste not to use the available software. Whether you are on macOS, Windows, or another operating system, there should be plenty of different tools to make your work and overall computer experience better.

For instance, you might be working with emails and outreach, and managing emails manually is too hard. You can incorporate some automation tools to send or respond to emails. Doing so will help you manage email inboxes more efficiently.

Optimal Performance

As a rule of thumb, you will not have a good time on a computer that freezes, crashes, or takes a lot of time to launch and load applications.

Figure out what is causing these problems and determine whether you can solve them yourself. If there is not enough free space on the drive, you can delete redundant files and free it up. If there are too many background processes, quit them and If there is too much desktop clutter, remove shortcuts and documents on the computer’s desktop.

Malware and viruses also need attention. A computer needs antivirus software that can detect and delete threats.

More severe issues, such as beeping noises, overheating, a flickering screen, or error messages should be left to someone who knows what they are doing.

Accessories

Other than mice and keyboards, computers have other great accessories that can come in handy and help you with efficiency.

Those who have a laptop should appreciate a cooling pad to counter the overheating issue. A laptop stand is also worth a shout.

For desktop computers, it might be difficult to create a comfortable setup without a monitor stand. A microphone and webcam could come in handy as well.

Then you have things like computer chairs. Instead of a cheap chair you have right now, purchase one that properly supports your back and makes the overall computer experience that much better.

Hardware

In case you have a somewhat outdated computer with lackluster hardware, you could consider investing some money and getting an upgrade. For example, additional memory or a new GPU would make a significant difference.

Replacing hard drives with solid-state drives is also popular right now. SSDs may not have as much storage as HDDs (not yet, anyway), but they are far superior performance-wise.

Integrated Features

Keep an eye on some integrated features that could make a difference. Some computers and operating systems come with dictation features that let you record a text using your voice instead of typing a keyboard.

Another instance of an integrated feature could be digital signatures on macOS. You can create a signature via Preview and use it in PDF documents. A digital signature saves time when you do not have to sign every document yourself.

The post Seven Computer Efficiency Tips for Less Experienced Users appeared first on Techyaz.com.

Login Failed – Error: 18456, Severity: 14, State: 38

Reason: Failed to Open the Explicitly Specified Database

Fix Error “Failed to Open the Explicitly Specified Database”

The error log is saying “Failed to Open the Explicitly Specified Database“, it means either your have specified wrong database in your connection string or your login does not have access to the specified database. You can validate below options to isolate this issue.

• Check whether you have specified correct database in your connection string or not
• If you are using correct database then whether the login you are using to establish database connection has access to this specified database or not.
• Correct if you find something in any of the above two options.
• Check login properties whether it is using correct database as default database configuration or not. If correct database is defined then login has access to that database or not. I will explain about this step in below section as well.
• You should also check whether number of connections to the database is exhausted or not. Review your maximum number of connections setting.
• Ensure your database is not set to AUTO CLOSE setting or not inaccessible. Database should be online and healthy state to accept connections.
• Make sure you have a trust between both machines, database server and the machine from where you are trying to connect. I would suggest you to read below article as well where i have explained various steps to troubleshoot SQL Server connection issues.

Read more articles on SQL error 18456 and connection issues:

• How to Fix SQL Server Error 18456: A Comprehensive Guide
• How to fix SQL Server error 53 – Not able to open database connection
• Fix SQL Server error 18456 – Login failed for user

Let’s learn how to check default database settings for a SQL Server login and a user mapping for any database to the login.

Check Login Properties

The solution to fix this issue can also come by reviewing the properties of this login. Launch its properties window and change the default database to the correct one if this setting is showing wrong database. Sometimes, we drop the databases from the SQL Server instances but never update other objects. If this login is not showing any database and it is showing blank then click at its drop-down to choose your desired database as the default database for this login. Click on Ok button to apply that change. You will stop getting this issue after making this change.

You can open login properties windows by right click at the identified login and then choose properties from dropdown options.

Sometimes, you have chosen the default database as “master” but your login doesn’t have connect permission on master database so ensure you have at least connect permission on the database which you are choosing as the default database for your login. You can click at “User Mapping” tab from left side pane of the login properties window. You will get all databases in top side of right side pane and level of access in bottom side pane. Click at your database from right side pane along with its level of permission which you want to assign. Click at Ok button to apply this change.

Have a look at below screenshot to understand default database of a login and from where you can access User Mapping tab to provide appropriate access to your database. Your login should have access to both databases, the one mentioned as default database for your login and the specified database in connection strings.

You can fix SQL error “Failed to Open the Explicitly Specified Database” by following above steps. Write your feedback if you have fixed this issue by other way. I will update this article accordingly with credits.

The post Fix SQL Error 18456: failed to open the explicitly specified database appeared first on Techyaz.com.

Most cloud storage services offer a certain amount of free space. Managing iCloud Storage can be rather difficult. On the surface, 5GB that Apple offers for free seems pretty decent, right? Well, user stance changes once they realize that these 5 gigabytes are per account rather than the device.

If you own multiple Apple devices, including a MacBook, iPhone, and iPad, you might run out of available iCloud storage sooner than you expect.

Sure, there is an option to pick a different cloud storage provider in addition to already having iCloud, but managing files on different services can be pretty difficult.

As for signing up for a monthly plan that gives extra storage, that is not a possibility for everyone because not all can afford to pay a fee every month for iCloud storage.

Thankfully, there are ways to manage your iCloud account more efficiently, even if you are stuck with those 5 gigabytes of storage.

Method #1 – Avoid Backing Up Data Too Often

Let’s start with an obvious one—backing up data. Whether you are on your Mac, iPhone, or iPad, you should get in the habit of backing up device files regularly. And since using Time Machine and other backup tools is time-consuming, people are looking for simpler options. And cloud storage is one of these options.

It is also worth mentioning that non-digital data backups require a storage device, such as an external HDD or a USB flash drive. Another reason to use clouds and focus on managing iCloud storage.

So when there are only 5 gigabytes of iCloud storage, backing up the system or individual applications will lead to a lack of storage in no time. If there are important files you want to copy for safekeeping, iCloud is probably not an option unless the number of files is not that large.

Method #2 – Minimize Your Photo Library

It is no secret that taking photos with an iPhone or iPad is popular. Moreover, the picture quality continues to improve with new and improved mobile devices. And as the quality improves, the photo quality increases as well.

Syncing photos with iCloud and transferring them there after you take the photos is a common practice. Over time, the number of photos can grow and take a significant amount of iCloud storage, which makes managing iCloud storage difficult. You also have to consider duplicate photos you might take accidentally.

Method #3 – Delete Old Messages

One would not expect that texts take a lot of space, right? Well, you might be surprised, especially if you are an avid texter who exchanges messages with friends and family often.

It is not just the text itself that requires storage. Attachments, such as photos one includes in a message, are also part of it. Keep it in mind the next time you are about to exchange messages with someone on your iPhone.

Method #4 – Manage Mail Attachments

The Mail app is another example of how a seemingly insignificant application you use on your devices might cause more problems than expected.

If you connect iCloud with Mail, the emails you receive might take a lot of iCloud space—another hindrance for managing iCloud storage properly. But it is not just emails themselves. Attachments are the biggest source of the issue in this case. Be it work emails, spam, exchanges with friends, and newsletters you are subscribed to are just a few examples.

Method #5 – Delete Unnecessary iCloud Junk

If you have been using iCloud for a while, you should take a closer look into your account. Scan through different folders, and you are bound to discover files that are no longer of use to you.

For instance, if you have been keeping information about websites that you want to visit later and wrote the list in a text document, you can simply bookmark pages on your computer’s internet browser instead.

There might be video game save files you forgot about. If you have already finished a video game, keeping these save files makes little sense. If you remove them, it will do good for managing iCloud storage.

Go through the iCloud account thoroughly and remove any files that you deem unnecessary. And when you finish removing the junk, you should notice an increase in the overall free storage.

Method #6 – Transfer Some Files Back to Apple Devices

The last bit of advice is about taking a different approach. Instead of keeping up some files on iCloud, you should transfer certain data to your Apple devices.

It is true that looking at the tips to clean Mac’s or iPhone’s storage, you will find that one of the recommendations is to transfer data to iCloud rather than vice-versa. However, if there is an issue with iCloud storage, you can do the opposite, which should help with managing iCloud storage efficiently.

Most recent MacBooks, iPhones, or iPads have decent storage themselves, so sacrificing a bit of that to not have as much clutter on your iCloud account should not be that much of an issue.

The post Managing iCloud Storage More Efficiently appeared first on Techyaz.com.

Privilege /Secrets maintenance is most crucial requirement in Identity and Access management services. The secrets/passwords are everywhere however in cloud environment these number are 4x times as compares to on premise solution with static secrets. The Secrets could be any form of digital credentials and sensitive information which could lead to breach!

What are Secrets?

A secret can be any sensitive information for e.g.

• User password
• Application and Database and other system-to-system passwords.
• auto-generated passwords /encryption keys
• Private encryption keys
• API Key and other application keys/credentials inside containers
• SSH Keys
• authorization tokens
• Private certificates for secure communication, transmitting and receiving of data (TLS, SSL etc.)
• One-time password devices

Why we need to manage Secrets?

The Secret management is imperative in today scenarios as this has been most affected sector and primary target for any Hackers. The emerging threat in digital environment and highly equipped hackers with self-learning abilities to classify, assess and exploit any vulnerability in the environment

Whether we are using secrets in different cloud services or within a particular cloud-based application, unorganized secrets management procedures can bring serious threat to entire security of platform for example: –

• Hard-coded and default credentials
• Managing passwords manually
• Sharing passwords
• Regular rotations
• Weak password and storing it in plain text files
• Hardcoded and embedded live scripts

Secrets Management Tools

In Cloud security it is imperative that primary focus should be on access control and circulation of dynamic secrets. There are various tools features provided by Cloud service provider and third-party vendors in Market for secret keys management however the most flexible and easy tool trending these days in the cloud industry is Hashicorp Vault. It comes with two products to provide cloud security services the Vault and boundary

Hashicorp is a software company with a Freemium Business Model. They provide various products to fully managed platform to automate infrastructure on any cloud.

The Hashicorp is based on open-source tools and marketable harvests that enable developers, operators, and security experts to secure, run, provision, and connect cloud-computing they basically provide infrastructure as code which is very flexible and mature. The products prevalent for cloud security are secrets management tool Hashicorp Vault and Boundary.

What is HashiCorp Vault?

HashiCorp Vault is a is a secrets management tool for securely accessing secrets. It is used to accomplish secrets keys management in distributed systems across cloud platforms. Vault empowers cloud security players to control access to tokens, passwords, encryption keys, and certificates to defend any potentially sensitive data. The contemporary “zero trust” model is used to harden inside the HashiCorp vault. The Vault can be easily integrated with applications to be explicitly authenticated, authorized to fetch secrets, rotating secrets and perform sensitive operations, along with catering audit requirements.

HashiCorp Vault solution is widely used across many industries including large financial organizations, hospitality, and everything in between to provide security in the cloud operating model.

Secrets Management tool HashiCorp Vault allows steady control access to encryption keys, passwords, certificates etc. for shielding technologies and applications. This delivers an extensive secrets management solution for enterprises looking for securing cloud environment

1– Vault helps protect data at rest and data in transit.

2– Vault exposes a high-level API for cryptography for developers to secure sensitive data without revealing encryption keys.

3- Vault also can act like a certificate authority, to provide dynamic short-lived certificates to secure communications with SSL/TLS.

4- Vault enables a brokering of identity between different platforms, such as AD on premises and AWS IAM to permit applications to work across platform borders. Vaults provide: –

• Storage Backends for Encrypted
• Isolated Namespaces
• Secure plugins
• Detailed Historical Audit logs
• Tenancy, rotating and revoking of secrets

1. Vault provides a master key and generates encryption keys to protect data. The master key is split into five parts. Any three of the five parts are required to reconstruct the master key.

HashiCorp Vault Architecture

The below architectural diagram of secrets management tool HashiCorp vault can explain the workflow of the vault process and services.

• Storage Backend
• Barrier
• Secrets Engine
• Audit Device
• Auth Method
• Client Token
• Token Store
• Root Tokens
• Rollback Manager
• Core
• Audit Broker
• Expiration Manager

Storage Backend – A storage backend is used for robust storage of encrypted data. The storage is placed at bottom of Architecture stack as it is non trusted components for the vault and chosen as per client requirement, the considered factors for the same are like High availability/Disaster recovery/Recovery time Objective. When the Vault is started the storage backend must be declared and configured well in advance.

HTTP API – The HTTP API is used to interact with clients, and it is also non-trusted component for the vault hence placed outside the Barrier

Barrier – The barrier is strong cryptographic components which creates an un-penetrable protection layer around the Vault. The barrier ensures data is validated and decrypted as it goes inside the Vault and all data gets encrypted as it goes out from the vault. The barrier by default stays in sealed state and must be unlocked before requesting any access operation to the vault.

The Unlocking of the vault is possible only using combination of Unseal Keys. When the vault is initialized it generate encryption keys. This key is in turn protected by Master key which gets divided into 5 parts and combination of any 3 keys of which are required to rebuild the master key. For protection purpose all data that flows between Vault and the storage backend passes through the barrier.

Image – Vault Architectures

Secrets Engine – Secrets engines are components which store, generate, or encrypt data. Secret Engine is like virtual file system supporting operations like read, write, delete, generate dynamic credentials, encryptions etc. In Vault when a secrets engine is enabled, a random UUID is generated. This becomes the data root for that engine. As Secret engine writes to the physical storage layer, it is prefixed with that UUID folder as relative access is not supported by the vault hence the secrets engine cannot access other data.

Audit Device – are leveraged to keep comprehensive record of logs for all requests and response inside the vault. As all the operations executed inside the vault are API request and response, thus audit log contains all authenticated communication with Vault, as well all generated errors.

Auth Method – Authentication is used to validate access to vault. The auth method are responsible for conveying identity and a set of policies to a user. Vaults validate a user and returns a client token that can be used for future requests.

Client Token /Vault token– Tokens are the method for authentication within Vault. Token can be generated leveraging authentication methods they can also be used dynamically to generate tokens based on external identities. Inside the Vault tokens record to information like Access control list policies. These policies control directs what access are allowed to the user inside the Vault these tokens also carried meta data which is used for Audit logs such as creation time, last renewal time etc.

Token Store – Are token authentication backend that it is responsible for creating and storing tokens, the token store has no login capability and all actions require existing authenticated tokens.

Root Tokens – are tokens that have the root policy committed to them.

Rollback Manager – This is internal component of Vault to control partial failure cases by using write ahead logging.

Core – The core is used to manage the flow of requests through the system, it enforces Access control Lists and ensure audit logging is done.

Audit Broker – is leveraged to distribute the request out to all the configured audit devices.

Expiration Manager – is used to automatically revokes the secret on Lease expire if allowed by the client

HashiCorp Vaults Pricing

Let’s discuss about Hashicorp vaults pricing. There are 3 options to use this tool from pricing stand point.

1. Open Source
2. Cloud – Managed Vault
3. Enterprise Vault Premium editions.

The Vault Open-source freeware version has limitation of ~50 users only and to leverage all features and functionality it is highly recommended to use Cloud or Enterprise version. You can visit attached link for all Vault Pricing Options.

Conclusion

In this Article we have covered What are Secrets? Why we need Secrets Management? and Secrets Management tool offered by Hashicorp Vault. There are several other tools available for secrets management in the market as mentioned below. As per the client requirement and existing infrastructure we can propose appropriate tools to our clients as long it serves the purpose of underline security with future integration possibilities

• Conjur Secrets Manager (Open Source) – CyberArk
• Dynamic Access Provider (DAP) Enterprise – CyberArk
• AWS Secrets Manager – Rotate, manage, and retrieve database credentials, API keys, and other secrets through their lifecycle
• Azure Key Vault – securely storing and accessing secrets
• Akeyless Vault for Secrets Management and Secure Remote Access
• Docker secrets management

The Security trend seen in last 5 years has shown paradigm shift towards Identify and Access management domain. IAM plays vital role in preventing Cyberattacks due to leak credentials and hence many organizations are moving towards taking proactive steps by adding more secrets tools and technology to protect their sensitive information. As these organization moves towards more flexible, scalable, secure and cloud agnostic environment.

The Hashicorp suits of products are outstanding in terms of ease of use, integration, and configurations. The can flawlessly assimilates with all offerings of major cloud vendors. The Hashicorp products carry solution to full scale infrastructure security management.

For the next topics we will cover about other HashiCorp product in security and its comparison to Other traditional Privilege Access Management tools in the market. Stay tuned for upcoming topics on Boundary and CyberArk PAM solution offerings.

Related Articles:

• Understanding Cloud Security & Data Protection
• Cloud Security – How to Secure Cloud Environment?
• Top 5 Cloud Service Provider Accreditations and Third-Party Auditor Reports

The post Cloud Secrets Management Tool – HashiCorp Vault appeared first on Techyaz.com.

A connection timeout has occurred on a previously established connection to availability replica ‘manvendradbggp03’ with id [availability group id]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.

You may also receive similar issue under different alwayson error 35201. Below error will generate while attempting to establish the connection to availability group but failed because of connection timeout error 35206. The error text of this SQL error 35201 is given below.

A connection timeout has occurred while attempting to establish a connection to availability replica ‘manvendradbggp03’ with id [availability group id]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.

If you are always getting above issues and unable to establish any connection to its respective availability replica then you should immediately look in to network side whether there is poor network latency, any network packet drop issue or firewall is blocking some connections or not as suggested in error code. But if you are getting this issue on intermittent basis then you should keep reading this article to understand more about alwayson error 35206.

SQL Server Error 35206 and Error 35201 in Always on

Both errors come because of connection timeout error between their respective replicas. Microsoft has categorized these errors as product issue and released cumulative updates to fix them. You should also consider these cumulative updates as per your SQL Server version. These issues will be very problematic if you will not address them on time because of below reasons:

• Availability databases will stop synchronizing. This could be a risk of potential data loss.
• Log file will start growing on your primary replica. This could be a potential risk for an outage if we will not address this issue on time.
• Frequent repetitive alerts for your critical systems

You must fix this issue by applying the cumulative update to avoid above problematic scenarios. But if you already have applied these updates and are still facing these issues then i would recommend you to read below section to try out other options.

Fix Always on Connection Timeout SQL Error 35206

Generally, this problem encounters only on high end systems where you have more than 24 cores CPU and SQL Server is highly transactional. One very simple workaround to overcome this issue is to restart SQL Server service on your secondary replica where you are getting this issue. Don’t restart SQL Server on primary replica. Restarting SQL Server on impacted availability replica will surely fix the issue for the time being.

Additionally, you should consider below checks to review and make changes accordingly as per your system design if you are still getting this issue on frequent basis.

Use Default Network Packet Size

Review network packet size configuration in SQL Server. Microsoft suggested to keep network packet size configuration with default value but sometime we make changes as per our need and forgot to revert these changes to their original values so i would recommend to revert this change to its default value. Read below article if you want to learn how to change network packet size configuration in SQL Server.

• How to Change Network Packet Size in SQL Server?

You should also consider evaluating your network bandwidth and firewall settings to make sure and isolate the issue. I would suggest you to work with network engineer on this front to review network or firewall related configurations.

Review Connection Timeout Setting

Another option i would recommend you to evaluate and review the session or connection time out settings. Make sure that session timeout setting for your always on configuration must be more than or equal to 10 seconds. You can consider increasing session time out if you have slow network between your replicas. Although if you are running highly transactional databases on high end box i assume you already have good network bandwidth but nothing wrong in reviewing the settings. Read below article if you want to reconfigure or change session time out in always on availability group.

• How to Change Session Timeout in Always on Availability Group Configuration?

If you are running your always on availability group configuration between multi subnet environment then i would recommend you to read attached Microsoft article to fix connection timeout errors in multi subnet availability groups.

Read More:

• Fix SQL Server Error 976: Cannot connect to Secondary Replica of AlwaysON Availability Group
• SQL Server Alwayson Error 35250: Joining database on Secondary Replica resulted in an error
• Fix SQL Server Error 19471: Listener issue that came during Configuring SQL Server AlwaysOn Availability Group
• SQL Server Alwayson Interview Questions & Answers

The post Fix Always ON Connection Timeout Error 35206 in SQL Server appeared first on Techyaz.com.

The connection timeout setting in AOAG applies only to identified secondary replica and its respective primary replica. Each secondary replica has its different session timeout value which works between the given replica and its primary replica. The default value for session timeout configuration is 10 seconds. Microsoft recommends to keep this setting value to 10 seconds or more to prevent system missing pings and false failure alerts.

Change Session Timeout for Availability Replica

This section will explain how to change or modify connection or session timeout value for an AOAG availability replica. This is needed sometimes if you are frequently getting connection timeout errors for your availability replicas. I will show two ways to modify session timeout in always on availability group. One is by using SQL Server Management Studio and another one by using T-SQL statement.

Modify Alwayson Connection Timeout using SQL Server Management Studio

Make sure you have connected to your SQL Server Instance which is hosting primary replica of always on availability group configuration. Follow below steps to change session timeout or connection timeout for identified availability replica where you are facing connection timeout errors 35206 or 35201.

• Launch SQL Server Management Studio and connect to the primary replica
• Expand folders once you connected to the primary replica instance. Click at plus sign to expand Always on High Availability node followed by Availability Groups node.
• Identify and click the availability group for which you have to configure connection timeout for one of its availability replica
• Identify the availability replica for which you have to change this value. Right click at this replica and click at Properties option to launch its properties page
• You can see Session timeout (seconds) option In the Availability Replica Properties dialog box. Use Session timeout (seconds) option to change the number of seconds for the session timeout period on this replica. Always keep it 10 or more as per your specific need.

We have successfully changed alwayson connection timeout for an availability replica using SQL Server management studio in above steps. Now, i will show you T-SQL approach to get this done in below section.

Change Alwayson Connection Timeout using T-SQL Statement

Here, i will show you how to change session timeout for an availability replica using T-SQL statement.

• Launch SQL Server Management Studio and connect to the primary replica.
• Open New Query window and run below ALTER AVAILABILITY GROUP statement.

ALTER AVAILABILITY GROUP group_name

MODIFY REPLICA ON ‘instance_name‘ WITH ( SESSION_TIMEOUT =seconds )

Make sure to replace group_name with your availability group name, instance_name with your secondary replica name for which you want to change session timeout value and seconds with appropriate time in seconds.

Once you will execute above statement, connection timeout value will change as per your specified value for your availability replica. Now, you can go ahead and monitor the connection timeout errors to see whether your issue has been fixed or not.

Here, i have explained how to modify or change session timeout for an always on availability group replica.

Read More:

• SQL Server Alwayson Interview Questions & Answers
• SQL Server Alwayson Error 35250: Joining database on Secondary Replica resulted in an error
• Understanding Backup Preferences for AlwaysOn Availability Group Databases

The post How to Change Session Timeout for Availability Group Replica appeared first on Techyaz.com.

Get Values between Two Dates using SQL BETWEEN

Let’s say you have a requirement to get all values between two date ranges or specific date time ranges. You can use SQL BETWEEN operator to get this done. Here is the example to get all values between date 19th March 2021 and 20th March 2021. Below example is also an use case of how to use BETWEEN operator in WHERE clause. You can remove ‘-‘ from date ranges if you want and you can directly mention date ranges as ‘20210319’ AND ‘20210320’.

SELECT name, type_desc,create_date, modify_date
FROM sys.objects
WHERE modify_date BETWEEN ‘2021-03-19’ AND ‘2021-03-20’

Here, i have fetched all modified objects on my SQL Server between given date range. Here is the output. We can see there are more than 730 rows returned. You can compare the dates in modify_date column whether output has returned correct data or not.

Now, Next requirement could be to retrieve some data between two date time ranges like you want details between specific time of dates. I will take same above query to show case this example as well. When we don’t specify the time along with date range then it defaults to 12:00 A.M. 

SELECT name, type_desc,create_date, modify_date
FROM sys.objects
WHERE modify_date BETWEEN ‘2021-03-19 4:38:00’ AND ‘2021-03-19 4:38:30’

Here, i have retrieved all modified objects between 30 seconds of above given time (Time 4:38:00 to 4:38:30). Here is the output and it is showing only 35 rows.

You can use this SQL between two date ranges or datetime ranges to fetch your data. You can use this operator in INSERT, UPDATE or DELETE statements as well.

Get Values between Two Numbers

This section will explain about getting details between two number ranges. Let me take same table which we have taken for above section sys.objects. Now, i want to get all objects having object id between 25 to 30 or you can mention any range. This is just an example to showcase. These number ranges will change as per your need and nature of data.

SELECT name, object_id, type_desc, create_date
FROM sys.objects
WHERE object_id BETWEEN ’25’ AND ’30’

Note, above object_id is column name and not the T-SQL function. Have a look at its output in below image. We have got only rows which are assigned with these object ids.

Use BETWEEN with NOT Operator

Above all examples shows how to get data between two ranges but we can use NOT operator with BETWEEN to return all values which is not between specified two ranges. Let’s take above example where BETWEEN operator has returned only 5 rows based on their specified two ranges. Now if i will use NOT operator in above T-SQL statement then output will return all rows of table sys.objects except above 4 rows which will be prevented by NOT operator. Let me show you this example.

SELECT name, object_id, type_desc, create_date
FROM sys.objects
WHERE object_id NOT BETWEEN ’25’ AND ’30’

Have a look at below highlighted are where objects ids between 25 to 30 are missing.

Here, i have shown you few use cases of SQL Server T-SQL operator BETWEEN statement. You can go head and try this operator for your business needs. For more information on this operator, visit MSDN article.

Read More

• Fix:VIEW SERVER STATE permission was denied on object ‘server’, database ‘master’
• Difference between UNION and UNION ALL T-SQL Operators
• SQL Server Interview Questions & Answers on Indexes

The post Learn How to use SQL Server BETWEEN Operator appeared first on Techyaz.com.

Azure Data Studio is cross-platform database management tool to manage on prem as well as cloud based SQL Server deployments on windows, Linux and MacOS platforms. This tool offers a modern editor experience with IntelliSense, code snippets, source control integration, and an integrated terminal.

When you launch Azure Data Studio first time, it will show you a popup window and ask you to enable the preview features. You can choose “Yes” to use preview features and “No” to disable this feature. If this settings is disabled in your Azure Data studio then you can enable it anytime by accessing settings tab given bottom left of the Azure Data Studio screen. Below is the list of preview features for SQL Server in Azure Data Studio.

• Azure portal integration
• SQL Server Backup and Restore
• Deployments of SQL Edge, SQL Server Big Data Cluster, SQL Server container image & SQL Server on Windows
• SQLCMD mode
• Admin Pack for SQL Server
• Azure Synapse Analytics Insights
• Central Management Servers
• Database Administration Tool Extensions for Windows
• Kusto
• Language packs
• PostgreSQL
• PowerShell
• Query History
• SandDance for Azure Data Studio
• Server Reports
• SQL Assessment
• SQL Server Agent
• SQL Server Profiler
• Machine Learning
• Managed Instance Dashboard
• Visual Studio IntelliCode
• whoisactive

Above list is not limited to only given features. I was restoring a database using Azure Data Studio. When i tried to click at restore button, another popup window came and suggested to enable preview features for this restore as shown in below image. When you try to preform any above activity in Azure Data studio, you will get similar popup window.

I will show you step by step process to enable or disable preview feature in Azure Data Studio.

Enable Preview Features

I was trying to perform a database restore using Azure Data Studio and got a popup which was saying ” You must enable preview features in order to use restore “. Follow below steps to get it done.

• Launch Azure Data Studio
• Click at the setting button given bottom left of the screen, then again click at the setting options from displayed menu.

• Type Enable Preview Features from search bar given on the screen.
• You will get few options in drop down. Click at checkbox for Enable unreleased preview features under Workbench: Enable Preview Features.

• This change will automatically been saved in Azure Data Studio.

Now, you are good to go ahead and use all features which are in preview as per your need.

Disable Preview Features

Disabling preview features in Azure Data Studio is similar to above steps. You just need to uncheck the checkbox which you have checked in above step. Follow below steps to get it disabled.

• Launch Azure Data Studio
• Click at the setting button given bottom left of the screen. You will get a list of options from which you need to click at the settings options again.
• Type “Enable Preview Features” from search bar given on the screen.
• You will get few options in drop down. Uncheck the checkbox for Enable unreleased preview features
• This change will automatically been saved in Azure Data Studio.

You have learnt preview features enablement and how to disable it in Azure Data Studio.

Read More Articles:

• Cloud Security – How to Secure Cloud Environment?
• SQL Server Interview Questions & Answers on Indexes
• How to Learn Cloud Computing?
• What is Cloud Computing

The post How to Enable Preview Features in Azure Data Studio appeared first on Techyaz.com.

A transport-level error has occured when receiving results from the server. (provider: TCP Provider, error: 0 – The semaphore timeout period has expired.) (Microsoft SQL Server, Error:121)

This was an intermittent issue and when we were executing the script from other server it was not throwing any issue. I did some research on this and found out that this error came because of unstable network connectivity.

SQL Server Error 121 The Semaphore Timeout Period Has Expired – Root Cause

There are various parameters that can affect network connectivity like network adaptors, packet drop, configured packet size etc. So i would suggest first you should connect to your network team and ask them to look into this issue. If network team has not found anything then you need to check application level network configurations at your level.

You should ask some questions to your network resource like whether any network packet drop being observed or not, or is there any NIC card issue etc. Let’s assume you have already reached out to network team and they haven’t found anything. I would suggest you to look into below options at your level to make sure everything is in place and not misconfigured.

• Check TCP\IP settings
• Ensure you have appropriate network packet size configured in SQL Server
• Make sure you have properly configured TCP Chimney Offload
• Validate you don’t have Network Interface Card (NIC) driver issue, you can get it checked with your network team

Solution

I have already described high level areas where you need to look in in above section. Let’s discuss them further here.

Check TCP\IP settings

You should open SQL Server configuration manager and check whether TCP configuration is properly done or not. Make sure to review all settings in SQL Server Network configuration settings. You should also read below article about this settings which causes a network error.

• Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol

Review Network Packet Size

You should also review network packet size configuration in SQL Server. This could be one of the possible reason for this issue. Ideally we should not change the default value of this setting and keep it as it is until you have a specific requirement to change network packet size. Read below article to understand and learn network packet size in SQL Server and also step by step process about how to change the network packet size to your desired value.

• How to Change Network Packet Size Configuration in SQL Server

TCP Chimney Offload

This settings is very important if we have network related connectivity issue. TCP Chimney Offload is a networking technology that helps transfer the workload from the CPU to a network adapter during network data transfer. It can be enabled or disabled in the following two locations:

• The operating system
• The advanced properties page of the network adapter

TCP Chimney Offload will work only if it is enabled in both locations. By default, TCP Chimney Offload is disabled in both these locations. However, OEM installations may enable TCP Chimney Offload in the operating system, in the network adapter, or in both the operating system and the network adapter.

Validate Network related Driver Issues

You should speak to your network resource and Windows OS platform resource and validate all drivers at OS layer and network layer should be up to date and they should not have any issue. Make sure to update the drivers if you found any issue any of these layer.

I hope you can fix your issue by following above steps mentioned in this article. Comment us how you have fixed this issue, the semaphore timeout period has expired.) (Microsoft SQL Server, Error:121)

Related Articles

• SQL Server Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server.
• Fix Error 1418: The server network address cannot be reached or does not exist.
• Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol
• SQL Server Native Client Error 50000: A network error occurred while attempting to read from the file

The post Fix SQL Server Error 121 – The Semaphore Timeout Period Has Expired appeared first on Techyaz.com.

• Mixed Mode ( Windows +SQL Server login )
• Windows Mode (Only Windows)

Mixed mode provides two ways to establish database connections. One is using SQL Server logins at SQL Server layer and another one is using Windows domain user authenticated using active directory and whose login is created and mapped on SQL Server instance.

Windows Mode has only one way to establish database connections and that is using windows domain accounts. We must map windows accounts on SQL Server first before making any database connections. This mode doesn’t provide access to SQL Server logins.

Read More to Grow:

• SQL Server Interview Questions & Answers on Indexes
• How to Prepare for a Job Interview?
• SQL Server Alwayson Interview Questions & Answers
• SQL Server Replication Interview Questions & Answers

Why Windows Authentication Mode is More Secure in SQL Server?

Windows mode is secure than Mixed mode authentication because mixed mode has SQL Server authentication which cannot use Kerberos security protocol. Windows account needs to be authenticated to domain active directory every time you establish a database connection. Also, Windows provides additional password policies that are not available for SQL Server logins and that is why Microsoft always recommends to use Windows authentication mode wherever it’s possible.

One more risk with Mixed mode is the encrypted SQL Server Authentication login password must be passed over the network at the time of the connection. Some applications that connect automatically will store the password at the client. These are additional attack points.

Change Authentication Mode in SQL Server

You can configure authentication mode in SQL Server during installing it to your system. SQL Server installation windows will allow you to choose any one of above given authentication modes. If you will choose mixed authentication mode then you need to provide sa password as per windows password policy. You can also change existing authentication mode setting to another one as per your business need.

Let’s assume you have installed SQL Server with Mixed authentication mode and now you have to change it to Windows Authentication mode. This section will explain step by step process to change SQL Server authentication mode.

We can set or change authentication mode in SQL Server either using SQL Server management studio or using T-SQL statements.

Using SQL Server Management Studio

1. Launch SQL Server Management Studio, connect to your target SQL Server instance.
2. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
3. On the Security page, under Server authentication, you can see both authentication modes. Select any as per your need and then click OK.
4. This change will require SQL Server service restart. A popup window will appear to ask you to restart the service when you will click at OK button in above step.
5. In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted.

You have changed your authentication mode from Mixed mode to Windows using SQL Server Management Studio.

If you are changing authentication mode from Windows to Mixed mode then make sure to enable SQL Server login sa account. This account gets disabled during windows authentication mode to secure your SQL Server instance as sa is generic SQL Server login as it can be targeted by hackers to access your instance. Below are the steps to enable this account:

1. In Object Explorer, expand Security, expand Logins, right-click sa, and then click Properties.
2. On the General page, you might have to create and confirm a password for the sa login.
3. On the Status page, in the Login section, click Enabled, and then click OK.

Using T-SQL Statement

Microsoft has provided an extended stored procedure to chnage authenication mode in SQL Server using T-SQL statement. This extended stored procedure chnages windows registry entries so be careful while changing authentication mode in SQL Server using T-SQL statements. Make sure to take a backup of windows registry before executing this script.

USE [master]
GO
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'LoginMode', REG_DWORD, 1
GO

Above command has again changed authenticating mode from mixed to windows.

If you are doing other way around then make sure to enable sa login as i suggested above. You can also use below T-SQL statement to enable sa account.

ALTER LOGIN sa ENABLE ;
GO
ALTER LOGIN sa WITH PASSWORD = 'STRONG-PASSWORD' ;
GO

Here, i have explained how to change SQL Server authentication mode from Windows to Mixed mode or vice versa. Please comment us if you have any feedback on this article.

Related Articles:

• Fix SQL Server Error 18456: Login failed for user ‘User_Name’.
• How to Change SQL Server Instance Name?
• Create a Logon Trigger to Restrict sysadmin logins to connect to SQL Server for given Time Interval
• Fix Error 18452: Login failed. The login is from an untrusted domain

The post How to Change Authentication Mode in SQL Server? appeared first on Techyaz.com.