Risks in SQL Server

Hi
I would like to know what are all high/medium/low risks are associated with oracle 9i to sql server migration.
My db size is 1 TB. We are okay with hardware adjustments.
What are complications we will face in furture if we go for it.
I appriciate your inputs with urls and documentations and direct answers
Thanks
Raj

With 1TB of data, my first question would be - do you have partitions? If so, understand how SQL Server horizontally partitions data and how that will affect your application programming and data access path.
My next first question would be, do you have lots of/ any stored procedures (packages, triggers, functions) that will have to be rewritten.
My thiurd first question would have to do with how Oracle and SQL Server differ in concurrency, read consistency, and locking. - In Oracle reads to not block writes and writes to not block reads - in SQL Server that is not necessarily true.
Even if all of your business logic were in the front end, it is far more than just moving the data and pointing to a different place. This will take lots of desk work to pull off successfully.

Similar Messages

Can we Install SQL Server Express with Advanced Services x 64 bit for our testing purpose without procuring any license? Also can we use it for commercial use if we are neglect risk sof using it on Production?

Can we Install SQL Server Express with Advanced Services x 64 bit for our testing purpose without procuring any license? Also can we use it for commercial/Production
use if we are agree to take risk of using it on Production?

Hi,
Yes you can, but you should be aware of the limitations of MS SQL Express version.
1. 1GB RAM
2. 10 GB database size per database excluding log file (SQL 2008 R2 and above)
3.Job Scheduling service is not available with SQL Server Express.
4.Data import and export feature is not available with SQL Server Express.
5.Limitation on number of CPU
Refer following article for features supported by different editions of MS SQL Server.
Features Supported by the Editions of SQL Server 2012
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
Praveen Dsa | MCITP - Database Administrator 2008 |
My Blog | My Page

Table or Object type - like #temp table in SQL Server

Hi
I need to create a temp table to hold certain data and then validate. What is the best way to do this oracle. Something similar to #temp tables in SQL Server.
Thanks

IN Oracle, you create the temporary table once, before you start your program. Then anyone can use that definition, but the system keeps the data isolated to eachr/session.
The difference in using Oracle: all DDL, including creating temp tables, performs commits and aquires locks that you want to avoid. It creates unnecessary serialization, causes transactional consistency issues and puts Oracle's Read Consistent model at risk (of ORA-01555 errors).
So, you (or the DBA) would "CREATE GLOBAL TEMPORARY TABLE ..." with the appropriate definition you want, and indicate whether you want the data deleted on commit, or on logoff.
Then you write your procedure, similar to the way you would do it in SQL Server, but you would not bracket it with creating/dropping the temp table - no need.

Sql server grants access to specific login to database.

i have created website for intranet and hosted it on server. for that i needed to create login "IIS APPPOOL\hi" in sql server 2008 for my application
to access my "reportdb" database. "IIS APPPOOL\hi" has sysadmin and public server roles in sql server 2008. And i have default login"sa" same
as "IIS APPPOOL\hi". these are working correctly. Now I want these two logins to access"reportdb" for all
operations in database and remaining all logins should be denied to access"reportdb". My Sql Server 2008 is having mixed mode (windows authentication and Sql authentication). plz help me

I think what Tauseef is requesting is to keep access for the 2 sysadmins & deny access to everyone else, correct?
As Uri mentioned, by being part of sysadmin role, “IIS APPPOOL\hi” & “sa” would have access to everything in the server, and nobody else should have access to the DB unless explicitly being granted access.
If you would really deny anyone else access to the database, you can potentially deny connect to public, and only sysadmins (who override permissions) would be able to connect; although I would strongly recommend against such practice.
Something else I would like to recommend against is the usage of sysadmin for what may not be a DBA role (IIS appPool). Following the least-privilege principle, I would recommend having a non-administrator user for applications that has enough capabilities
to perform the tasks needed.
The main risk is that a SQL injection (SQLi) bug in your application would lead to a complete compromise of your SQL server.
If there are app tasks that would require elevated permissions, I would recommend encapsulating the logic in a stored procedure and either use impersonation or digital signatures to accomplish a controlled elevation of privileges instead. If you have any
question on this topic I will be glad to assist.
I hope this information helps,
-Raul Garcia
SQL Server Security
This posting is provided "AS IS" with no warranties, and confers no rights.

SQL Server Reporting Services FAQ

Hi All,
This thread is a summary of the Frequently Asked Questions on SQL Server Reporting Services. We consolidate them and post here for your reference. If you have any further questions, please kindly start a new thread so that more community members, MVPs, and MSFTs can join the discussion and share their ideas. Thanks for your understanding.
Part I: SQL Server Reporting Services General Topics
1. How to migrate SQL Server 2008 Reporting Services to another computer?
2. How to combine connecting string via parameter?
3. How to install a 32-bit version of SQL Server 2005 Reporting Services on a computer that is running a 64-bit version of Windows?
4. Error of EXECUTE permission denied on object 'xp_sqlagent_notify'.
5. Security consideration for anonymous access to Report Server.
6. How to create a custom report template in Reporting Services?
7. Does Reporting Services support horizontal tables which have fixed rows and dynamic columns?
8. How to reset the page number back to 1 every time the report gets a group break?
9. How to open the drill- through report in a new browser window?
10. How to verify the version of SQL Server?
11. How to use multiple datasets?
12. How to upgrade report from SQL Server 2000 to SQL Server 2005?
13. Out of memory error when exporting reports to Excel.
14. How to improve PDF quality of the report exported in Reporting Services 2005?
15. How to enable the Select All option for a multi-value parameter?
Part II: SQL Server Reporting Services SharePoint Integrated Mode Topics
1. How to deploy reports to SQL Server Reporting Services in SharePoint Services integrated mode?
2. How to integrate SQL Server Reporting Services and SharePoint Services?
3. How to refer the reports on the Report Server in SharePoint Services?
4. How to manage user to view reports in SharePoint integrated mode?
5. What information is needed when posting questions regarding SharePoint integrated mode?
6. Is Report Builder available in SharePoint Integrated Mode?
PLEASE NOTE: Microsoft does not offer formal support for the communities you'll find here. Instead, our role is to provide a platform for people who want to take advantage of the global community of Microsoft customers and product experts. Microsoft may monitor content to ensure the accuracy of the information you'll find, but any information provided by Microsoft staff is offered "AS IS" with no warranties, and no rights are conferred. You assume all risk for your use.
Microsoft Online Community Support

1.        Question 3: How to install a 32-bit version of SQL Server 2005 Reporting Services on a computer that is running a 64-bit version of Windows?
Answer:
To install the 32-bit version of Reporting Services on a computer that is running the 64-bit version of IIS 6.0, we can follow these following steps:
1.       Uninstall the 64-bit version of Reporting Services.
Note: Side-by-side installations of 32-bit versions of Reporting Services and 64-bit versions of Reporting Services are not supported.
2.       Run the Dotnetfx64.exe file to manually install the .NET Framework.
The Dotnetfx64.exe file is in the Tools\redist\2.0 folder on the SQL Server 2005 Setup media. To download the Dotnetfx64.exe file, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=70186
3.       In IIS Manager, click Web Server Extensions.
4.       In the Details pane, right-click ASP.NET V2.0.50727, and then click Allow.
5.       Right-click Web Sites, and then click Properties.
6.       Click the ISAPI Filters tab.
7.       In the Filter Name column, click ASP.NET_2.0.50727, and then click Edit.
8.       Replace C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_filter.dll with C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll.
Note: The Aspnet_filter.dll file in the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ folder is a 32-bit version of the file.
9.       Click OK two times, and then close IIS Manager.
10.   At a command prompt, run the following command:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
11.   Install the 32-bit version of Reporting Services.
12.   After setup is complete, open IIS Manager, and then click Web Server Extensions.
13.   In the Details pane, right-click ASP.NET V2.0.50727 (32-bit), and then click Allow.
To install the 32-bit version of Reporting Services on a computer that is running the 64-bit version of IIS 7.0, follow these steps:
1.       Enable ASP.NET and IIS before you install Reporting Services.
2.       Open a command prompt. To do this, click Start, point to All Programs, point to Accessories, right-click Command Prompt, and then click Run as administrator.
3.       In the User Account Control dialog box, click Continue.
4.       Copy the following script:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
5.       In the upper-left corner of the Command Prompt window, right-click the command prompt icon, click Edit, and then click Paste.
6.       Press ENTER to run the script.
7.       Install the 32-bit version of Reporting Services. You must apply SQL Server 2005 Service Pack 2 (SP2) after you install Reporting Services in Windows Vista. If you install SQL Server 2005 Express Edition with Advanced Services, you can run SQL Server 2005 Express Edition with Advanced Services SP2.
For more information, visit the following Microsoft Web site:
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2
http://go.microsoft.com/fwlink/?LinkID=63922
8.       Reset IIS.
9.       Configure the report server for local administration. To access the report server and Report Manager locally, follow these steps:
a.       Start Microsoft Internet Explorer.
b.      On the Tools menu, click Internet Options.
c.       Click Security.
d.      Click Trusted Sites.
e.      Click Sites.
f.        Under Add this website to the zone, type http://servername.
g.       If you are not using HTTPS for the default site, click to clear the Require server certification (https:) for all sites in this zone check box.
h.      Click Add.
i.         Repeat steps f and g to add http://localhost, and then click Close.
10.   This step lets you start Internet Explorer either to localhost or to the network computer name of the server for both Report Server and Report Manager.
a.       Create role assignments that explicitly grant you full-permissions access. To do this, follow these steps:
b.      Start Internet Explorer by using the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.
c.       Start Report Manager.
d.      Note By default, the Report Manager URL is http://servername/reports. If you are using SQL Server 2005 Express Edition with Advanced Services SP2, the Report Manager URL is http://servername/reports$sqlexpress. If you are using a named instance of Reporting Services, the Report Manager URL is http://servername/reports$InstanceName
e.      On the Home page, click Properties.
f.        Click New Role Assignment.
g.       Type a Windows user account in the following format: domain\user
h.      Click to select the Content Manager check box.
i.         Click OK.
j.        In the upper-right corner of the Home page, click Site Settings.
k.       Click Configure site-wide security.
l.         Click New Role Assignment.
m.    Type a Windows user account in the following format: domain\user
n.      Click to select the System Administrator check box.
o.      Click OK.
p.      Close Report Manager.
11.   Open Report Manager in Internet Explorer without using the Run as administrator option.
Microsoft Online Community Support

Moving the log file of a publisher database SQL Server 2008

There are many threads on this here. Most of them not at all helpful and some of them wrong. Thus a fresh post.
This post regards SQL Server 2008 (10.0.5841)
The PUBLISHER database primary log file which is currently of 3 blocks and not extendable,
must be moved as the LUN is going away.
The database has several TB of data and a large number of push transactional replications as well as a couple of bi-directional replications.
While the primary log file is active, it is almost never (if ever) used due to its small fixed size.
We are in the 20,000 TPS range at peak (according to perfmon). This is a non-trivial installation.
This means that
backup/restore is not even a remotely viable option (it never is in the real world)
downtime minimization is critical - measured in minutes or less.
dismantling and recreating the replications is doable, but I have to say, I have zero trust in the script writer to generate accurate scripts. Many of these replications were originally set up in older versions of SQL Server and have come along for the
ride as upgrades have occurred. I consider scripting everything and dismantling the whole lot pretty high risk. In any case, I do not want to have to reinitialize any replications as this takes, effectively, an eternity.
Possible solution:
The only option I can think of is to wind down everything, such that there are zero outstanding uncommitted transactions and detach the database, delete the offending log file and reattach using the CREATE DATABASE xyz ATTACH_REBUILD_LOG option.
This should, if I have understood things correctly, cause SQL Server to recreate the default log file in the same directory as the .mdf file. I am not sure what will happen to the secondary log file which is not moving anywhere at this point.
The hard bit is insuring that every transaction in the active log files have been replicated before shutdown. This is probably doable. I do not know how to manually flush any left over transactions to replication. I expect if I shut down all "real"
activity and wait for a certain amount of time, eventually all the replications will show "No replicated transactions are available" and then I would be good to go.
Hillary, if you happen to be there, comments appreciated.

Hi Philip
you should try this long back suggested way of stopping replication and restore db and rename or detach attach
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6731803b-3efa-4820-a303-4ffb7edf154a/detaching-a-replicated-database?forum=sqlreplication
Thanks
Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem
I do not wish to be rude, but which part of the OP didn't you understand?
Specifically the bit about 20,000 transactions a second and database size of several TB. Do you have any concept whatsoever of what this means? I will answer for you, "no, you are clueless" as your answer clearly shows.
Stop wasting bandwidth by proposing pointless and wrong solutions which indicate that you did not read the OP, or do you just do this to generate points?
Also, you clearly failed to notice that I was on the thread to which you referred, and I had some pointed comments to make. This thread was an attempt to garner some input for an alternative proposal.

Windows 8 and IE 10 crashed after printing from Report Manager SQL server 2008 / 2008 R2

We have a problem with Windows 8 in combination with IE 10 and printing reports.
When we print a report from the Report Manager 'http://<servername>/reports' the browser crashed after a print.
Sometimes before printing and somthimes after printing or when you close the browser.
Al other operating systems like XP, Vista, Windows 7 with different IE versions have no problem.
I tried the report manager from SQL Server 2008 and SQL Server 2008 R2.
The same error occured when printing from our Internet application and the reportviewer.
(ASP application written in Visual Studio 2010 and reportviewer version 10.)
The event log shows two different messages.
Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16453, time stamp: 0x509b0dfb
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
Exception code: 0xc0000005
Fault offset: 0x00061252
Faulting process id: 0x780
Faulting application start time: 0x01ce03a294f7d1d5
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d4a72486-6f96-11e2-be6e-10604b6a74ed
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16384, time stamp: 0x50107ee0
Faulting module name: rsclientprint.dll, version: 2009.100.1600.1, time stamp: 0x4bb67a74
Exception code: 0xc0000005
Fault offset: 0x00017e7a
Faulting process id: 0x9c8
Faulting application start time: 0x01ce02f35c70ab85
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\Downloaded Program Files\rsclientprint.dll
Report Id: a13fccc6-6ee6-11e2-be67-10604b6a74ed
Faulting package full name:
Faulting package-relative application ID:
Is there a fix for this problem?

Dear Mike Yin,
Thank you for your response. Your answer was the
reason for finding the real problem.
In december 2010 a SQL Server 2008 fix was the cause. I don't remember exactly the problem, but we changed the RSCLIENTPrint-x86.cab file. But instead to use the version of SQL Server 2008 we used the version of SQL Server 2008
R2 (10.50.1600.1). This worked until
Windows 8 (Internet Explorer crashed when printing).
We fixed this problem by using the RSClientPrint-x86.cab file from SQL server 2008 (10.0.5500.0).
But we now get the known problem that the
activeX always must be installed again.
The reason for this is that the version of
the SQL Server (10.0.5512.0)
and the rsclientprint.dll (10.0.5500.0) is different. SQL Server is newer (caused
by a security patch (KB2716436)).
Do you know when this problem will be resolved
by Microsoft?
Work arrounds
I've also tried to install the RSClientprint.dll
every time automatically (without user interaction).
But this will be delayed the printing for more
than 4 seconds. This
is very annoying.
Another workaround is to generate a PDF and print the PDF. But this is also
a lot slower.
Uninstall the security patch. but I don't know the security risk.

Hyper-v Failover clustering for SQL Server lab

Hi,
After 20yrs years of IT software experience, now I am realizing that I don't know much about hyperV clustering. :) I am trying to setup a lab. I badly need help on configuring network adapters
to make the machines accessible from each other. Please see details below:
I have a laptop with 8gb ram with windows 8.1 hyper-V. I created 4 VMs with Windows 2008r2 on it and further I intend having SQL Server Failover Clustering. VM details are as below:
DC - Domain Controller
SanStorage - MS iSCSI target
Win1 - Primary node in the cluster that will have SQL Server instance
Win2 - Secondary node in the cluster that will have SQL Server instance.
The laptop has 1 Qualcomm network adapter (generally used for connecting Lan cable) and a Broadcomm (wifi) adapter. I intend setting up three virtual adapters
First for regular communication
Second for Data (SQL Server Data to be stored on SCSI)
Third for HeartBit
Normally, (on my laptop) I connect to internet using Broadcomm (Wi-Fi) and want to ensure that whenever needed:
Run this lab even when Lan or wifi is NOT connected. If one of them is mandatory then even that could be the option.
I should be able to use internet within all VMs as well- though this is good to have requirement.
Internet needs to be available on laptop at least. Even if it is unavailable in VMs that is ok.
Now the actual problem.
I DON'T KNOW how many virtual internal/external/private switches to be
defined and assigned to individual VMs. What should be the IPs, Subnets, DNS, Gateways defined on those?
I was able to setup the stuff up-to certain extend and then it stopped working for unknown reasons. I have VMs ready. Next what should I do? Steps...
setup network adapters in each VM
setup DNS on DC
Add remaining 3 VMs in domain
Define Win1 and Win2 as cluster
Configure Target
Configure initiators and access the target
e. Install SQL Server
Is above correct?
My queries probably demands a separate article. But I have already referred many articles and couldn't figure it out so posting it here. I sincerely request your help!
PS – Even after disabling firewall (with and without having DNS setup) I am unable to ping VMs from each other.
Regards,
ThingToLearn
Thanks, Pravin

Hi,
You need create another guest vm as the NAT device, attach the NAT external to the Wifi adapter or cable adapter, then you can set all your vms in internal network
vswitch.
The related third party article:
Using Wireless with Hyper-V
http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx
Hope this helps.
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
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.

Oracle 11.1.0.7 x64 to SQL Server 2008 connectivity

Hi There,
I'm trying to establish connectivity between oracle database running 11.1.0.7 64bit on windows 2008 server x64 to sql server 2008 database. Both databases (oracle and SQL) are on the same machine.
I know with the older oracle versions, we used to setup hs connection between the two databases, however, I've been reading note 466225.1 (How To : How to Setup DG4ODBC (Oracle Database Gateway for ODBC) on Windows 32bit) on metalink and it states the following:
>
Please be aware:
- DG4ODBC is first ported to 64bit Windows platforms starting with 11.2. Using a 32bit DG4ODBC on a 64bit Windows operating system is NOT certified.
- HSOLEDB is no longer available for 11g on Windows.
>
So, according to the above, I'm guessing that we won't be able to use dg4odbc to establish the connectivity between the two.. how about the old hsodbc setup under ORACLE_HOME\hs\admin ? would that work? or is there another way that w can do this?
I've been working on this and trying to get it going but not sure if I'm doing something wrong or it just doesn't work here..
On the server I did the following:
1. created the sqlserver DSN and tested the connection and it's all ok.
2. added the following to the tnsnames.ora
SQLCentralODBC =
(DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=188.87.135.90)(PORT=1522))
    (CONNECT_DATA=(SID=SQLCentralODBC))
    (HS=OK)
) 3. added the following to the listener.ora:
LISTENER_ELMSCENTRAL =
(ADDRESS_LIST=
      (ADDRESS=(PROTOCOL=tcp)(HOST=188.87.135.90)(PORT=1522))
SID_LIST_LISTENER_SQLCENTRAL=
(SID_LIST=
      (SID_DESC=
         (SID_NAME=SQLCentralODBC)
         (ORACLE_HOME=C:\oracle\product\11.1.0.7)
         (PROGRAM=hsodbc)
)4. the listener started ok, and I validated the dsn connection and it's all ok:
C:\Users\oracle>tnsping SQLCentralODBC
TNS Ping Utility for 64-bit Windows: Version 11.1.0.7.0 - Production on 21-MAY-2010 15:47:12
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Used parameter files:
C:\oracle\product\11.1.0.7\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=188.87.135.90)(PORT=1522)) (CONNECT_DATA=(SID=SQLCentralODBC)) (HS
=OK))
OK (10 msec)
C:\Users\oracle>5. created the db link:
SQL> create database link LM_SQLC connect to sqlc_user identified by xxx using 'SQLCentralODBC';
Database link created.6. Test the connection:
SQL> select * from event@LM_SQLC;
select * from event@LM_SQLC
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from LM_SQLC
SQL>Any ideas/help will be really appreciated.
Thanks alot.
Edited by: user4415740 on May 21, 2010 12:36 PM
Edited by: user4415740 on May 21, 2010 12:52 PM

They say "Using a 32bit DG4ODBC on a 64bit Windows operating system is NOT certified." but we do it extensively and it works just fine. You need to install a 32-bit home and create a listener for the 32-bit gateway. Only downside (aside from maintaining 2 homes) is that if you need to file an SR, you must prove that you're able to reproduce the problem when the gateway is running on a 32-bit OS. We keep a little 32-bit server around for this purpose and point our gateways to that box to reproduce issues for SR's.
If you want to run "certified" all the time, you could leave the gateways running in Production on a 32-bit OS, but it runs considerably slower this way, and all because Oracle won't support your SR's. You have to decide if you really think you'll hit an issue that wouldn't reproduce on the true 32-bit OS and decide if it's worth the risk. We've made our decision...
Good luck!

Compatibility_level on SQL Server 2012 in-place upgrade

Hi all,
Based on BOL, master and user databases' compatibility_level will not be changed to 110 on SQL Server 2012 in-place upgrade.
Database Compatibility Level After Upgrade
The compatibility levels of the tempdb,
model, msdb and
Resource databases are set to 110 after upgrade. The
master system database retains the compatibility level it had before upgrade.
If the compatibility level of a user database was 90 or 100 before the upgrade, it remains the same after upgrade. If the compatibility level was 80 or less before upgrade, in the upgraded database, the compatibility level is set to 90, which is the
lowest supported compatibility level in SQL Server 2012.
I get the some result in our environment. So in-place upgrade SQL 2008 instance to SQL 2012 (both standalne and clustered), master/user databases' compatibility_level is 100. I also try to use SQL 2012 new function
OFFSET and FETCH, it works.
My concern is, whether we have to manually update the compatibility_level to 110? As SQL 2012 new features seem work even with compatibility_level <110, is there any problem if we leave it?
(I didn't find any document about this, and related change metioned as a step for SQL 2012 in-place upgrade.)
Any thoughts?
MCSE:Data Platform

So the idea is that if you have applications that are dependent on behaviour that changes, you can stay with the old compat level. I believe that there is some upgrade assistant to investigate whether this applies to you.
On the top of my head, I don't recall any differences between compat levels 100 and 110, but there surely are some. But there are no new reserved keywords as I recall. And some things break even with the old compat level. (COMPUTE BY and the old RAISERROR
syntax for instance.) So I don't think it is particularly brave to change the compatibility level. Change it back if something really breaks.
The risk if you don't change it now, is that you have code developed on a dev server with compat level 110, which breaks when you deploy in production. And this happens one year from now, and no one recalls that this server has compat level 100, so it
causes a lot of confusion and waste of time.
Erland Sommarskog, SQL Server MVP, [email protected]

How to present SAP R/3 data in SQL Server 2005 Reporting service?

Our company is using SharePoint Portal Server 2003 as our intranet. We are also using SAP R/3 4.6C to run their business. There are huge amount of important data in SAP database. There ere are business needs to present SAP data on SharePoint pages which are easier and more friendly to be accessed by users.
The top concern for IT people to meet this challenge is DO NOT CHANGE/UPGRADE THE EXISTING SAP SYSTEM which is so far run smoothly and stably. We cannot accept any risk to make big changes on SAP. and now we want to adopt the Microsoft SQLServer 2005 BI Solution. the most challenge is the ETL part.how to extract the data from SAP R/3 Data base to the SQL Server Data warehouse?
any suggestion or comments is welcome!

Hi
1.if you use web templates you can post the URL in share
point very easily.
any web developer will do that for you in 2 min.
2.this is a more chalanging issue.
the main issue is exacly as you defined it - the ETL.
the main advantage of BW over most BI tools is its
connectivity to SAP R3 and CRM.
But still there are many way's to extract data out
of any SAP sys and in R3 the data model makes it quite
easy.
In CRM its much more complicated because of the much
more complex Data Model.
Here are a few way's to extract data from SAP:
- olap bapi
http://help.sap.com/saphelp_bw33/helpdata/en/64/9b8f3c855f0454e10000000a11405a/frameset.htm
- odbo - vb/.net/c sharp
'connecting to sap bw using vb and ado md'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee19e9c7-0301-0010-8f84-97e3f6d7b5a6
'connecting to sap bw with excel and odbo'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a06a51f3-0201-0010-8591-b742cfafd267
'odbo'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7f88b390-0201-0010-ae94-fdfd42b13407
'sap .net connector' (seems old version)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb4dc990-0201-0010-429a-bf43852a6895
.net connector
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5a04426d-0601-0010-5e99-aeea1cd4aa81
'Access SAP BW ODS BAPI Using C-Sharp and SAP .NET Connector 2.0' doc can be download here
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/12f6d390-0201-0010-e18d-cdb4554a9e75
Reg's
Edan

Split TempDb in SharePoint 2010 Sql Server DB

Hi ,
We have envirenment of sharepoint farm,one Database server.We have plan to split tempDb acording microsoft best practices.
By the time of we have the largest content database is 260 in size and SQL Server has a 2-core processor.
So the tempdb would be split in two files with 40 GB per .mdf file.
Kinldy suiggest hopw to split TempDb.
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

Hi Shanky,
We are not facing any issue,But we had take Micorosft RaaS services,Microsoft Consutlatan suggest thet we should break oure TempDb
RaaS ISSUE/RISK
Initial Size of Temp DB is too small
TempDB database Size may be too small.
SQL Server instance has only one tempdb data file while there are more than one scheduler in use
One or more user database files are placed on same disk volume along with TempDB database files
REMEDIATION COMMENTS
The size and physical placement of the tempdb database can affect the performance of a SharePoint farm. For example, if the size that is defined for tempdb
is too small, part of the system-processing load may be taken up with autogrowing tempdb to the size required to support the workload every time you restart the instance of SQL Server. You can avoid this overhead by increasing the
sizes of the tempdb data and log files.
Currently .mdf and .ldf files are in the D volume along with all other SharePoint databases and there is just one tempdb .mdf file.
More information:
http://technet.microsoft.com/en-us/library/ms175527(v=SQL.105).aspx
ACTION PLAN
Set the recovery model of tempdb to SIMPLE recovery model.
Create as many files as needed to maximize disk bandwidth. Using multiple files reduces tempdb storage contention and yields significantly better scalability. However,
do not create too many files because this can reduce performance and increase management overhead. As a general guideline, use
# of TempDB Files = # of Processors Cores / 4 and then adjust the number of files up or down as necessary.
Preallocate space for all tempdb files by setting the file size to a value large enough to accommodate the typical workload in the environment. You can go by a rule
of thumb that the size should be 25% of the largest SharePoint content database.
Important: Make each TEMPDB data file the same size.
Allow your TEMPDB files to grow automatically and monitor the disk free space, set the file growth in fix size and not in percentage. We recommend the following
general guidelines for setting the FILEGROWTH increment for tempdb files:
tempdb file size from 0 to 100 MB - FILEGROWTH increment in 10 MB
tempdb file size from 100 to 200 MB - FILEGROWTH increment in 20 MB
tempdb file size from 200 MB or more - FILEGROWTH increment in 10%*
* The FILEGROWTH increment should be set to a maximum of 6 GB, regardless of the tempdb file size.
Put the tempdb database on a fast I/O subsystem. Use disk striping if there are many directly attached disks.
Put the tempdb database on disks that differ from those that are used by SharePoint.
Important: This action plan requires a downtime of your SharePoint
farm as you will have to stop SQL Server services to move data and transaction log files to different disks.
By the time of this remediation the largest content database is 300 in size and SQL Server has a 2-core processor. So the tempdb would be
split in two files with 40 GB per .mdf file.
STATUS
SharePoint administrators will work on the action plan.
Downtime required for to apply this action plan? YES
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

SharePoint 2013 + SQL Server 2008 vs 2012

I am trying to determine the best course of action when building a new SharePoint 2013 Enterprise Farm. Should we use SQL Server 2008 R2 or SQL Server 2012? I have found some information online, but I wanted to know if there were more pros and cons to SQL
2012 over 2008. Can anyone tell me if my short list is adequate enough? Also, are there any integration concerns with other applications that I may need to look out for by using SQL 2012 that don't exist in SQL 2008?
The list of benefits of SQL 2012 over SQL 2008 I know of include:
AlwaysOn
Read-Only Secondary
Contained Database
ColumnStore Indexes
Shredded Storage
PowerPivot BI
Reporting Services BI
Are there any negatives to using SQL 2012?
Thanks,
Alex

Alex,
The only negatives I have seen are
1. You must be careful that the AOAG configuration is supported. For many cases like the config DB, Async mode is not supported for DR.
2. Microsoft has not published their support stance for Many DBs yet.
So for example for "App Management Service Application" DB or "Secure Store" DB Microsoft says
To be determined. Currently not supported because testing is not finished.
For a complete list look here
http://technet.microsoft.com/en-us/library/jj841106.aspx
So although AOAG is a great option technically (and perhaps in the long run the strategic option) I would like Microsoft to complete their testing. (unless one is ready to take risk and go where MS itself hasn't gone)
val it: unit=()

Best way to migrate SharePoint 2003 data into SQL Server 2008

Hi Experts,
I am planning to migrate data from SharePoint 2003 into SQL Server 2008. After the migration SharePoint site will be deleted in couple of months and then that data will be feed into .Net Front end application
1) What is the best and easy way to do it?
2) Is there any way to automate the migration process? i.e. If a new record gets entered into SharePoint it should be populated into SQL Server 2008.
3) Any other suggestions
Thanks,
John

Dear John,
If it's just a few lists, and you just want to import them "as-is" then it should be possible to do so ... and survive to tell the about it ;-)
Generally speaking, You will need to write a small process (program or script) to read/parse each list and check if the item(s) are in the target table (I assuming that there is a distinct table as target
for each list, and that each list has 'something" you can use to distinct each row), if it's not there, the just add them according to your needs.
Then just rerun the process periodically and it would keep your databases up to date (you could even set ti up to update those records that have changes, but that would delay your process significantly)
What i just described is doable, and not TOO complicated, it could be done i a lot different ways, and with different alternatives of programming/scripting languages. for sure you can do it in any flavor
of .net language, and even powershell.
As I mentioned, this is speaking in general, the actual implementation would depend on your specific needs and the kind of data that you have/need to keep.
Best Regards / Saludos, Marianok
Disclaimer: This post, and all included code and information is provided "AS IS" with no warranties or guarantees and confers no rights. Try it at your own risk, I take no responsibilities.
Aclaración: Esta publicación, y todo en código e información en la misma, es provista "AS IS" / "Como Está" sin garantía alguna y no le confiere ningún derecho. Pruebelo su propio riesgo. No asumo responsabilidad alguna.

Error in CLR assembly after migrating to SQL server 2012

We moved to SQL Server 2012 from 2008R2 and I am unable to get the CLR assembly working. I have read several topics about trustworthy setting and a mismatch dbo SID. I checked the SID and everything looks good and the 2008R2 server works fine with
Trustworthy set to OFF. I'm starting to think it is a .NET issue. 2008R2 works with 2.0 and 2012 uses 4.0 and i'm wondering if just redeploying the assembly will fix the problem. Any suggestions would be greatly appreciated.
Msg 10314, Level 16, State 11, Procedure MP_ExportXYToCSV2, Line 41
An error occurred in the Microsoft .NET Framework while trying to load assembly id 65540. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation
to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly 'exporttocsv, Version=1.0.4780.25878, Culture=neutral, PublicKeyToken=f5567e386ca8280d' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
System.IO.FileLoadException:
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)

It is not clear what you have done, for an assembly with a permission set beyond SAFE to work, one of these conditions must be set:
1) The database is trustworthy and the database owner has EXTERNAL ACCESS ASSEMBLY or UNSAFE ASSEMBLY permission, depending on the permission set for the assembly.
2) The assembly is a signed with a key, and that key exists in the master database. A login has been created from the key, and this login has been granted the matching assembly permission.
Since you say that it worked on SQL 2008 R2 without trustworthy, I would assume that you had a key-login pair on the old server, but forgot to move them to the new server.
Don't set the database trustworthy. This is a potential security risk.
Erland Sommarskog, SQL Server MVP, [email protected]

Risks in SQL Server

Similar Messages

Maybe you are looking for