Understand SQL Server 2008 R2 replication features for a reporting database

Hi, I am using SQL Server 2008 R2 and working on building a reporting database using transactional push replication and want to know the downside that we should aware of using this.
For instance, is the data always available to the users even when changes are being written from the publisher?
I am also interested in learning replication mechanism & internals. How should I proceed?
Thanks in advance........
Ione

>>For instance, is the data always available to the users even when changes are being
written from the publisher?
Answer is Yes.
For more information
http://www.codeproject.com/Articles/715550/SQL-Server-Replication-Step-by-Step
--Prashanth

Similar Messages

Windows Server 2008 and SQL Server 2008 R2 - ?? for replication with Oracle

Hello:
I am running Windows Server 2008 and SQL Server 2008 R2 - 64 bit
I need to replicate data between the SQL 2008 and Oracle 11.2 ?? with Oracle being the publisher
I also would lile SqlPlus installed on the server.
I need a definite answer as to what I should download from the Oracle download area. There are just so many packages and so many version I dont know what to download.
Thanks

Hi,
Currently Microsoft Windows Server 2008 and SQL Server 2008 are not supported for SAP Business One.
For detailed information about all supported platforms, we have the following link for your reference:
www.service.sap.com/smb/sbo >product availability > supported platforms.
Regarding the information on the service marketplace this is updated on a regular basis and provides the most up to date information regarding the supported platforms for Business One.
Platforms not mentioned in this documentation are not supported.
hope it helps,
Regards,
Ladislav
SAP Business One Forum Team

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

SQL SERVER 2008 R2 - REPLICATION BEGINNERS

Hi all Friends,
Am beginner to ms sql 2008 and i have installed sql Express edition and management studio and tried to do replication there some issues i have faced
1) Cant use my host as distributor
2) SQL server agent Edition is running
3)Cant create publisher also
May i know which edition supports for all replication ( Merge,Transactional,Snapshot)
Thankful to repliers

You do not mention what you are replicating to. SQL Server express can only be a merge replication subscriber. If you want to replicate to a SQL Server Standard Edition and above you will need to make the SQL Server Standard Edition server your publisher
and the SQL Server express edition your subscriber and then changes will move from the merge replication subscriber to the publisher and vice versa.
As the SQL Server Express client does not have SQL Server agent, you will need to do a push subscription from the Standard Edition, or run RMO, or a batch file which runs replmerg.exe on the subscriber. You might also be able to run web sychronization.
If the source and destination servers are both SQL Server Express editions you might want to use Sync Services.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

HELP ME!!! I have a problem regarding SQL Server 2008 R2 Replication! :((((

Good day!
I'm having a big problem in my SQL Server 2008 R2... I can't see the "Local Publication" under the Replication...
About not installing it, I guess that's not true because I checked all the features to install.
Is this a bug? Do I need to re-install my SQL Server 2008 R2? Or simply, do I need to do something simple without re-installing it?
PLEASE HELP....
See Link below:
http://oi59.tinypic.com/4jx3y1.jpg

None. This is a freshly installed SQL Server 2008 R2. After installing, All I did was create a database.
If you want to know how I did it, simply:
1. Open SSMS, connect to local server
2. Open Object Explorer
3. Expand your local server
4. Right+Click on the Database then clicked on to "New Database..."
5. Entered my database name then clicked "OK"

SQL Server 2008 R2 { An Error occured when attaching database(s) }

Hello Guys!
I just installed SQL Server 2008 R2 a couple of days ago, on the first day use i can attach database(.mdf) with out any problem.
on the day 2, i keep getting this error:
http://img515.imageshack.us/img515/14/1212i.png
TITLE: Microsoft SQL Server Management Studio
An error occurred when attaching the database(s). Click the hyperlink in the Message column for details.
BUTTONS:
OK
after clicking the Hyperlink this window open:
http://img34.imageshack.us/img34/8766/hyperg.png
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'STARGAZER-PC\SQLSTARMAX'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Unable to open the physical file "E:\New folder\DataBase.MDF". Operating system error 5: "5(Access is denied.)". (Microsoft SQL Server, Error: 5120)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=5120&LinkId=20476
BUTTONS:
OK
in that day i reinstall SQL Server 2008 R2, because I'm so confused. after that i try to attach i still got the same error, what i did is i share the folder where the database is.
i open SSMS and try to attach and i attached without any error...
i think this is the 4rth day, untill now everytime i want to attach a database i got this error, and even i try to share the folder where the database is i still got that error.
any advice guys?
Thanks a lot
jhules
if you want to be happy, find something you love to do and do it for free, then find someone to to you for it.

The Error clearly shows that MDF files and LDF files are not matching or LDF file is corrupted.
You can follow either of the one option below
1. Restore a recent backup rather attaching the MDF file
2. Attach single MDF file without LOG File( Warning: All the log transactions will be gone and new log file will be created)
EXEC sp_attach_single_file_db @dbname = 'AdventureWorks2008R2',
@physname = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\AdventureWorks2008R2_Data.mdf';
Thanks, Aditya Badramraju, _______________________________________________________ Please mark answered 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. _______________________________________________________

SQL Server 2008 64-bit - Master Data Services troubleshoot database create Error

I am getting the following error when trying to create a new database in SQL server using MDS
        Microsoft.MasterDataServices.Configuration.ConfigurationException: Data is Null. This method or property cannot be called on Null values. ---> System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or
property cannot be called on Null values.
           at System.Data.SqlClient.SqlBuffer.get_String()
           at Microsoft.MasterDataServices.Configuration.DatabaseUtilities.GetDatabases(DatabaseServerInformation server)
           at Microsoft.MasterDataServices.Configuration.Commands.NewMasterDataServicesDatabase.InternalProcessRecord()
           at Microsoft.MasterDataServices.Configuration.Commands.ConfigurationCmdlet.ProcessRecord()
           at System.Management.Automation.CommandProcessor.ProcessRecord()
           --- End of inner exception stack trace ---
        at Microsoft.MasterDataServices.Configuration.InstanceManager.Execute(Command command)
           at Microsoft.MasterDataServices.Configuration.InstanceManager.CreateMasterDataServicesDatabase(DatabaseServerInformation serverInformation, DatabaseInformation databaseInformation)
           at Microsoft.MasterDataServices.Configuration.UI.MdsDatabase.CreateNewDatabase()
How can this error be resolved?
Thanks

Just double check the code and history.
The bug is fixed in 2011/08/23 and made into SQL 2012 RTM. So I assume you are using 2008 R2, which mainstream support is ended. I am not able to push a fix to that.
https://msdn.microsoft.com/en-us/library/ms178534.aspx
collation_name
sysname
Collation for the database. Acts as the default collation in the database.
NULL = Database is not online or AUTO_CLOSE is set to ON and the database is closed.
The only option would be fix the NULL collation databases.

SharePoint 2013, SQL Server 2012 SP1 Enable RBS for Additional Content Databases

We Enabled RBS in our SharePoint 2013 Environment recently. The time when we Configuring we had only one Content Database and we successfully configured. now we created more web applications and we need to enable RBS for newly created Content Databases.
we searched and tried lots of approaches, but we cudn't manage to achieve this. can anyone help us to enable RBS on additional Content Databases. (No offense but direct instructions would be great rather than providing links).
Thank you!

Here is step by step instruction with screenshot
http://thesharepointfarm.com/2011/03/enabling-rbs-on-multiple-content-databases/
Try to run
run this command on the SharePoint server: msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME=”WSS_Second” FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=”DBServer”
Thank you so much for the reply Indrajeet. we followed the instruction to the letter but when we try the command, it failed. while doing some search, we came across an interesting Article.
http://rudolphoravec.blogspot.com/2012/10/remote-blob-storage-rbs-and-sharepoint.html
And surprisingly it is Working.

SQL Server versions Mainstream Support Dates for 2005 and 2008

What is the link to Microsft's official published Support dates for SQL Server 2005 and SQL server 2008.
There are several conflicting reports and am looking for the official MicroSoft link so it can be shared as needed.

Hello,
Please refer to following blogs
http://blogs.msdn.com/b/sqlreleaseservices/archive/2011/01/27/end-of-mainstream-support-for-sql-server-2005-and-end-of-service-pack-support-for-sql-server-2008-sp1.aspx
http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=sql
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Analysis Server for sql server 2008 r2 express?

Not sure if this is a forum where I could ask about how I could obtain analysis server for sql server 2008 R2 express - only for academic purposes (not doing any production stuff - just getting up to speed on OLAP, creating fact tables, star schema,
snowflake schema, ...). Suggestions appreciated how I may obtain a version of analysis server for sql server 2008 R2 Express -- or if this is not a good forum to ask that question then I would be grateful for being pointed to the proper forum.
Thanks
Rich P

SQL Express Edition Doesn't support analysis services.
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx#SSAS
As Li said, you need to go with the developer edition.
-Prashanth

Commercial distributed application with SQL Server 2008 back-end

Hi All, I am suffering some confusion and wondered if anyone could clear up a few questions for me.
I am currently developing an application to be sold commercially, to be deployed locally on a customer's site. It is a client-server application and the server utilises an SQL Server 2008 back-end. Client applications however do connect directly to the SQL
Server.
We probably want to support about 100+ client applications. Each client application could feasibly be making several SQL query requests per second.
Firstly, what are the licensing implications of this for the customer? I understand SQL Server 2008 can support 30000+ concurrent connections, but am I correct in thinking that each client application will require CALs? Or I understand there is a "processor
licence"...
Secondly, and I know this is quite a broad question, but can anyone offer a rough estimation of the processing/storage requirements for the server?
Thanks in advance!

Hi click,
Usually, SQL Server is licensed through Microsoft Volume Licensing programs using two software licensing models, one is the Per Processor (Core-based) licensing model, another is Server plus Client Access License (Server+CAL) licensing model which is based
on the users or devices accessing the product.
Using the Per Core Licensing Model When running SQL Server in a physical operating system environment (OSE), all physical cores on the server must be licensed. When licensing SQL Server software under the Server+CAL model, customers purchase a server license
for each server and a client access license (CAL) for each device (Device CAL) and/or user (User CAL) accessing SQL Server or any of its components.
For more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide
to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
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: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
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
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: 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\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting 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: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801

Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
log file:
===============
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
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: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
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
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting 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: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801

SQL Server 2008 R2 - Cannot remove 50th instance with command line uninstall

I have reached the 50 instance SQL Server limit on my Microsoft Server 2008. I have tried to remove an existing instance using the command line below but it still is reporting that "No more transforms are available because the maximum 50 has been
reached." and the uninstall is hanging on Select Features. Some of the instances on this server are for SQL Server 2008 and some are for R2. Where do I go from here?
"C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\setup.exe" /Action=Uninstall /FEATURES=SQL /INSTANCENAME=myinstance

"C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\setup.exe" /Action=Uninstall
/FEATURES=SQL /INSTANCENAME=myinstance /Q
Try this..
/Q = Quite Mode..
Chetan ================================================================== ================================================================ 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.

Vb6,adodb with sql server 2008

hi for i am new to vb6 with sql server 2008. I have managed to create database named : Tuscan77 in project folder with all the necessary tables with primary and foreign keys in tables. I have done the same project in vb6 with adodb with ms access and i have
finished it. But now based on my boss orders i have to connect vb6 with adodb with sql server 2008.
Now below is my code in mdi parent form in vb6 which i used to connect to database in access.:
Dim i As Integer
Dim AccessConnect As String
Dim dBOOL As Boolean
Dim dMstr As String
If (Left(App.Path, 1) = "\") Then
dMstr = Dir(App.Path & "tuscanDB.mdb")
Else
dMstr = Dir(App.Path & "\tuscanDB.mdb")
End If
dBOOL = IIf(dMstr = "", False, True)
If (dBOOL) Then
AccessConnect = "Driver={Microsoft Access Driver (*.mdb)};" & _
"Dbq=tuscanDB.mdb;" & _
"DefaultDir=" & App.Path & ";" & _
"Uid=Admin;Pwd=;"
If (adoDatabase.State <> 0) Then
adoDatabase.Close
End If
adoDatabase.ConnectionString = AccessConnect
adoDatabase.Open
Else
Dim mPath As String
CommonDialog1.CancelError = True
CommonDialog1.Flags = cdlOFNHideReadOnly + cdlOFNPathMustExist + cdlOFNFileMustExist
' Set filters
CommonDialog1.Filter = "All Files (*.*)|*.*|RTF (*.rtf)|*.rtf|Text Files (*.txt)|*.txt"
' Display the Save dialog box
CommonDialog1.FileName = ""
CommonDialog1.ShowOpen
dMstr = Dir(CommonDialog1.FileName)
mPath = Left(CommonDialog1.FileName, InStr(mPath, dMstr) - 2)
If (CommonDialog1.CancelError = False) Then
AccessConnect = "Driver={Microsoft Access Driver (*.mdb)};" & _
"Dbq=" & dMstr & ";" & _
"DefaultDir=" & mPath & ";" & _
"Uid=Admin;Pwd=;"
' Connection Object Methods
adoDatabase.ConnectionString = AccessConnect
adoDatabase.Open
End If
End If
where adoDatabase is name of my connection in vb6 with adodb with ms access.
Now how i connect vb6,adodb with sql server 2008?
Now my sql server 2008 details:
Server type: Database Engine
Server name: NPD-4\SQLEXPRESS
Authentication: Windows authentication
User name: NPD-4\TUSCANO
password:(it is left blank or not necessary)
Database name: Tuscan77
How to i connect my Database named Tuscan77 in vb6 and adodb.? Can anyone help me please.Any help or guidance would be greatly appreciated.

Hi,
It would be more appropriate to post all your vb6 related queries in the below forums.
http://www.vbforums.com/forumdisplay.php?1-Visual-Basic-6-and-Earlier
http://forums.codeguru.com/forumdisplay.php?4-Visual-Basic-6-0-Programming
SRIRAM

SQL Server 2008 R2: which version of Visual Studio do I need to keep database projects and SSIS projects in the same solution

I need to build a solution containing a database project and an integration services project for SQL Server 2008R2. Apparently, the subset of Visual Studio tools that comes with SQL Server 2008R2 does not include database projects and does not have
Team Foundation Server support. Because of those limitations, I am trying to determine which version of Visual Studio will allow me to:
1. Build a single solution that includes both a database project and an Integration Services project
2. For the database project, be able to import a database schema from an existing SQL Server 2008 R2 database, do schema compares and update the project from the database and vice versa
3. For the Integration Services project, be able to deploy the packages to SQL Server Integration Services on SQL Server 2008 R2 (that is, to the msdb database).
4. Use Team Foundation Server for source control of the whole solution, including both project types.

Hi G Britton,
To build a solution containing a database project and an integration services project for SQL Server 2008 R2 and use Team Foundation Server for source control.
You can choose to install Visual Studio 2008.
And as you want to utilize Schema compare and/or Data compare functionalities in Visual Studio, you will need to install the
Visual Studio Team System 2008 Database Edition or Visual Studio Team System 2008 Team Suite.
In addition, for Visual Studio issues, I would like to recommend you post the question in the
Visual
Studio forums to get better support.
Reference:
Team Foundation Version Control
Compare and Synchronize Database Schemas
Interoperability and Coexistence (Integration Services)
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Understand SQL Server 2008 R2 replication features for a reporting database

Similar Messages

Maybe you are looking for