Sor Ser Rus BongAbb Oy Luy Tip Douch Knea by Sasa

When I text you, It's mean I miss you. When i don't text you, it's mean I am waiting for you to miss me

Step Guide To Install SQL Server 2008 In Window

First double click on the setup.exe file.
After a few seconds a dialog box appears:

This will disappear from the screen and then the main installation page appears:

STEP 1 : SQL Server Installation Center
Click on the Installation hyperlink on the left hand side of the screen:

STEP 2 : SQL Server Installation Center
Click on the “New Server stand-alone installation” link on the right side of the screen:

The following dialog appears on the screen whilst the install program prepares for installation:

After a minute or so (the timing will vary according to your system), the following screen appears:

STEP 3 (optional) :
If any checks have failed, click on the Show details button or “View detailed report link” to find out the cause, correct it, then click on the Re-run button to perform the checks again.
STEP 4 : Product key
If all checks have passed, click on the OK button. After a few moments, the option to select the edition and to enter the license key (or “product key”) will appear. Note that the product key box may already be populated, depending on which edition you have. Don’t enter the product key we’ve shown here, it won’t work on your system!:

STEP 5 : License Terms
Enter the product key into the box, or choose the free edition if you’re evaluating SQL Server 2008, and click on the Next button:
Click in the “I accept the license terms” check box, then click on the Next button again.
STEP 6 : Setup Support Files
The following screen appears; click on the Install button:

The following screen will appear whilst Windows Installer prepares itself for the installation. This will take a short while:

After 30 seconds or so the dialog appears again:

STEP 7 : Setup Support Rules
If all is well, the following screen appears:

Click on the Next button again.
STEP 8 : Feature Selection
Select the features you want to install.
At a minimum, the following are useful (I’d argue essential), but what you need will depend on your needs:

Click on the Next button.
STEP 9 : Instance Configuration
After a short while the following screen appears:

For most installations, keep the default settings.
Click on the Next button.
STEP 10 : Disk Space Requirements
This screen just tells you if you have sufficient disk space on the drive you’re installing to, and what’s going to be installed where.

Click on Next.
STEP 11 : Server Configuration
This step allows you to set up the service accounts that will be used to run SQL Server. If you have created Windows NT or Active Directory accounts for use with services, use these.
If not, then just to get the installation up and working, use the built-in Network Service account for all three services listed (this account does not require a password).
This allows SQL Server to start up after installation. However, it can be easily changed later to another account through the Services applet (Control Panel -> Administrator Tools -> Services):

In addition, remember to change the Startup Type to Automatic, for all three services. This automatically starts the SQL Server database engine, SQL Agent and SQL Browser services when the server is re-booted.
The first service runs the SQL Server database engines executable process. The other two services allow scheduled jobs to run after installation (and after a re-boot), and allow the SQL Server to be found by clients on the network.
Do not worry about changing the collation tab, unless there is a specific requirement for anything other than the default collation sequence. Finally, click on Next.
STEP 12 : Database Engine Configuration – Account Provision
This screen allows you to set up database engine security.

Change the Authentication Mode to Mixed Mode unless you are certain you only need Windows-only authentication.

• Many third party applications rely on SQL Server logins to operate correctly, so if you are setting up a server for a third party application, rather than one developed in-house, enabling Mixed Mode authentication is a good idea.

If you pick Mixed Mode security, you must also enter a password for the sysadmin account (sa).
Enter and confirm a secure password for the sa account and keep it somewhere safe. Do not give it to any one you do not want to have access to the SQL Server.
Note that you MUST also provide a Windows NT account on the local machine as a SQL Server administrator. If you do not want Windows system administrators to be able walk up to the box and login to SQL Server, create a new, local, dummy Windows user and add this account instead. Otherwise, add in the local administrator account, or your own Windows account on the domain in which the SQL Server will reside.
STEP 13 : Database Engine Configuration – Data Directories
Click on the Data Directories tab.

Change the directories to specify which drives in your system will be used for the various types of database files.
Generally it’s advisable to put the User database directory and User log directory on separate physical drives for performance, but it will depend on how Windows has been configured and how many disk drives you have available.
If you are installing on a single drive laptop or desktop, then simply specify:

Data root directory	C:\Program Files\Microsoft SQL Server
User database directory	C:\Data
User log directory	C:\Logs
Temp DB directory	C:\TempDB
Temp Log directory	C:\TempDB
Backup directory	C:\Backups

Do not click on the FILESTREAM tab unless you know you need to change these options, as it is not generally required for most installations, but can easily be changed by using sp_configure ‘filestream_access_level’, ”after SQL Server has been installed. Click on Next.
STEP 14 : Error Usage Reporting
This screen simply asks if you want to send error information to Microsoft and can safely be skipped if you do not want to share any information.

Click boxes if you want to help Microsoft help you.
Click on Next again…
STEP 15 : Installation Rules
This screen simply checks if there are any processes or other installations running which will stop the installation of SQL Server 2008.

Click on Next again – you’re almost ready to install:
STEP 16 : Ready to Install
This screen summarises what you are about to install and gives you a last chance to cancel or change anything that’s wrongly configured:

Check that what’s being installed is what you want and then click on Install when you’re sure you want to start the installation process:
Installation Progress
SQL Server 2008 will now install. How long it takes depends on the speed of your machine, what load it’s under, the installation media (CD is slower) and what you’ve chosen to install.

…More Installation Progress

… and Finally
Finally, the installation will complete:

…and the following dialog box will appear:

Click on OK, the machine will NOT reboot.
The following will appear:

…followed by:

Click on the Next button again…
STEP 17 : Installation Complete
The following screen appears:

It may be worth clicking on the installation log at the top of the screen to check everything’s gone as expected. Not that this is MUCH smaller than the usual SQL Server installation log files of old.
Finally, click on the Close button. The following dialog will appear:

Click on OK – your server will NOT re-boot at this point.
The dialog box will disappear and you will be returned to the Installation Center:

Click on the Close button (the “x”) in the top right of the screen.
Finally, manually reboot your machine to complete the SQL Server 2008 installation.
This is way to check you SQL Server is has been completed success installation

How to check that SQL Server 2008 has installed correctly

Here are a short number of post-installation checks which are useful to perform after re-booting your new SQL Server. You don’t have to run these, and there are other ways to check, but they are very useful for non-DBAs to be sure that the installation is basically sound and a connection can be made to the new SQL Server before handing it over to someone else.
Check 1: Has the SQL Server Service Started?
Check SQL Server 2008 has started.

Check 2: Does Management Studio Work?
Check Management Studio works by firing it up.


Click on NO when you see this dialog box:


Check 3: Can you run a basic query against the new SQL Server?
Check SQL Server works by running a simple query from Management Studio:

Enter the query shown below and hit F5 to run it:

Check 4: Is SQL Server Agent Running?
Check SQL Server Agent is running for scheduled jobs. There should be a green arrow next to the SQL Server Agent database symbol (it’s small, you might have to look hard):

Check 5: Can SQL Server be seen from the Network?
Check that the new SQL Server can be seen from another SQL Server on the same domain by running isql –L (or osql –L):
If you can’t see the new SQL Server in this list, check that the SQL Server Browser service is started on the machine where you have just installed SQL Server.
Check 6: Has the TCP/IP network protocol library been enabled on the server?
If the browser service is started but you still cannot connect to the server, click on Start ->Programs -> SQL Server 2008 -> SQL Server Configuration Manager (on the server where SQL Server’s just been installed)

The SQL Server Configuration Manager window opens.
Click on the SQL Server Network Configuration node and expand it.
In the example below, we have MSSQLSERVER (a base instance of SQL Server), and SQLEXPRESS showing as installed.
If in doubt, click on Protocols for MSSQLSERVER.

In the above screenshot, the TCP/IP network protocol library is disabled. We need to enable it in order that remote servers can talk to the newly installed SQL Server.

• A word of explanation : In most installations, Named Pipes can be ignored, unless there is a requirement for it. In virtually all environments, VIA can also be ignored as this protocol requires a special network card. Shared memory is the “local” protocol that SQL Server uses when talking to a client application on the same server as itself, for example when SQL Server Management Studio connects to it. It is usually best to leave this enabled.

You will need the TCP/IP protocol enabled if you need to connect to your new SQL Server from a remote client or another server via TCP/IP, which is what most networks use.
If it shows as DISABLED (above), double click on the TCP/IP protocol line, and the following window will appear:

Ensure that Enabled is set to Yes, and click on OK.
The following warning will appear:

Click on OK, and you will be returned to the Configuration Manager window, where TCP/IP will now be shown as enabled:

Go back to the Services applet, and re-start the MSSQLSERVER service so that the TCP/IP protocol can be used to connect to your new SQL Server.
Then try to connect to it again from a remote machine.
If you have experienced problems with the previous connectivity tests, you should now be able to repeat at least some of them successfully.

Message dialog: is not a valid login or you do not have permission | MS SQL Server 2008 Expressis not a valid login or you do not have permission

While I have to install was MS SQL Server 2008  Express. But something was wrong, every time I tried to install SQL Server 2008 express I had the same error message is not a valid login or you do not have permission.




This error message was meaningful, because I installed it using my account with has administrator access.
I tried to remove and reinstall SQL Server, I tried different versions of SQL Server, but nothing helped.
But finally I found a solution how to avoid this error message is not a valid login or you do not have permission
By default godaddy virtual server has the same name as user account and this was the reason of error message.
I renamed my server and error disappeared and I was able to install SQL Server Express without errors.
Hop this post can help you.

Resolving yellow WAMP server status

Update: Using XAMP

After I’ve written this blog post I’ve figured out that XAMP, although very similar to WAMP, doesn’t force you to run Apache as a service, instead it can run it as a regular process. So I ended up using XAMP, and changed Apache port to 8080 so now everything works.

WAMP Issues

If you have Window 7 or later you may have come across issues with WAMP server trying to start Apache service on port 80 and failing.
There are many conflict and issues that might have come up.
Before you try anything, check if you have ZoneAlarm, Nod32, or any other program/firewall that might be blocking Apache server.
If you’re sure that firewall isn’t the problem here is a couple of fixes that you can try.
NOTE: After every fix you try, you must click on yellow WAMP icon and choose Restart All Services

Checking which process is causing the problem

• Open Command Prompt window by typing cmd in Run command box or Start Search, and hit Enter.
• Type in the following command:

netstat -o -n -a | findstr 0.0:80

The last column of each row is the process identified (process ID or PID).

• Identify which process or application is using the port by matching the PID against PID number in Task Manager.
• If you don’t see PID column in your Task Manager you need to go to Processes tab -> View Menu -> Select Columns and choose PID from the list
• Now, you may have identified application that reserves port 80, or you may have found out that System is using your port 80. That means that one of internal services is using your port, in which case continue reading further.

Conflict with Skype

If you found out that Skype is using your port 80, you need to change some settings in Skype. On Windows, Skype reserves port 80 which is used for HTTP. Apache requires this port. So if you’re running Skype, you must go to Tools > Options. Then in the Advanced section, select Connection. Un-check the box that says “Use port 80 and 443 as alternatives for incoming connection“. Quit Skype and restart. The issue should be resolved.

Conflict with IIS Server

IIS Server and Apache are both web server that use port 80 so they might be in conflict. Try stopping IIS by:

• Going into Control Panel -> Administrative Tools -> Internet Information Services
• Right click on Default Web Site
• Click on Stop option in the popup menu, and see of the listener on port 80 has cleared.

Conflict with MS SQL Server

MS SQL Server installs “SQL Server Reporting Services (MSSQLSERVER)” that apparently defaults to 80. You can try stopping it to free up port 80.

• Go to Control Panel -> Administrative Tools -> Services
• There find MSSQLSERVER (might be found also under SQL Server)
• Double click it -> Click Stop
• Under Startup type: choose Manual

Other Services that can cause conflicts

As described above for MS SQL Server:

• Go to Control Panel -> Administrative Tools -> Services
• You can try stopping:
  • Web Deployment Agent Service
  • Windows Remote Management
  • Autodesk EDM Server
  • World Wide Web Publishing Service

There are probably more of them, but this where the ones that I tryed.

Try turning off HTTP driver directly

If you’ve tried everything mentioned above and your WAMP server is still not working you could try this (which eventually helped me).

• Right click on My Computer icon -> Properties
• Go to Device Manager
• Click on View menu and chooseShow hidden devices
• Now from the list choose Non-Plug and Play devices
• Double click HTTP -> go to Driver
• For Type choose Disabled
• Restart your computer

After your computer boots up you should be able to start up WAMP server.

If everything else fails

You could try changing Apache server to listen to some other port other than port 80.

• Click on yellow WAMP icon in your taskbar
• Choose Apache -> httpd.conf

Inside find these two lines of code:

Listen 80

ServerName localhost:80

and change them to something like this (they are not one next to the other):

Listen 8080

ServerName localhost:8080

Restart all services, and try typing localhost:8080 into your browser.
WAMP server should now be working.

5 positive thooughts ,Education Qu...

Crystal Reports for Visual Studio 2012

Environment

1. Support integration with Visual Studio 2012 and 4.5 .NET Framework runtime.
2. Added support for following platforms:
   • OS: Windows 7 SP1, Windows 8, Windows 2012
   • Database: SQL Server 2012, HANA SP5
   • Web Browser: Firefox 16, IE10 (limited support; more information forthcoming soon)
   • Other technology: IIS 8, Flash 11
   Download here

Hope it can help you .

Tom and Jerry Funny Movie Full Movie 2013