Stop charging of Sql Server

My company has a Sql Server Virtual machine. It cost us alot of money to have Sql Server running on this machine, so we have migrated all data to another database and shutdown all Sql Server services, but azures keep charging for run time of the Sql Server.
Is it possible to remove Sql Server without reinstalling the machine, so we dont have to pay for it?

Hi,
Is the Azure Virtual Machine still running ?
You will have to Stop the Virtual Machine [from the management portal] to avoid getting charged for compute time.
Regards,
Mekh.

Similar Messages

SQL Server 2008 KB2977321 Failed with Error code 1642

As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?

I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No

Database in Suspect Mode in SQL Server 2000 Log Shipping Environment

Hi All
We have movement of SQL Server 2000 at physical level. We have disable jobs and stop Agent and SQL Server services.
After moved the server we have started the server and then start SQL Server 2000 services.
All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance

All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance
Hello,
Did you made sure no transactions like restore logs were running when you stopped SQL server service or agent .I have seen in SQL 2000 an abrupt stop of SQL Server agent when its doing a process can sometimes force database in suspect mode.
I would like you to get your disk analyzed by vendor ASAP for any fault in disk at first go it seems to me an underlying hardware issue.
Please can you check errorlog and event viewer to find out any possible cause for database going into suspect mode
I always suggest to use Backup and restore method of recovery to get out from suspect database problem.If you dont have then you can move with DBCC Checkdb and various repair options but be sure
DATA LOSS might be possible when you use repair allow data loss and repair_rebuild removes constraints.
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

How to recover from mdf file (SQL Server 2000)

Hi,
My database corrupted because when I was running an update query, there is a power failure. After the computer booted, I cannot open the database anymore, it just not responding. Then I stop the sql server service, and tried to rename the .mdf and .ldf. After that it worked normally, but I need the data from the corrupted mdf file, I tried to attach the database but it just hanged. I even tried to attach without the .ldf file but it didn't work either, so I concluded that the problem is with the mdf file.
Is there any way to recover my data ??
Thanks in advance
Regards,
Edwin

Try this undocumented stuff provided by Kevin [MS].
==========
1. Back up the .mdf/.ndf files at first!!!
2. Change the database context to Master and allow updates to system tables:
Use Master
Go
sp_configure 'allow updates', 1
reconfigure with override
Go
3. Set the database in Emergency (bypass recovery) mode:
select * from sysdatabases where name = '<db_name>'
-- note the value of the status column for later use in # 6
begin tran
update sysdatabases set status = 32768 where name = '<db_name>'
-- Verify one row is updated before committing
commit tran
4. Stop and restart SQL server.
5. Call DBCC REBUILD_LOG command to rebuild a "blank" log file based on the
suspected db.
The syntax for DBCC REBUILD_LOG is as follows:
DBCC rebuild_log('<db_name>','<log_filename>')
where <db_name> is the name of the database and <log_filename> is
the physical path to the new log file, not a logical file name. If you
do not
specify the full path, the new log is created in the Windows NT system
root
directory (by default, this is the Winnt\System32 directory).
6. Set the database in single-user mode and run DBCC CHECKDB to validate
physical consistency:
sp_dboption '<db_name>', 'single user', 'true'
DBCC checkdb('<db_name>')
Go
begin tran
update sysdatabases set status = <prior value> where name = '<db_name>'
-- verify one row is updated before committing
commit tran
Go
7. Turn off the updates to system tables by using:
sp_configure 'allow updates', 0
reconfigure with override
Go
============

CF8 & MSDE SQL Server DSN Connection Error SOLVED!!!

Getting the following error trying to add a CF DSN to SQL
Server?
Connection verification failed for data source:
datasource_name
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver]Error establishing socket to host and port: localhost:1433.
Reason: Connection refused: connect
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver]Error establishing socket to
host and port: localhost:1433. Reason: Connection refused: connect
There are several steps in order to make ColdFusion 8 and
MSDE SQL 2005 Server
1. TCP/IP is not enabled by default. When looking in SQL
Server Configuration Manager it appears TCP/IP is enabled by there
is a second place that it has to be enabled.
2. The TCP/IP port is dynamically assigned each time the
service is started, if they are no errors it the port number stays
the same but if there is an error the port number is dynamically
changed the next time the service starts.
3. You have to add your dsn login username and password to
the database in order to connect without using the sa username and
password.
Steps to get DSN setup correctly.
1. Open SQL Server Configuration Manager
2. Expand the SQL Server 2005 Network Configuration Group
3. Click on Protocols for SQLEXPRESS
4. Right click TCP/IP in the right pane and select properties
5. On the protocol tab under enabled set to yes and apply.
6. Disable dynamic port assignments by following the
instruction below:
If enabled, the default instance of the Microsoft SQL Server
Database Engine listens on TCP port 1433. Named instances of the
SQL Server Database Engine and SQL Server Compact Edition are
configured for dynamic ports, which means they select an available
port when the SQL Server service is started. When connecting to a
named instance through a firewall, configure the Database Engine to
listen on a specific port, so that the appropriate port can be
opened in the firewall.
To assign a TCP/IP port number to the SQL Server Database
Engine
In SQL Server Configuration Manager, in the console pane,
expand SQL Server 2005 Network Configuration, expand Protocols for
<instance name>, and then double-click TCP/IP.
In the TCP/IP Properties dialog box, on the IP Addresses tab,
several IP addresses appear, in the format IP1, IP2, up to IPAll.
One of these are for the IP address of the loopback adapter,
127.0.0.1. Additional IP addresses appear for each IP Address on
the computer. Right-click each address, and then click Properties
to identify the IP address that you wish to configure.
If the TCP Dynamic Ports dialog box contains 0, indicating
the Database Engine is listening on dynamic ports, delete the 0.
In the IPn Properties area box, in the TCP Port box, type the
port number you wish this IP address to listen on, and then click
OK.
In the console pane, click SQL Server 2005 Services.
In the details pane, right-click SQL Server (<instance
name>) and then click restart, to stop and restart SQL
Server.
7. Open Microsoft SQL Server Management Studio Express
8. Connect to your local copy of SQL Server
9. Expand the Security group
10. Right click login. Select new login.
12. Enter the dsn login name you want.
11. Choose SQL Server Authetication.
12. Enter the dsn password you want twice.
13. Disable user must change password at next login
14. Choose default database if you like.
15. Click User Mappings in left pane.
16. Click databases you want login to have access to.
17. Click ok.
You should now be able to add your CF DSN using localhost for
server and the port number you put in earlier. Default port number
is 1433.
You can view which port number SQL is listening to at this
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp
tcpport
You can test connectivity to the sql server by typing telnet
localhost 1433 or the port number you selected at a command prompt.
You should get a blank screen not an error.
Hope this helps, I spent 3 hours figuring it out.
David

I'm running into the same error with CFMX 7 and SQL 2000. The
port is set correctly (1433) in SQL, but it just can't communicate
successfully. SQL reside on a seperate server. Any thoughts?
Chris

Error when re-starting an SQL Server Instance from VBA - [SQL-DMO]Service Control Error: Access is denied.

Our Application needs to have the use of the [Named Pipes] and [TCP/IP] Protocols. To save our Users the hassle of having to enable them manually our application has always done it for them and then stopped and restarted SQL Server. However
since the advent of Vista and Windows 7, the restart stopped working. We solved the problem by detecting the failure to re-start and giving Users sufficient instructions for them to do it themselves. Since this only occurs during installation on
the Server, this approach has not been too much of a hassle. However we would like to tidy this up if possible. This the VBA code that is causing the problem:
    obj_SQLServerInstance2.Start _
        g_SQL_UseWindowsAuthentication, _
        SQLServerInstance, _
        UserName, _
        Password
This still works when run under XP, but fails under Windows 7 with the Error:
[SQL-DMO]Service Control Error: Access is denied.
Does anyone know how to resolve the problem?

This still works when run under XP, but fails under Windows 7 with the Error:
[SQL-DMO]Service Control Error: Access is denied.
Hello Brian,
Under Windows 7 you have to run the VBA script with admin permission, a normal user don't have permissions to start/stop services.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Sap4.7 and sql server 2000 on windows2003:when install di ,error:MDB-05039

sap4.7 and sql server 2000 on windows2003:
when install database instance ,there is a error,at change tempdb
MDB-05039:Unable to stop server dev ,
please help !!!!

Every time you start SQL Server it also creates a new tempdb. When you change the layout (physical structure, size) you have to restart SQL Server in order for these changes to take effect.
It seems that the installation routine has changed the layout (it does that according to your input!) and is now trying to stop and restart SQL Server. When you run into this error, have you tried to stop and restart SQL Server manually? After that choose the Retry option of the installation routine. Just a guess...
Do you have some more log information?
Sven

Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"

Hello,
I have a big problem.
I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".
I already tried all solutions from Google for this problem but nothing works.
Can someone help me plase?
My System: Window 8 Pro with Visual Studio 2012.
Thanks
Sven

Would you please uplaod/share SQL Server setup logs
C:\Program
Files\Microsoft
SQL Server\110\Setup
Bootstrap\Log\20130125_133342
to file sharing service like SkyDrive.com
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread.

Dispatcher stopped and not able to connect with sql server

Hi ,
                   In one of test system disp+work is started and then within no time its stopped.
I am able to connect with sql server 2005 database but while starting sap dispatcher is stopping.
Here is the log of dev_wo
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, MJ
B
B Thu Jan 05 07:24:02 2012
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' ...
B Library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' loaded
B Version of 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' is "700.08", patchlevel (0.72)
B New connection 0 created
M sysno      11
M sid        DE1
M systemid   560 (PC with Windows NT)
M relno      7000
M patchlevel 0
M patchno    75
M intno      20050900
M make:      multithreaded, Unicode, optimized
M pid        988
M
M kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)
M length of sys_adm_ext is 572 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 988) [dpxxdisp.c   1299]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm)          23936     (1408)
M DpShMCreate: sizeof(tm_adm)          3994272     (19872)
M DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
M DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
M DpShMCreate: sizeof(comm_adm)          528064     (1048)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm)          0     (72)
M DpShMCreate: sizeof(vmc_adm)          0     (1440)
M DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
M DpShMCreate: sizeof(gw_adm)     48
M DpShMCreate: SHM_DP_ADM_KEY          (addr: 07F90040, size: 4659000)
M DpShMCreate: allocated sys_adm at 07F90040
M DpShMCreate: allocated wp_adm at 07F91E40
M DpShMCreate: allocated tm_adm_list at 07F97BC0
M DpShMCreate: allocated tm_adm at 07F97BF0
M DpShMCreate: allocated wp_ca_adm at 08366E90
M DpShMCreate: allocated appc_ca_adm at 0836CC50
M DpShMCreate: allocated comm_adm at 0836EB90
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 083EFA50
M DpShMCreate: allocated gw_adm at 083EFA90
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 083EFAC0
M DpShMCreate: allocated wall_adm at 083EFAC8
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Thu Jan 05 07:24:03 2012
M ThInit: running on host sugarland
M
M Thu Jan 05 07:24:04 2012
M calling db_connect ...
C Warning: Env(MSSQL_SERVER) [SUGARLAND\DE1] <> Prof(dbs/mss/server) [SUGARLAND]. Profile value will be used.
C Thread ID:708
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll'
C dbmssslib.dll patch info
C    patchlevel   0
C    patchno      72
C    patchcomment MSSQL: Thread check in DbSlDisconnect (969143)
C np:(local) connection used on SUGARLAND
C CopyLocalParameters: dbuser is 'de1'
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:24:19 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:24:34 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:24:49 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn to np:(local).
C Retrying without protocol specifier: (local)
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:25:05 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:25:21 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:25:37 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 0
B ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY2=> sql error 0      performing CON [dblink#3 @ 431] [dblink 0431 ]
B ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1411]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10156]
M
M Info for wp 0
M
M    stat = 4
M    reqtype = 1
M    act_reqtype = -1
M    rq_info = 0
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = 65535
M    rq_source = 255
M    last_tid = 0
M    last_mode = 0
M    semaphore = 0
M    act_cs_count = 0
M    control_flag = 0
M    int_checked_resource(RFC) = 0
M    ext_checked_resource(RFC) = 0
M    int_checked_resource(HTTP) = 0
M    ext_checked_resource(HTTP) = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M    vm = V-1
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
M * ERROR       ThInit: db_connect
M *
M * TIME        Thu Jan 05 07:25:37 2012
M * RELEASE     700
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        10354
M * COUNTER     1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 988) [dpnttool.c   327]
Please help me on this
Thanks
Srikanth

Hi Amit,
             I restarted the system but dispatcher still in same stage.
Here is the log for dev_w0
========================================
Fri Jan 06 03:41:06 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 0
B ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY2=> sql error 0      performing CON [dblink#3 @ 431] [dblink 0431 ]
B ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1411]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10156]
M
M Info for wp 0
M
M    stat = 4
M    reqtype = 1
M    act_reqtype = -1
M    rq_info = 0
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = 65535
M    rq_source = 255
M    last_tid = 0
M    last_mode = 0
M    semaphore = 0
M    act_cs_count = 0
M    control_flag = 0
M    int_checked_resource(RFC) = 0
M    ext_checked_resource(RFC) = 0
M    int_checked_resource(HTTP) = 0
M    ext_checked_resource(HTTP) = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M    vm = V-1
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
M * ERROR       ThInit: db_connect
M *
M * TIME        Fri Jan 06 03:41:06 2012
M * RELEASE     700
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        10354
M * COUNTER     1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3632) [dpnttool.c   327]

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 twitter

Memory 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

Alert: SQL Server Service Broker or Database Mirroring Transport stopped

Hi Team,
I got this error message even no one DB configured as mirroring ???
Alert: SQL Server Service Broker or Database Mirroring Transport stopped Priority: 0 Severity: 2 Resolution state: New
Alert description: The Database Mirroring protocol transport has stopped listening for connections.

Can you check the rule. By default the configurations are disabled state that is the reason you are getting the alert.
If it's not configured properly then you might need to override it
--Prashanth

OGG for SQL Server - Extract stops capturing - Bug?

Hi, all,
I've found a problem with OGG for SQL Server where the Extract stops capturing data after the transaction log is backed up. I've looked for ways to reconfigure OGG to avoid the problem but couldn't find any reference to options to workaround this problem. It seems to be a bug to me.
My Extract configuration is as follows:
EXTRACT ext1
SOURCEDB mssql1
TRANLOGOPTIONS NOMANAGESECONDARYTRUNCATIONPOINT
EOFDELAY 60
EXTTRAIL dirdat/e1
TABLE dbo.TestTable;
I'm using the EOFDELAY parameter for testing purposes only, since it's easy to reproduce the scenario that causes the issue when the extract polling is configured with longer intervals.
When the Transaction Log backup runs, SQL Server marks all the virtual logs that are older than the primary and secondary truncation points as inactive (status = 0). These virtual logs can then be reused if required. They still contain change records, though, and OGG can read from then if required, before they are overwritten. This situation will never occur if we are not using SQL Replication and have the Extract configured with the parameter MANAGESECONDARYTRUNCATIONPOINT.
However, I'm trying to simulate a scenario where OGG is used along SQL Replication and the extract is configured with the NOMANAGESECONDARYTRUNCATIONPOINT option. The situation that I've reproduced and caused the Extract to stop capturing is the follow sequence of events:
1. Extract reads transaction log and capture change up to LSN X
2. More change are made to the database and the LSN is incremented
3. Log Reader reads Transaction Log, captures changes up to LSN X+Y and advances the secondary truncation point to that LSN
4. A transaction log occurs, backs up all the active virtual logs, advances the primary truncation point to a LSN greater than LSN X+Y, and marks all the virtual logs with LSNs <= X+Y as inactive (status = 0)
5. Changes continue to happen in the database consuming all the available inactive virtual logs and overwriting them.
6. The extract wakes up again to capture more changes.
At this point, the changes between LSNs X and X+Y are not in the Transaction Log anymore, but are available in the backups. From what I understood in the documentation the Extract should detect that situation and retrieve the changes from the Transaction Log backups. This, however, is not happening and the Extract becomes stuck. It still pools the transaction log at the configured interval query the log state with DBCC LOGINFO, but doesn't move forward anymore.
If I stop and restart the Extract I can see from the trace that it does the right thing upon startup. It realises that it requires information that's missing from the logs, query MSDB for the available backups, and mine the backups to get the required LSNs.
I would've thought the Extract should do the same during normal operation, without the need for a restart.
Is this a bug or the normal operation of the Extract? Is there a way to configure it to avoid this situation without using NOMANAGESECONDARYTRUNCATIONPOINT?
The following is the state of the Extract once it gets stuck. The last replicated change occurred at 2012-07-09 12:46:50.370000. All the changes after that, and there are many, were not captured until I restarted the Extract.
GGSCI> info extract ext1, showch
EXTRACT EXT1 Last Started 2012-07-09 12:32 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:54 ago)
VAM Read Checkpoint 2012-07-09 12:46:50.370000
LSN: 0x0000073d:00000aff:0001, Tran: 0000:000bd922
Current Checkpoint Detail:
Read Checkpoint #1
VAM External Interface
Startup Checkpoint (starting position in the data source):
Timestamp: 2012-07-09 11:41:06.036666
LSN: 0x00000460:00000198:0004, Tran: 0000:00089b02
Recovery Checkpoint (position of oldest unprocessed transaction in the data so
urce):
Timestamp: 2012-07-09 12:46:50.370000
LSN: 0x0000073d:00000afd:0004, Tran: 0000:000bd921
Current Checkpoint (position of last record read in the data source):
Timestamp: 2012-07-09 12:46:50.370000
LSN: 0x0000073d:00000aff:0001, Tran: 0000:000bd922
Write Checkpoint #1
GGS Log Trail
Current Checkpoint (current write position):
Sequence #: 14
RBA: 28531192
Timestamp: 2012-07-09 12:50:02.409000
Extract Trail: dirdat/e1
CSN state information:
CRC: D2-B6-9F-B0
CSN: Not available
Header:
Version = 2
Record Source = A
Type = 8
# Input Checkpoints = 1
# Output Checkpoints = 1
File Information:
Block Size = 2048
Max Blocks = 100
Record Length = 20480
Current Offset = 0
Configuration:
Data Source = 5
Transaction Integrity = 1
Task Type = 0
Status:
Start Time = 2012-07-09 12:32:29
Last Update Time = 2012-07-09 12:50:02
Stop Status = A
Last Result = 400
Thanks!
Andre

It might be something simple (or maybe not); but the best/fastest way to troubleshoot this would be to have Oracle (GoldenGate) support review your configuration. There are a number of critical steps required to allow GG to interoperate with MS's capture API. (I doubt this is it, but is your TranLogOptions on one line? It looks like you have it on two , the way it's formatted here.)
Anyway, GG support has seen it all, and can probably wrap this up quickly. (And if it was something simple -- or even a bug -- do post back here & maybe someone else can benefit from the solution.)
Perhaps someone else will be able to provide a better answer, but for the most part troubleshooting this (ie, sql server) via forum tends to be a bit like doing brain surgery blindfolded.

Data Warehouse errors, SQL Server Agent Stopped

I just installed SCE 2010 on a 2k8 server and went through the config wizard. Now it is showing Data Warehouse alerts, including:
Data Warehouse failed to discover object health state standard data set. Failed to enumerate (discover) Data Warehouse objects and relationships among them. The operation will be retried.
Exception 'SqlException': Management Group with id '6FDBE66E-E35D-BCB8-0FA1-5947E45FE643' is not allowed to access Data Warehouse under login 'domain\user'
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Discovery.StandardDataSet
Instance name: State data set
Instance ID: {217CFE24-F6F6-0DFF-9EA9-64C62895EE29}
Management group: SCESERVER_MG
I let the SCE install SQL 2008 Express. When I checked on the SQL Services, SQL Server Agent Service is stopped and will not start. Not sure if this is the cause of the above issue. I also can't log in to the SQL Server Management Studio.
How can I fix this? What other information do you need from me.

Danny01 - tried the domain admin rights on the service with no difference - put it back
Radhey Shah - I checked the admin account and it is the same account that I set the SQL up with. How do I verify this account has admin rights on the SQL DB?
The error that comes up when I try to run the SQL Server Agent Service is...
"The Sql Server Agent (Essentials) service on SCESERVER
started and then stopped. Some services stop automatically if
they are not in use by other serives or programs."
Also, when I look at the alerts within SCE, here is the current alert..
OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
: Cannot open database "OperationsManagerDW" requested by the login. The login failed.
Workflow name: Microsoft.Windows.Client.Vista.ComputerGroup.DiskTrendsComputer
Instance name: Microsoft System Center Data Warehouse
Instance ID: {16781F33-F72D-033C-1DF4-65A2AFF32CA3}
Management group: SCESERVER_MG

SAPINST 4.7 with MS SQL SERVER Error "Unable to stop server"

I'm trying to install SAP 4.7 on
- Windows 2003 Server _ host "tpt"
- SQL Server 2000 SP3 _ new Instance "MYSAP". Collation is already set to "SQL_Latin1_General_CP850_BIN2".
Sapinst ran well on all input data steps.
Next it applied from steps
"Create SAP System Opertion System Groups and Users"
"Check/Adapt File System"
until step "MS SQL SERVER tempdb Parameters" with Processing message "Changing location of
tempdb files", then stopped the installation.
I've got Error_Log file:
Transaction begin ********************************************************
INFO 2004-09-19 10:21:24
Successfully connected to "tpt\MYSAP"
ERROR 2004-09-19 10:21:25
MDB-05039 Unable to stop server "tpt\MYSAP"; error: "[Microsoft][ODBC SQL Server Driver][SQL Server]Herunterfahren des Servers auf Anforderung. (german text means "Server shuts down on request")
[Microsoft][ODBC SQL Server Driver][SQL Server]SQL Server beendet diesen Prozess." (german text means "SQL Server stops this process")
ERROR 2004-09-19 10:21:25
MDB-05034 Call to a threaded function returned "1".
Transaction end **********************************************************
WARNING 2004-09-19 10:30:21
The step doChangeTempDBParameters1 with step key SAPSYSTEM|ind|ind|ind|ind|ind|0|SAPComponent|ind|ind|ind|ind|ind|0|DatabaseServer|windows|ind|mss|ind|ind|0|TempDB|windows|ind|mss|ind|ind|0|doChangeTempDBParameters1 executed with status ERROR.
WARNING 2004-09-19 10:30:21
An error occurred during the installation.
Can you help me?
Thanks very much
thanh

Hello,
you should not use a german version of MS SQL Server.
Regards
Gregor

Stopping sql server services while applying Service pack On SQL server 2008 and 2008 R2

Hi,
I am planning to apply service pack 3 for SQL 2008 R2 and Service pack 4 for SQL server 2008. This is my first time and I am applying first QA and DEV environment. I have one confusion. In cluster once you fail over sql resources to active node all of the
sql services including SQLSERVER and Agent are automatically stopped in passive node where we apply service pack. But in Stand alone, The services are not automatically stopped. Do I need to manually stop those services like SQLSERVER, Agent, Browser
and others if any before I start applying service pack?
Early Response is highly appreciated.
Thanks In Advance

Hello,
You don’t need to stop SQL Server services. Let SQL Server setup do it as needed.
Please read the following article for the cluster you would like to update:
https://support.microsoft.com/kb/958734?wa=wsignin1.0
The following article may be useful too:
http://www.sqlcoffee.com/Tips0014.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Stop charging of Sql Server

Similar Messages

Maybe you are looking for