How to let sql server 2008 know the table created at front end in c#
How to let sql server 2008 know the table created at front end in c#
The best solution is to create table type and pass the DataTable as table-valued parameter. I have an article on my web site about this:
http://www.sommarskog.se/arrays-in-sql-2008.html
The full article is a bit of overkill for what you are doing right now, but just the few first pages should get you going.
Erland Sommarskog, SQL Server MVP, [email protected]
Similar Messages
-
How to install SQL SERVER 2008 r2 in window 7 home premimum 64bit
how to install SQL SERVER 2008 r2 in home premimum 64bit os. can any say that weather it will support or not in window 7 home premimum os.
my server log file:
Final result: SQL Server installation failed.
To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052700
Exit facility code: 1212
Exit error code: 1316
Exit message: SQL Server installation
failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-27 00:52:25
End time: 2014-03-27
00:56:09
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name: SEVALAL-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance
Instance ID Feature Language
Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
Database Engine Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
SQL Server Replication 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
Full-Text Search 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER
Analysis Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER
Reporting Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL
Database Engine Services 1033 Express Edition 10.3.5500.0
No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL
SQL Server Replication 1033 Express Edition 10.3.5500.0
No
Sql Server 2008 R2
Client Tools Connectivity 1033
10.50.1600.1 No
Sql Server 2008 R2
Client Tools Backwards Compatibility 1033
10.50.1600.1 No
Sql Server 2008 R2
Client Tools SDK 1033
10.50.1600.1 No
Package properties:
Description: SQL Server Database Services
2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20140327_005035\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: IS,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL
Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft
SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20140327_005035\ConfigurationFile.ini
Detailed results:
Feature: Integration
Services
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management
Tools - Complete
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management
Tools - Basic
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync
Framework
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passedmy summary log file information:
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052700
Exit facility code: 1212
Exit error code: 1316
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-27 00:52:25
End time: 2014-03-27 00:56:09
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name: SEVALAL-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL Database Engine Services 1033
Express Edition 10.3.5500.0 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL SQL Server Replication 1033
Express Edition 10.3.5500.0 No
Sql Server 2008 R2 Client Tools Connectivity
1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools Backwards Compatibility
1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools SDK
1033 10.50.1600.1 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: IS,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
Detailed results:
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SystemConfigurationCheck_Report.htm -
How to restore SQL Server 2008 database to SQL Server Express 2012
How to restore SQL Server 2008 database to SQL Server Express 2012.
I BACKED UP a SQL Server 2008 database from work, which runs the enterprise version of 2008, and I tried to RESTORE it to my new 64-Bit home PC which is running the new SQL Server Express 2012 64-Bit (Advanced Edition).
But if fails. I get the following message text.
Can anyone help me please. I thought restoring a 2008 database to the later version 2012 would be possible.
Here is the error message. Thanks.
TITLE: Microsoft SQL Server Management Studio
Restore of database failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the backup, or use a
backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the
backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
Are you sure your database is SQL server 2008 from error message it seems your SQL server version is 2000.I guess you have multiple versions of SQL server.
AFAIK you cannot restore backup of SQL server 2000 to 2012 directly .Restore it first to SQL 2008/2008R2 or 2005 then take backup again of new database created and then you would be able to restore it on 2012.Its kind of intermediate way
Also make sure your DB size is less than 10 G as max DB size supported by Express edition is 10 G and if your DB size is more than 10 G restore will fail.
You are also trying to restore enterprise DB backup on express edition so you will loose enterprise features on express edition
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
How to connect sql server 2008 r2 sp2 with vs2013 ultimate?
how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Hi Shahzad,
>>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
And then you can create the connect string in the Add Connection dialog box.
Hope it help you!
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
How can install SQL Server 2008 Integration Services without CD?
How can install SQL Server 2008 R2 Integration Services without CD?
The PC with Windows 7 32-bits is far away and poor bandwidth . So, I want to install SQL Server 2008 Integration Services without CD.
Does any installer for SSIS only?Copy the install media from a memory stick, portable drive or network.
Arthur My Blog -
How to install SQL server 2008 express on Windows server 2008 R2 standard OS
Hi,
I have Windows server 2008 R2 Standard edition (64-bit) and trying to install SQL server 2008 express edition since I do not have SQL server 2008. When I install it I am unable to see Management Studio so I am trying to install management studio as well
but still I am facing issue. Please let me know whether SQL server 2008 express edition is compatible with Windows server 2008 R2 Standard. If not then pls let me know the proper steps to install it.
RegdsHello,
Service Pack 1 for SQL Server 2008 is required to be compatible with Windows Server 2008 R2.
Please download QL Server 2008 Express with SP1 included from the following link:
http://www.microsoft.com/en-us/download/details.aspx?id=25052
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
How to stop SQL Server 2008 R2 generating SQLDump.mdmp files constantly?
Something went wrong with local SQL Server 2008 R2 and it constantly generates SQLDump.mdmp files. It generated 40Gb(!) of SQLDump.mdmp this morning. Server rebooted, but didn't help.
Any ideas what happened with SQL Server and how to stop SQLDump.mdmp files generation?
SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP |
My Blog about Information Management |
My twitterMemory Dumps are generated automatically by the SQL Server under various circumstances - most of which indicate potential problems in the Instance or the machine. Some that I can recall right now are:
Database Corruption
Non-yielding scheduler
Non-yielding resource monitor
AV (Access Violation)
There can be several other reasons as well. SQL Server generates the dumps, so that these dumps can be analyzed to find out potential problems in the SQL Server.
IMHO, rather than trying to find out ways to stop the dumps from being generated, please try to find out potential problems in the Instance or the machine and fix that. This will stop the dump generation anyway.
In case you need any assistance in analyzing the Dumps, please feel free to engage Microsoft Support.
Suhas De
Please mark solved if your question is completely answered; vote it as helpful to help others find a solution quicker.
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog: http://blogs.msdn.com/b/suhde -
How to configure Sql Server 2008 R2 for debugging without disabling Windows Firewall?
When I try to debug a procedure in Sql Server 2008 R2 I get a dialog box telling me to unblock some ports.
>>
The Windows Firewall on this machine is currently blocking remote debugging. Remote debugging requiers that the debugger be allowed to receive informatino from the network. Remote debugging also requires DCOM (TCP Port 135) and IPSEC (UDP 4500
/ UDP 500) be unblocked.
<<
I went to the Windows Firewall and added some new Inbound rules for each of the specified ports (in the images below. But after this and rebooting entire computer -- I still get this dialog box when I want to go into debug mode from SSMS. I can
actually kind of debug standalone code in the SSMS window if I cancel the dialog box. But I can't debug an actual stored procedure -- which is what I need to do. I also noticed that my server has an IP address instead of LocalHost. This is
not a public Server -- it's my private development machine which is on a peer to peer network (with one other workstation), but I don't need that workstation to be able to access this server.. Would localholst make a difference for debugging? How
should I configure the sql server? The firewall?
Rich PUse PRINT and SELECT for debugging. That's what I do. I used to play with the debugger in SQL 2000 and older days, but I realised that I spent more time on getting it to work that I gained from using it.
I thought about that. I guess that IS the way to go. Very well. Thank you for the suggestion. Although, when the debugger does work in the regular window (not a stored proc because it doesn't work there) the debugger IS nice.
For debugging my proc I am thinking I will insert param vals into a test collection table for now. One obscure error I am getting with a particular proc -- in a When loop on one parameter I get the "value will be truncated" error -- but everything
is set to accept 1000 characters and none of the source data even comes close to 1000 characters. I have isolated at what point the error occurs and which section of data where the error is occurring but I have not isolated the cause of the error.
I cannot reproduce the error when I run the procedure by hand in a regular query window with the exact same code. The error only occurs when the code is run in the stored proc.
Rich P -
SQL Server 2008 is the worst installation experience ever
Sorry but you guys have really messed up with SQL Server 2008 installation.
I've been using SQL server since 6.5, so I would classify as a fan. We were looking at upgrading from 2005, which I was quite pleased with.
The installation experience is the worst I've ever experienced. I am a computer expert, and I couldn't figure out how to install it properly. Why is it that when I downloaded SQL Server Management Studio Express 2008, it seems as though it wants
to install the full database? Why is it when I was asked if I wanted to install a new version of SQL Server 2008 or use a previous install, when I chose previous install, it said that an instance ID was missing, but there was no way to specify anything
else? It drove me crazy.
Why are there so many requirements and restrictions for the installation, when all I want to do is install Management Studio? It's intolerable and makes me never want to upgrade to 2008. Why is the process so terrible when Microsoft is supposed
to have the best UE people in the business?
You guys did a really terrible job on this one.We have not tried to cluster 2012. We used to cluster; however, we were not prepared to manage the added complications. The result was that our non-clustered servers had better uptime. We used to joke about how many 8s we were
getting with our cluster. (To be fair, it did not help that we had a 7x24 SLA with only 8-5 staff. When the cluster fails to failover, it can be a long time before it is fixed. We eventually got the kinks worked out.)
I understand the frustration. Excellence and stability can be achieved, but product lifecycles can punish those who seek such qualities. Product changes and shorter support lifecycles produce revenue for MS, so I don't see this getting better.
There will be a new OS, new SQL, and a new set of problems the next time around.
I expect things to get worse until we get pushed into the cloud. A stable environment in the cloud is profitable for MS and clients. I do not think this is the case now outside the cloud. Upgrading applications to remain
on supported products is very costly. And about the only business benefit of the upgrade is that the product remains on a supported platform and gets security updates. Sort of sound like that blackmail virus? I'd rather pay to have a
patch for new features and focus on application upgrades that improve business processes. Now bug fixes can require a major version change - which will have new bugs. I'm ranting because of some head pounding
I've done this week due to a hard coded limitation introduced in SQL 2012 by design. I'll replace the process, but I wonder how long it will work as my SQL related PSH often breaks with a new version of something. I'll
stop now. Where'd my Prozac go? Next week is new week, life is good, everything will work,....
PS I actually enjoy the work and think MS products are decent; however, our environment does seem to be more frail and less stable due to MS product changes - even if the products are getting better. Better is worse - what an odd thought.
Randy in Marin -
SQL Server 2008 on the Web/App server for BPC 7.0
In a multi-server environment (DB/OLAP on a 64-bit platform, Web/App on a 32-bit platform), is it necessary to have SQL Server on the Web/App server if Reporting Services is not used? Could you explain why SQL Server is needed on this server if Reporting Services is not used?
Hi
Reporting Service is a requirement for BPC. If it is not deployed on App Server, it can be deployed elsewhere but is required.
Other SQL related things that go on App Server include:
Reporting Services
Shared Features
Client Tools Connectivity
Management Tools - Complete
Business Intelligence Development Studio
Integration Services
Client Tools Backward Compatibility
Microsoft SQL Server 2005 Backward Compatibility Components from Microsoft SQL Server 2008 Feature Pack
Reporting Services/Integration Service requires SQL license(s). Standard ediiton of these can be used if you are not performing Load Balanced deployement.
Regards
Shaam -
Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"
I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server -
How to install sql server 2012 using the license of sql 2014
Hello,
We want to install sql server 2012 on a server because of an application that can not work with sql server 2014.
We have a license for sql server 2014. The license is not visible for sql 2014 in our licenses because it is now included in the installation package. We also can not get a license key for SQL 2012 server now.
How can we get a valid sql server 2012 license key?
Thanks,
Gr. Peter.Hello Peter,
This is a community forum for technical questions & issues.
For question regarding pricing / licensing please contact a Microsoft sales partner or licensing expert.
Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist.
Regards.
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog -
How to connect SQl Server 2008 to SAP BW
Hi Experts,
i would to build the following scenario.
I would like to connect an infoprovider or a query in sap BW to a SQL Server.
The goal will be to use the Management studio as well and to send the data from SAP BW (Cube or Query) to the sql server.
1. Could you please advice steps by steps how to do the istallation?
2; Which connectors should i use?
3. Is there any document which provide the tools, drivers, connectors to be used?
4. Is there any how to which can help after the installation to run the scenario?
Thank you in advance for your Input.
Cheers
GiloHello,
What you request can be done with DB Connect.
A good starting point is the following link :
[http://help.sap.com/saphelp_NW04/helpdata/en/58/54f9c1562d104c9465dabd816f3f24/content.htm|http://help.sap.com/saphelp_NW04/helpdata/en/58/54f9c1562d104c9465dabd816f3f24/content.htm]
Also I recommend to search further on SDN because there are some interesting posts on connecting BW to external databases like SQL Server.
Wim -
How to delete the Folder from sql server 2008
Hi all,
I was trying to delete the folder from sql server 2008 with the below script
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @cmd VARCHAR(8000)
DECLARE @folderName VARCHAR(256) -- filename for backup
SET @folderName = + (CONVERT(varchar(10), GETDATE()-7, 112)) -- 7 days back date folder name
SET @path = 'I:\Backup_Test\' + @folderName -- Folder path
SET @cmd = 'del ' + @path -- Delete
EXEC master..xp_cmdshell @cmd
--Print @cmd
This is not working it was asking the Confirmation (I:\Backup_Test\20100629\*, Are you sure (Y/N)? ) what will i do to the delete the folder.
Thanks,
Prasad R.I would notice you that T-SQL does not play well to do things like that. Do not you want using .net language to delete folders?
Old method is
declare @HR int, @CFOLDER varchar(255),@FSO int
set @CFOLDER='D:\folder\'
EXEC @HR = sp_OACreate 'Scripting.FileSystemObject', @FSO OUT
EXEC @HR = sp_OAMethod @FSO, null, 'DeleteFolder', @CFOLDER
Now regarding to your second question please examine xp_fileexist system stored procedure
CREATE FUNCTION dbo.fn_file_exists(@filename VARCHAR(300))
RETURNS INT
AS
BEGIN
DECLARE @file_exists AS INT
EXEC master..xp_fileexist @filename, @file_exists OUTPUT
RETURN @file_exists
END
GO
-- test
SELECT dbo.fn_file_exists('c:\a.txt')
Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/ -
How to store Invalid Dates in SQL Server 2008
Hi,
I have SQL Server 2008 and My table has start_Date and end_date column which is DATETIME datatype.
Somehow my table is having invalid dates which is lesser than 1753-01-01 00:00:00.0 range.
I want to know how this date get inserted in the SQL Server.
Thanks,
MuthuprabhuCan you post the DDL for that table together with a SELECT query and results demonstrating invalid data?
DECLARE @dt DATETIME = '1753-01-01 00:00:00.0';
-- Command(s) completed successfully.
DECLARE @dt DATETIME = '1752-01-01 00:00:00.0';
Msg 242, Level 16, State 3, Line 4
The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.
Datetime conversion:
http://www.sqlusa.com/bestpractices/datetimeconversion/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014
Maybe you are looking for
-
HP Officejet Pro 8500A Plus Printer will connect to apps but will not connect to EPrint
OS MAC 10.6.8 Snow Leopard. I am using a wireless connection, no USB, and everything worked fine at one time. Recently, all remote printing, including Airprint stopped connecting. I am unable to access anything on the HP website via the printer ex
-
How to print the script before realasing?
how to print the script before realasing?
-
I am creating a list of words with special characters in some of them. I get to a point where I cannot enter data directly into the cell. I have to use the data entry bar at the top in the toolbar. Any solutions available? This is the table I am crea
-
Want to know ram supported in my laptop Dv6 3004 tu
Hi, My ram is of 2gb ddr3. I am planning to upgrade my ram upto 6 gb. I want to buy extra 4gb ram from my vaccant slots. But Which type it will support. Type Speed Capacity Voltage Any recomends brand????? Plese help me out hp.
-
Passing Session State Variables to SQL query
Hi, I am using 3 pages in my application build by APEX 3.1.2. Login Page, Report Page and Form Page. I am using LDAP authentication for Login Page and I want the user session information to be feeded to the filter query being used to display data on