SQL Azure Administration Tool

Are there any web-based admin tools to develop my Azure SQL database with?  I have downloaded the SQL 2012 Express Management Tools, but cannot connect to my Azure SQL Database server with them because port 1433 is blocked.
This seems to be a common problem, but so far I have found no way to connect to my database.  My 30 day trial ends in 29 days and I'm hoping to get this resolved before day #30.  :-)
The SQL Azure Labs I downloaded from the Azure website talk about a tool in the Azure Portal, but I cannot find anything there.  Everything just points to downloading the SQL 2012 Management Tools.
Thanks,
Brian

You can use the database management tools in the Portal to create tables and run T-SQL. Granted, it is not as convenient as SSMS but it will do the job very nicely. 
Patrick Wood,
Founder, Gaining Access Technologies http://gainingaccess.net/

Similar Messages

  • SQL Server Config Manager, Windows Administration Tools, Manage Computer and Task Manager

    I want to cross check the
    SQL Server Config Manager, Windows Administration Tools, Manage Computer and Task Manager
    for running of SQL SERVER.
    I stop SQLEXPRESS instance in one of the above tools but the others become unaware of the latest changes except
    Task Manager.
    For example when I stop SQL EXPRESS from within SQL Server Congiguration Manager
    it still seems working in Windows Administration Tools, Manage Computer windows.
    What is the reason for this?

    Hi,
    Aprat from SQL Server configuration manager all other are windows tool and should not be used to manage SQL Server in anyway. Although I cannot completely understand list of tools you mentioned
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Is there any Tools for Code coverage for SQL Azure Database projects

    I need to capture data base code coverage for all the manual and automated test. this is for Azure DB, is there any tools available for the same? Please advise

    Hi,
    In order to code coverage for SQL Azure, use Microsoft Test Manager.
    This Link helps you in understanding and step by step procedures for manual testing.
    http://msdn.microsoft.com/en-us/library/vstudio/hh698492(v=vs.110).aspx
    Along with the above link also refer to
    http://msdn.microsoft.com/en-us/library/jj156172.aspx
    http://msdn.microsoft.com/en-us/library/jj156144.aspx
    Girish Prajwal

  • The February 2015 release of SQL Server Data Tools is now available for download

    We'd like to announce the availability of the latest February 2015 release of SQL Server Data Tools.
    This update is now available for Visual Studio 2012 and 2013. For Visual Studio 2012, use the SQL > Check for Updates tool inside Visual Studio. For Visual Studio 2013, check the Visual Studio update channel (Tools > Extensions and Updates > Updates)
    for this update.  Alternatively, administrative installs are available via the link below.
    Get it here:
    http://msdn.microsoft.com/en-us/data/hh297027
    What’s New?
    Support for the latest Azure SQL Database V12 features
    Improved Cross-Platform Schema Comparison
    New advanced publish options
    Fixes for customer reported issues
    For more details, see the SQL Server Data Tools team blog:
    http://blogs.msdn.com/b/ssdt/archive/2015/03/03/sql-server-data-tools-and-data-tier-application-framework-update-for-february-2015.aspx

    While we are investigating this issue, you can revert to the November release with the links below.  You will need to uninstall your current SSDT.MSI and then run the installer from these ISOs.
    Visual Studio 2012 versions:
    SSDT_11.1.41025.0_BR.iso
    SSDT_11.1.41025.0_CN.iso
    SSDT_11.1.41025.0_DE.iso
    SSDT_11.1.41025.0_EN.iso
    SSDT_11.1.41025.0_ES.iso
    SSDT_11.1.41025.0_FR.iso
    SSDT_11.1.41025.0_IT.iso
    SSDT_11.1.41025.0_JA.iso
    SSDT_11.1.41025.0_KO.iso
    SSDT_11.1.41025.0_RU.iso
    SSDT_11.1.41025.0_TW.iso
    Visual Studio 2013 versions:
    SSDT_12.0.41025.0_BR.iso
    SSDT_12.0.41025.0_CN.iso
    SSDT_12.0.41025.0_DE.iso
    SSDT_12.0.41025.0_EN.iso
    SSDT_12.0.41025.0_ES.iso
    SSDT_12.0.41025.0_FR.iso
    SSDT_12.0.41025.0_IT.iso
    SSDT_12.0.41025.0_JA.iso
    SSDT_12.0.41025.0_KO.iso
    SSDT_12.0.41025.0_RU.iso
    SSDT_12.0.41025.0_TW.iso

  • Error connecting SQL Azure - Network access for Distributed Transaction Manager (MSDTC) has been disabled

    Sometimes I have an error connecting SQL Azure. The error occurs in an asp.net application and in a windows service running on VM in Azure. Error details:
    System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network
    access in the security configuration for MSDTC using the Component Services Administrative tool. ---> System.Runtime.InteropServices.COMException: The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT:
    0x8004D024)
       at System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction(UInt32 propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier, Guid& transactionIdentifier, OletxTransactionIsolationLevel& isolationLevel,
    ITransactionShim& transactionShim)
       at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
       --- End of inner exception stack trace ---
       at System.Transactions.Oletx.OletxTransactionManager.ProxyException(COMException comException)
       at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
       at System.Transactions.TransactionStatePSPEOperation.PSPEPromote(InternalTransaction tx)
       at System.Transactions.TransactionStateDelegatedBase.EnterState(InternalTransaction tx)
       at System.Transactions.EnlistableStates.Promote(InternalTransaction tx)
       at System.Transactions.Transaction.Promote()
       at System.Transactions.TransactionInterop.ConvertToOletxTransaction(Transaction transaction)
       at System.Transactions.TransactionInterop.GetExportCookie(Transaction transaction, Byte[] whereabouts)
       at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction tx)
       at System.Data.ProviderBase.DbConnectionPool.PrepareConnection(DbConnection owningObject, DbConnectionInternal obj, Transaction transaction)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal&
    connection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
       at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
       at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
       --- End of inner exception stack trace ---
       at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
       at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection()
       at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
       at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClassb.<GetResults>b__9()
       at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
       at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
       at System.Data.Entity.Core.Objects.DataClasses.EntityReference`1.Load(MergeOption mergeOption)
       at System.Data.Entity.Core.Objects.DataClasses.RelatedEnd.DeferredLoad()
       at System.Data.Entity.Core.Objects.Internal.LazyLoadBehavior.LoadProperty[TItem](TItem propertyValue, String relationshipName, String targetRoleName, Boolean mustBeNull, Object wrapperObject)
       at System.Data.Entity.Core.Objects.Internal.LazyLoadBehavior.<>c__DisplayClass7`2.<GetInterceptorDelegate>b__2(TProxy proxy, TItem item)

    Hello,
    I am not an expert in MSDTC but as we know,SQL Azure Database does not support
    distributed transactions. This means that SQL Azure doesn’t allow Microsoft Distributed Transaction Coordinator (MS DTC) to delegate distributed transaction handling.
    One common cause of MSDTC getting involved in Entity Framework applications is the fact that we close and reopen the same connection as needed (i.e. for each query that is executed).To avoid the stack from opening and closing the connection multiple times,
    you can simply open the connection explicitly and run the queries in the same connectio.
    The following thread is about a similar issue, please refer to:
    http://answers.flyppdevportal.com/categories/azure/sqlazure.aspx?ID=d705a8cf-cba4-494c-96f6-96a136bd29e3
    What's more, you can also try the workaround that involves setting the Enlist option of the SQL Azure connection to false. For the detail explanation, please refer to:Entity
    FrameWork and SQL Azure
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • "The CREATE USER statement must be the only statement in the batch" in SQL Azure - why? what to do?

    I'm getting an error on a line in the middle of a larger sql script, only in SQL Azure.
    IF NOT EXISTS (SELECT * FROM sys.database_principals WHERE name = N'foouser')
    CREATE USER [foouser] FOR LOGIN [foouser] WITH DEFAULT_SCHEMA=[dbo]
    GO
    Error: "The CREATE USER statement must be the only statement in the batch."
    I don't actually understand what 'the only statement in the batch' means.
    What is a batch? Is it a SQL file? Is it related to a 'GO' statement or an 'IF' statement? What is the reason for the error? And how do I avoid it?
    Thanks,
    Tim

    >IF...ELSE imposes conditions on the execution of a Transact-SQL statement
    I understand the general purpose of an If statement. I could let go of our definition of statement counting disagreeing too except that because of the error I'm stuck.
    It's less important for Create User but what I am really puzzled over now is a very similar issue how am I supposed to do a safe version of CREATE LOGIN, when I don't know whether a login has been previously created on the server or whether I
    am setting up the database on a clean server?
    IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name = N'foouser')
    CREATE LOGIN [foouser] WITH PASSWORD = 'asdfasdf'
    GO
    If I try and execute this script, it throws the same error as above.
    The first unworkable workaround idea is to omit the if statement
    CREATE LOGIN [foouser] WITH PASSWORD = 'asdfasdf'
    GO
    But if the login already exists on the server (because a similar script was already run), then the script throws an error.
    The second unworkable workaround idea is to do
    DROP LOGIN [foouser]
    GO
    CREATE LOGIN [foouser] WITH PASSWORD = 'asdfasdf'
    GO
    Obviously this throws an error in the second block if the login doesn't already exist on the server.
    The third workaround idea I have is to go conditional by putting an IF condition around DROP instead of CREATE:
    Unfortunately that doesn't work for me either!
    "The DROP LOGIN statement must be the only statement in the batch"
    (This is despite the fact that 'drop login' is listed on the
    supported commands page, not the partially supported page..?! Which disagrees with the notes on
    this page.)
    Anyway the real question I am interesting in addressing is: is there actually a way to have a 'Create/Delete login
    if exists' operation which is SQL-Azure compatible and doesn't throw me error messages (which messes with the sql execution tool I am using)?
    If there is no way, I would like to believe it's because it would be a bad idea to do this. But in that case why is it a bad idea?
    Tim

  • SQL Azure Reporting - There was an exception running the extensions specified in the config file. --- Maximum request length exceeded.

    I am trying to deploy an RDL file (5MB) to SQL Azure Reporting server in South Central US using the deploy function in SQL Server Data Tools but facing the following error during deployment to Azure Reporting server.
    "There was an exception running the extensions specified in the config file. ---> Maximum request length exceeded."
    Is there any limit on the size of RDL files which can be deployed to Azure Reporting server? I have seen some online posts which talk about increasing the maxRequestLength in httpruntime of web.config in Reporting server. But in case of Azure Reporting server
    how can be make modification to this configuration?
    I have tried to upload it directly to SQL Azure Reporting server from the Management Portal --> Upload Report function which still resulted in error.
    Thanks & Regards, Deep

    Thanks for your question. Unfortunately we are in the process of deprecating SQL Reporting services.  Full details are available at http://msdn.microsoft.com/en-us/library/gg430130.aspx
    Thanks Guy

  • SQL Azure: More Intermittent Timeouts

    Hi guys,
    We have a set of 5 online auction systems running on Windows Azure & SQL Azure. Each system consists of a single web worker and one or more web roles. Each system is using ASP.NET MVC 3 and Entity Framework, Repository Pattern and StructureMap.
    The worker role is responsible for housekeeping and runs two groups of processes. One group is run every ten seconds, the other every second. Each process will likely run a database query or stored procedure. These are scheduled with Quartz.net
    The web role serves the public interface and back office. Among other basic crud functionality, both of these provide screens which, when open, will repeatedly call controller methods which will result in execution of stored procedure read-only queries.
    The frequency of repetition is about 2-3 seconds per client. A typical use case would be 5 back office windows open, and 25 end user windows open – all hitting the system repeatedly.
    For a long time we have been experiencing intermittent SQL timeout errors. Three of the most common ones are:
    System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
    System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
    System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    The only predictable scenario is during an auction where a specific controller -> sproc starts to timeout during the event (presumably due to load). All other times the errors appear to be completely random and come in singles, two’s, and three’s etc.
    even during periods of user inactivity. For example the system will go 18 hours without an error and then could be 5 – 10 errors from different housekeeping methods, or perhaps a user logged on and viewed their account.
    Other info:
    I have tried to run the affected queries/sprocs on SQL Azure using both local SSMS and Azure web-based query tool – all seem to execute quickly, 1 second max. Query plans not showing anything too suspicious although I am by no means a SQL query performance
    expert, or any other kind of expert for that matter
    J
    We have wrapped all affected areas in Azure SQL Transient Fault Handling Blocks – but as is discussed here
    http://social.msdn.microsoft.com/Forums/en-US/ssdsgetstarted/thread/7a50985d-92c2-472f-9464-a6591efec4b3, they do not catch timeouts, and according to “Valery M” this is for good reason.
    We are not storing any session information in the database, although asp.net membership information is stored in the database.
    We use 1 “SQL Azure server instance” which hosts all 5 databases, two for staging and three for production. All 5 systems are generally active at the same time although it is unlikely that more than one will be in a state of live load use at any given time.
    All web roles, worker roles and the SQL Azure server reside in the same Azure Geographical Region.
    Any thoughts on where we should be looking? Would it help giving each system it's own SQL Azure server? ... Failing a solution by ourselves - is it possible to get Microsoft to open a support ticket and take a look under the hood at what’s going on in with
    our application – how does one go about this?
    Thanks in advance.
    Ilan

    Ditto.
    New website/database (has only been in production for a week or so). The model we have is pretty simple Azure website MVC EF 6.1.1 using a single database in same region as website. I have monitored for and have never found any throttled connections or deadlocks.
    What I have tried so far
    I bumped the timeout in the connection string to 60 seconds
    I changed the web site to Basic and configured the auto scale to max instance size and count
    That seemed to help - but then just recently during points of high volume usage (client requests, data in and out, CPU time) I started seeing this error. As I narrow the focus to look at metrics during the exact time of the error it doesn't reflect
    the exact peak. For example peak usage may be at 3:45, but the errors occur at 4:30 when the usage is less than 3:45 by a fair amount.
    To try to force recreate and see if it was caused by transaction data table locks I ran a query in a transaction block with a WAITFOR delay and then went to the web site and tried to access data that would be locked by that query. That test did generate
    an error - but not this specific "semaphore timeout period has expired" - so I don't think it is caused by table locks.
    I did notice that when the error happens - it generally happens to one user and then happens multiple times to that one user over the course of what can be a minute or so and in different queries (views). The last analysis showed that pattern for
    one user with 2 other users getting the error but just once (and in different views/queries).
    USER A - got about 9 of these errors in about 8 different views over the course of a little more than a minute (20:26 to 21:35)
    USER B - got 1 (in the same timespan)
    USER C - got 1 (in the same time span)
    Analysis of the error logs showed it isn't unique to any single view/query or scenario wrt queries. The only clue that makes it less of an intermittent situation is does correspond with usage. However, it doesn't have to be specifically peak usage at the
    exact moment - but in a window (within an hour), It makes me wonder if it is the load or just the fact that more usage just increases the odds (I will monitor this relation some more and note the exact metrics). 
    I am now bumping the timeout in the connection string to 90 seconds and I have changed the database DTU setting to 50

  • Mangage SQL Azure is not working

    Hi Azure team,
    I have installed Google chrome in my laptop, but i cant open sql azure using management portal in azure.
    I verified silver light is enabled in chrome.
    Kindly let me know what will be the issue and how to open SQL azure from manage portal ?

    Hi Saravanabharathi,
    According to your description, you could not open SQL Azure via Windows Azure Platform Management Portal in Google chrome. In theory, because the Windows Azure Platform Management Portal
     is built on Silverlight, you can view, monitor and manage the exposed aspects of SQL Database with any browser using the web management tool.
    You need to first sign in with the Windows Live ID that you’ve associated to your Windows Azure account. You can post error message or detail for analysis. Or
     I recommend you try to open the Management Portal by using Internet Explorer (IE) 10.0 or higher version of IE. By default, Internet Explorer displays automatically pop-ups that appear as a result of you clicking a link or button.
     Now, to reach the new management portal, you need go to:
    http://windows.azure.com .
    For more information about using  the Database Manager from the Management Portal, you can review the following articles.
    http://blogs.msdn.com/b/sqlazure/archive/2010/12/01/10099203.aspx
    https://social.technet.microsoft.com/wiki/contents/articles/4723.getting-started-with-windows-azure-sql-database-development.aspx
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SQL Server Management Tools - Could not write value to key \SOFTWARE. Error code: 1406

    Detailed Results:
    Feature: Management Tools-Basic
    Status: Failed
    Component Name: Sql Server Management Studio
    Component Error code: 1406
    Error Description: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
    The first time the installer worked installing perfectly, but I needed an named instance of "SQL2008", so I removed the instances. After this re-installing is not working.
    From past 3-4 days I went through most of the links which has provided solutions for error code 1406, and not having success for installing.
    I have tried these options,
    1) Ran the installer using "Run as Administrator"option. I am an Administrator user for the machine.
    2) In Registry Editor, right-click HKEY_CURRENT_USER\Software, and then click Permissions. Click Add, type Everyone, and then click OK. Under Group or user names, click Everyone. Under Permissions, click to select Full Control in the Allow column, and then
    click OK.
    3) Uninstalled the Sql server product, and used Revo Uninstaller / CCleaner to clean the registry and the remaining files and folders.
    4) Multiple versions of SQL installers have been tried (SQL 2008/2012/2014)
    5) Logged in as local/Administrator for the machine, tried the similar steps.
    6) The same installers are still working in one of the virtual machines for multiple times of installation and uninstallation without having any problems.
    Please let me know, if needed further information. Please provide help for installing SQL server management studio.
    Regards,
    Ananth.

    I have the same problem.
    I can not install MSSQLManagementStudio. I suppose
    that is not the fault of permissions
    . I have tried to
    install as an administrator
    on the computer in the domain where the account has domain administrator permissions.The account is added to the local administrators.
    I also have tried to install as local administrator
    account after the removal of the domain.
    With the same result.
    Operating System Windows 8.1 Prof.
    I have tried  2012, 2012with SP1 , 2012x86 , 2014. All with same result:
    Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value  to key \SOFTWARE.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    Other elements installs without any problem.
    sql_ssms_Cpu64_1.log show that the problem is in that point:
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup,,BinaryType=0,,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=SqlToolsPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=Path,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=SQLPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(,,)
    MSI (s) (1C:C0) [10:32:51:834]: Note: 1: 1406 2:  3: SOFTWARE 4: 5
    MSI (s) (1C:C0) [10:33:19:949]: Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value  to key \SOFTWARE.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    Error 1406. Could not write value  to key \SOFTWARE.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    07/30/2014 10:33:19.949 [540]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    ...... rest of the roolbaack next
    As i the lines:
    MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
    MSI i opening the root hive of HKLM/Softftware
    and MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(,,)
    and trying to Add Default Value.
    What is impossible regardless of the
    level of permissions.
    Please provide help for installing SQL server management studin in any version
    Regards,
    Michael

  • Administration Tool Cache vs. Cursor Cache

    Hi everyone,
    Someone asked me what's the difference between the cache in the administration tool ( Manage->Cache) versus cursor cache (Settings -> Administrator -> Manage Sessions), and even though I've cleared them both many-a-time, I still am not sure the difference.
    Can someone explain to me the difference between the two?
    Thanks!
    -Joe

    Hi,
    The cache in the administration tool is a file based cache on the OBIEE server which stores the results of database requests. This means that if a user makes a request the OBIEE server first checks the cache to see if the query has already been run and cached, or if a superset of the query has been run and cached (i.e. a less restrictive query that the current query can be satisfied from). If it finds there is a cache entry then it will return the results from here instead of issuing any SQL to the database, thereby speeding up getting the results back to the user.
    The cache shown in the cusrsor cache is the cache on the presentation server, this is a cache of the content which is being returned to the user's browser, this means if the user goes back to see results for a query they have already made then the presentation server can just return the same content to them without even having to go to the OBIEE server again at all.
    So basically 2 levels of caching, one on the OBIEE server and one on the presentation server.
    Regards,
    Matt

  • Cannot connect to SQL Azure

    Hello,
    I have tried everything I could think of and still did not manage to connect to SQL Azure server instance I have created.
    1) Using the SQL Server Management Studio 2008 R2 -
        I get: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.  ...."
        I have the 1433 port allowed by my firewall (even placed a machine in the DMZ) and I have added my IP address to the SQL Azure firewall.
    2) Using this app: https://onlinedemo.cerebrata.com/SQLAzureClient/default.aspx
       I get "Unable to retrieve the list of databases...."
       Now, in this case enabling the TCP port 1433 from my network is not even required as I this tools connects directly to SQL Azure. And yes, I have added the firewall rule on my SQL Azure Server.
    3) Using this tool: http://hanssens.org/tools/sqlazuremanager/
       I get a message similar to what I get at 1)
    The only thing that works is the "Test Connection" performed on SQL Azure site.
    Can someone please help?
    Regards,
    Luc

    I cannot connect either using that Omega tool but I have no problem from SSMS R2.
    Let's try something simple: connecting from Project Houston:
    Check "Allow Microsoft Services access to this database"
    Go to http://sqlazurelabs.com. Click Project Houston CTP 1 on left.
    When asked for data center, click the one where your db is deployed.
    Agree to terms
    Enter full database name - somename.database.windows.net -
    along with database name, username, and password. Note: if you didn't allow Microsoft Services access to your database, you'll get an error
    You should now be connected to your database.
    If that worked, at least you know your database is up and running correctly. Now try connecting from SSMS R2. The parameters should be identical,
    except you don't have to specify which database to connect to.

  • I'm unable to create a new Table on SQL Azure.

    I'm trying to create a new table in my custom database. But i'm getting this error message:
    'Filegroup reference and partitioning scheme' is not supported in this version of SQL Server.'
    Here is the sample create schema:
    CREATE TABLE dbo.[Contact](
    [ID] [int] IDENTITY(1,1) NOT NULL,
    [FirstName] [nvarchar](250) NULL,
    [LastName] [nvarchar](250) NULL,
    [InsertDateTime] [datetime] NULL,
    [UpdateDateTime] [datetime] NULL,
    [PhoneNo1] [nvarchar](50) NULL,
    [CellNo1] [nvarchar](50) NULL,
    [IsActive] [bit] NOT NULL,
    CONSTRAINT [PK_Contact] PRIMARY KEY CLUSTERED
    [ID] ASC
    )WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
    ) ON [PRIMARY]
    GO
    BT

    In addition to Neil's comment, I would add that one of the major strengths of SQL Azure is its simplicity from an administrative standpoint while providing as much parity as possible for the relational and programming stack.  In somes
    cases, less is more. SQL Azure is an example.  By having a simpler system we are able to get certain capabilities not available on premise. Take a look at the CREATE DATABASE XYZ AS COPY OF operation for example, you do not have to worry about finding
    a server with enough space; you do not have to worry about moving files around a network or creating shares between machines; and best of all, you do not have to any kind or provisioning of cleanup as a result of cloning a database. The upcoming Data Federation
    feature is another example of what you can achieve when you are free of underlying configuration details.
    That's not to say SQL Azure wouldn't benefit from some capabilties of the SQL Server platform (for example TDE); but personally I am happy that two years later we still don't have to worry about many of those low-level configuration details.
    Herve Roggero, Blue Syntax MVP SQL Azure Co-Author: Pro SQL Azure

  • Cannot view data on physical layer on Oracle BI administration tool

    Hi everyone
    I have a schema1 and table1, table2, table3.
    I have connect in odbc using the schema username and password and it was successful.
    I can view the data using toad and sql oracle developer with schema username and password.
    I also import the tables in Oracle BI administration tool with my schema username and password.
    But my problem is i cannot view the data on the table in physical layer using my schema username and password.
    Please help,
    Thanks in advance
    Edited by: hanson on Sep 16, 2009 7:15 AM

    Hi,
    I'm confused about the last bit, you did a database import to get the tables into the RPD, which worked, but now they are not showing in the phsyical layer of the rpd? They should be there under a database with the name of the ODBC/OCI that you used when you imported them.
    If they are not there then this would make me think that the import of the tables has not worked, try importing just one and see what happens.
    Regards,
    Matt

  • How to Restore ".bak" file in Sql Azure...

    I'm new in windows azure. I have taken db backup from my local machine. how to restore database backup(.bak) in sql azure.

    Hello,
    You can't restore a backup file to SQL Azure; you don't have any file access to Azure and there is no such a restore option in SQL Azure.
    If you have the database on a on-premise SQL Server you can deploy it from your server to SQL Azure, there are several tools available for it.
    See e.g.:
    Data Migration to Windows Azure SQL Database: Tools and Techniques => From SQL Server
    Migrating a Database to SQL Azure using SSDT
    SQL Azure Deployments
    Olaf Helper
    Blog
    Xing

Maybe you are looking for