Search Results

Search found 29121 results on 1165 pages for 'sql 2000'.

Page 36/1165 | < Previous Page | 32 33 34 35 36 37 38 39 40 41 42 43  | Next Page >

  • SQL 2000 - Returning from a Stored Procedure

    - by user70192
    Hello, I'm writing a stored procedure. This procedure has a case where if it is met, I want to stop executing the procedure and return -1. How do I do this? Currently, I'm trying the following: IF @result <> 1 BEGIN SELECT -1 END However, SELECT is not a typical "return". As you can imagine I spend most of my time in code which is why i'm looking for something like a "return". Thank you,

    Read the article

  • How to Delete Duplicate Rows in SQL 2000?

    - by Mikecancook
    I thought I had this figured out but it turns out I'm just deleting the first record. The following returns the duplicate rows. All have a count of 2. I just want to delete the first one for each duplicate record. select scorestudentid, scoreadvisor, scorecorrect, count(*) from scores where scoretestid = 3284 group by scorestudentid, scoreadvisor, scorecorrect having count(scorestudentid) > 1 Which returns: scorestudentid scoreadvisor scorecorrect no column name 13033719 28059 3.0 2 13033777 28086 3.0 2 13033826 28147 3.0 2 13033960 28023 3.0 2 So I put this together thinking it would work: set rowcount 1 delete from scores where scoretestid = 3284 and scorestudentid in ( select scorestudentid from scores where scoretestid = 3284 group by scorestudentid having count(scorestudentid) > 1) It really seems like it should be a simple concept but I'm not getting it.

    Read the article

  • updating only date part from datetime in sql server 2000

    - by user294146
    hi Experts, I have data in the table like the following. col1 col2 col3 -------------------------------------------------------- 6/5/2010 18:05:00 6/2/2010 10:05:00 Null 6/8/2010 15:05:00 6/3/2010 10:45:00 6/5/2010 11:05:00 6/3/2010 15:05:00 Null 6/7/2010 12:05:00 6/1/2010 15:05:00 6/3/2010 10:45:00 6/1/2010 14:05:00 what my requirement is I want to update the date of there columns with single date without disturbing the time. say for example I want to update the table data with 6/1/2010 where the field data is not null. please let me know the query for updating the table data. thanks & regards, murali

    Read the article

  • Dynamically changing databases in SQL Server 2000

    - by spuppett
    At work we have a number of databases that we need to do the same operations on. I would like to write 1 SP that would loop over operations and set the database at the beginning of the loop (example to follow). I've tried sp_executesql('USE ' + @db_id) but that only sets the DB for the scope of that stored procedure. I don't really want to loop with hard coded database names because we need to do similar things in many different places and it's tough to remember where things need to change if we add another DB. Any thoughts Example: DECLARE zdb_loop CURSOR FAST_FORWARD FOR SELECT distinct db_id from DBS order by db_id OPEN zdb_loop FETCH NEXT FROM zdb_loop INTO @db_id WHILE @@FETCH_STATUS = 0 BEGIN USE @db_id --Do stuff against 3 or 4 different DBs FETCH NEXT FROM zdb_loop INTO @db_id END CLOSE zdb_loop DEALLOCATE zdb_loop

    Read the article

  • SQL Server connection error (a weird one) (unsolved yet)

    - by Pinchy
    SQL Server can be connected from local system but can not be connected from remote system in the network. The error code is 40 from Visual Studio and 1326 when I try to connect to SQL Server from Management Studio. Firewall isn't the problem TCP/IP connection is enabled from SQL Server There are 2 pc terminals that can connect to the SQL Server but the 3th one cannot and using the same connection strings so the connection string is right It is SQL server 2000 any help will be appreciated thanks

    Read the article

  • Possible DNS issue after a reinstall of Windows Server 2000 (get off my lawn)

    - by cop1152
    I just replaced a drive on a Win2000 Server that replicates AD and issues out DHCP at one of our offices. I successfully joined it to the domain, setup range of IP's, etc, but am still having issues. I cannot RDC to it with name or IP. I can ping it, browse to it with Windows Explorer, and remote to it with some other software, but not RDC. The other issue is this: Users are unable to authenticate on it. They receive the message 'username or password incorrect' (or something like that). Changes made on the main domain controller seem to take forever to trickle down. The most significant entry in the DNS Server Log is Event ID 7062: The DNS Server Encountered a Packet Addressed to Itself. At least, I think its significant. The Directory Services Log shows numerous Event IDs 1265: The attempt to establish a replication link with parameters failed with the following status: The DSA operation is unable to proceed because of a DNS lookup failure. Does this make any sense to anyone? I feel like its something very simple that I am overlooking. Thanks in advance.

    Read the article

  • T-SQL Tuesday #005: Creating SSMS Custom Reports

    - by Mike C
    This is my contribution to the T-SQL Tuesday blog party, started by Adam Machanic and hosted this month by Aaron Nelson . Aaron announced this month's topic is "reporting" so I figured I'd throw a blog up on a reporting topic I've been interested in for a while -- namely creating custom reports in SSMS. Creating SSMS custom reports isn't difficult, but like most technical work it's very detailed with a lot of little steps involved. So this post is a little longer than usual and includes a lot of...(read more)

    Read the article

  • T-SQL Tuesday #005: Creating SSMS Custom Reports

    - by Mike C
    This is my contribution to the T-SQL Tuesday blog party, started by Adam Machanic and hosted this month by Aaron Nelson . Aaron announced this month's topic is "reporting" so I figured I'd throw a blog up on a reporting topic I've been interested in for a while -- namely creating custom reports in SSMS. Creating SSMS custom reports isn't difficult, but like most technical work it's very detailed with a lot of little steps involved. So this post is a little longer than usual and includes a lot of...(read more)

    Read the article

  • find the all the stored procedures and jobs in sql server 2000

    - by kumar
    Hi, In SQL SERVER 2005 This query works fine : Select * from sys.procedures where object_definition(object_id) like '%J%' SELECT * FROM MSDB.DBO.SYSJOBS WHERE NAME LIKE '%J%' but in sql server 2000 it is not working. Here i need to find the all the stored procedures and jobs which matches my string ? how to find in sql server 2000 ? regards, kumar

    Read the article

  • Microsoft Tech-Ed North America 2010 - SQL Server Upgrade, 2000 - 2005 - 2008: Notes and Best Practi

    - by ssqa.net
    It is just a week to go for Tech-Ed North America 2010 in New Orleans, this time also I'm speaking at this conference on the subject - SQL Server Upgrade, 2000 - 2005 - 2008: Notes and Best Practices from the Field... more from here .. It is a coincedence that this is the 2nd time the same talk has been selected in Tech-Ed North America for the topic I have presented in SQLBits before....(read more)

    Read the article

  • SQL Server 2000 intermittent connection exceptions on production server - specific environment probl

    - by StickyMcGinty
    We've been having intermittent problems causing users to be forcibly logged out of out application. Our set-up is ASP.Net/C# web application on Windows Server 2003 Standard Edition with SQL Server 2000 on the back end. We've recently performed a major product upgrade on our client's VMWare server (we have a guest instance dedicated to us) and whereas we had none of these issues with the previous release the added complexity that the new upgrade brings to the product has caused a lot of issues. We are also running SQL Server 2000 (build 8.00.2039, or SP4) and the IIS/ASP.NET (.Net v2.0.50727) application on the same box and connecting to each other via a TCP/IP connection. Primarily, the exceptions being thrown are: System.IndexOutOfRangeException: Cannot find table 0. System.ArgumentException: Column 'password' does not belong to table Table. [This exception occurs in the log in script, even though there is clearly a password column available] System.InvalidOperationException: There is already an open DataReader associated with this Command which must be closed first. [This one is occurring very regularly] System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable. System.ApplicationException: ExecuteReader requires an open and available Connection. The connection's current state is connecting. System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. And just today, for the first time: System.Web.UI.ViewStateException: Invalid viewstate. We have load tested the app using the same number of concurrent users as the production server and cannot reproduce these errors. They are very intermittent and occur even when there are only 8/9/10 user connections. My gut is telling me its ASP.NET - SQL Server 2000 connection issues.. We've pretty much ruled out code-level Data Access Layer errors at this stage (we've a development team of 15 experienced developers working on this) so we think its a specific production server environment issue.

    Read the article

  • Event on SQL Server 2008 Disk IO and the new Complex Event Processing (StreamInsight) feature in R2

    - by tonyrogerson
    Allan Mitchell and myself are doing a double act, Allan is becoming one of the leading guys in the UK on StreamInsight and will give an introduction to this new exciting technology; on top of that I'll being talking about SQL Server Disk IO - well, "Disk" might not be relevant anymore because I'll be talking about SSD and IOFusion - basically I'll be talking about the underpinnings - making sure you understand and get it right, how to monitor etc... If you've any specific problems or questions just ping me an email [email protected]. To register for the event see: http://sqlserverfaq.com/events/217/SQL-Server-and-Disk-IO-File-GroupsFiles-SSDs-FusionIO-InRAM-DBs-Fragmentation-Tony-Rogerson-Complex-Event-Processing-Allan-Mitchell.aspx 18:15 SQL Server and Disk IOTony Rogerson, SQL Server MVPTony's Blog; Tony on TwitterIn this session Tony will talk about RAID levels, how SQL server writes to and reads from disk, the effect SSD has and will talk about other options for throughput enhancement like Fusion IO. He will look at the effect fragmentation has and how to minimise the impact, he will look at the File structure of a database and talk about what benefits multiple files and file groups bring. We will also touch on Database Mirroring and the effect that has on throughput, how to get a feeling for the throughput you should expect.19:15 Break19:45 Complex Event Processing (CEP)Allan Mitchell, SQL Server MVPhttp://sqlis.com/sqlisStreamInsight is Microsoft’s first foray into the world of Complex Event Processing (CEP) and Event Stream Processing (ESP).  In this session I want to show an introduction to this technology.  I will show how and why it is useful.  I will get us used to some new terminology but best of all I will show just how easy it is to start building your first CEP/ESP application.

    Read the article

  • SQL Server v.Next (Denali) : Deriving sets using SEQUENCE

    - by AaronBertrand
    One complaint about SEQUENCE is that there is no simple construct such as NEXT (@n) VALUES FOR so that you could get a range of SEQUENCE values as a set. In a previous post about SEQUENCE , I mentioned that to get a range of rows from a sequence, you should use the system stored procedure sys.sp_sequence_get_range . There are some issues with this stored procedure: the parameter names are not easy to memorize; it requires multiple conversions to and from SQL_VARIANT; and, producing a set from the...(read more)

    Read the article

  • Update SQL Server 2000 to SQL Server 2008: Benefits please?

    - by Ciaran Archer
    Hi there I'm looking for the benefits of upgrading from SQL Server 2000 to 2008. I was wondering: What database features can we leverage with 2008 that we can't now? What new TSQL features can we look forward to using? What performance benefits can we expect to see? What else will make management go for it? And the converse: What problems can we expect to encounter? What other problems have people found when migrating? Why fix something that isn't (technically) broken? We work in a Java shop, so any .NET / CLR stuff won't rock our world. We also use Eclipse as our main development so any integration with Visual Studio won't be a plus. We do use SQL Server Management Studio however. Some background: Our main database machine is a 32bit Dell Intel Xeon MP CPU 2.0GHz, 40MB of RAM with Physical Address Extension running Windows Server 2003 Enterprise Edition. We will not be changing our hardware. Our databases in total are under a TB with some having more than 200 tables. But they are busy and during busy times we see 60-80% CPU utilisation. Apart form the fact that SQL Server 2000 is coming close to end of life, why should we upgrade? Any and all contributions are appreciated!

    Read the article

  • VS 2010 and Entity Framework: accessing SQL Server 2000 databases

    - by pcampbell
    Consider a Visual Studio 2010 project whose requirement is to model the data using Entity Framework. The datasource is a SQL Server 2000 database. The first step is creating a new ADO.NET Entity Data Model item. The Entity Data Model Wizard prompts for a Data Connection. When creating a new Connection, you will need to use a provider other than SqlClient. Usually it's SQLOLEDB. The list of data providers only has SqlClient or ".NET Framework Data Provider for SQL Server". Is there a work-around for Visual Studio 2010 to create or use data connections to SQL Server 2000 using the Entity Framework?

    Read the article

  • Mysterious constraints problem with SQL Server 2000

    - by Ramon
    Hi all I'm getting the following error from a VB NET web application written in VS 2003, on framework 1.1. The web app is running on Windows Server 2000, IIS 5, and is reading from a SQL server 2000 database running on the same machine. System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. at System.Data.DataSet.FailedEnableConstraints() at System.Data.DataSet.EnableConstraints() at System.Data.DataSet.set_EnforceConstraints(Boolean value) at System.Data.DataTable.EndLoadData() at System.Data.Common.DbDataAdapter.FillFromReader(Object data, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) The problem appears when the web app is under a high load. The system runs fine when volume is low, but when the number of requests becomes high, the system starts rejecting incoming requests with the above exception message. Once the problem appears, very few requests actually make it through and get processed normally, about 2 in every 30. The vast majority of requests fail, until a SQL Server restart or IIS reset is performed. The system then start processing requests normally, and after some time it starts throwing the same error. The error occurs when a data adapter runs the Fill() method against a SELECT statement, to populate a strongly-typed dataset. It appears that the dataset does not like the data it is given and throws this exception. This error occurs on various SELECT statements, acting on different tables. I have regenerated the dataset and checked the relevant constraints, as well as the table from which the data is read. Both the dataset definition and the data in the table are fine. Admittedly, the hardware running both the web app and SQL Server 2000 is seriously outdated, considering the numbers of incoming requests it currently receives. The amount of RAM consumed by SQL Server is dynamically allocated, and at peak times SQL Server can consume up to 2.8 GB out of a total of 3.5 GB on the server. At first I suspected some sort of index or database corruption, but after running DBCC CHECKDB, no errors were found in the database. So now I'm wondering whether this error is a result of the hardware limitations of the system. Is it possible for SQL Server to somehow mess up the data it's supposed to pass to the dataset, resulting in constraint violation due to, say, data type/length mismatch? I tried accessing the RowError messages of the data rows in the retrieved dataset tables but I kept getting empty strings. I know that HasErrors = true for the datatables in question. I have not set the EnableConstraints = false, and I don't want to do that. Thanks in advance. Ray

    Read the article

  • Error with SQL Server Setup 2012 on Windows 2012

    - by Jeff
    I am trying to install SQL Server on Windows 2012. I was able to finally get the wizard up and running after making some changes on the server, but now it fails no matter what I do with the following error: TITLE: SQL Server Setup failure. SQL Server Setup has encountered the following error: There is an error in XML document (108, 148).. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0x066FCAFD%25400x5539C151 LinkID: 20476 Product Name: Microsoft SQL Server Message Source setup.rll Message ID: 50000 EvtType: 0x066FCAFD%400x5539C151 What I've tried: Installing from commandline with /q Result from CL installation: Error result: -2147467259 Result facility code: 0 Result error code: 16389 Please review the summary.txt log for further details The Verbose CL installation reveals: Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1033: NotInstalled Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1036: NotInstalled Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1040: NotInstalled Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1041: NotInstalled Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1042: NotInstalled Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1046: NotInstalled Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1049: NotInstalled Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_2052: NotInstalled Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_3082: NotInstalled Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_bids_loc.msi' does not exist Package ID sql_bids_loc_Cpu64_1053: NotInstalled Sco: File 'C:\SQL Install\x64\setup\x64\sql_ssms.msi' does not exist Sco: File 'C:\SQL Install\x64\setup\x64\sql_ssms.msi' does not exist Package ID sql_ssms_Cpu64: NotInstalled Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1028: NotInstalled Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1031: NotInstalled Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1033: NotInstalled Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1036: NotInstalled Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1040: NotInstalled Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1041: NotInstalled Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1042: NotInstalled Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1046: NotInstalled Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1049: NotInstalled Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_2052: NotInstalled Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_3082: NotInstalled Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\x64\sql_ssms_loc.msi' does not exist Package ID sql_ssms_loc_Cpu64_1053: NotInstalled Sco: File 'C:\SQL Install\x64\setup\sql_common_core_msi\x64\sql_common_core.msi' does not e Sco: File 'C:\SQL Install\x64\setup\sql_common_core_msi\x64\sql_common_core.msi' does not e Package ID sql_common_core_Cpu64: NotInstalled Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1028_CHT_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1028: NotInstalled Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1031_DEU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1031: NotInstalled Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1033: NotInstalled Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1036_FRA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1036: NotInstalled Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1040_ITA_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1040: NotInstalled Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1041_JPN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1041: NotInstalled Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1042_KOR_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1042: NotInstalled Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1046_PTB_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1046: NotInstalled Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1049_RUS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1049: NotInstalled Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\2052_CHS_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_2052: NotInstalled Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\3082_ESN_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_3082: NotInstalled Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Sco: File 'C:\SQL Install\1053_SVE_LP\x64\setup\sql_common_core_loc_msi\x64\sql_common_core Package ID sql_common_core_loc_Cpu64_1053: NotInstalled Sco: File 'C:\Users\Administrator\AppData\Local\Temp\2\SQL Server 2012\Setup\1033_ENU_LP\x6 lSupport.msi' does not exist Sco: File 'C:\Users\Administrator\AppData\Local\Temp\2\SQL Server 2012\Setup\1033_ENU_LP\x6 lSupport.msi' does not exist Package ID SqlSupport_Cpu64: NotInstalled Sco: File 'C:\SQL Install\redist\watson\x86\dw20shared.msi' does not exist Sco: File 'C:\SQL Install\redist\watson\x86\dw20shared.msi' does not exist Package ID WatsonX86_Cpu32: NotInstalled Package ID sqlncli_Cpu64: NotInstalled Package ID SqlLocalDB_Cpu64: NotInstalled Package ID SqlLocalDB_CTP3_Cpu64: NotInstalled Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTStub.msi' does not exist Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTStub.msi' does not exist Package ID SSDTStub_Cpu32: NotInstalled Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTDBSvcExternals.msi' does not exist Sco: File 'C:\SQL Install\1033_ENU_LP\x64\setup\x86\SSDTDBSvcExternals.msi' does not exist What does this mean?

    Read the article

  • SQL Server 2005 Table Alter History

    - by Kayes
    Hi. Does SQL Server maintains any history to track table alterations like column add, delete, rename, type/ length change etc? I found many suggest to use stored procedures to do this manually. But I'm curious if SQL Server keeps such history in any system tables? Thanks.

    Read the article

  • Which Edition of SQL Server 2008 R2 should you use?

    - by BuckWoody
    SQL Server 2008 R2 has just released to manufacturing (RTM’d) as I write this. With each new release, we make changes to the “Editions” we offer. A SQL Server “version” deals with the major changes in the product – and “edition” is a set of features and capabilities within that version (you’re welcome). So… definitely run over to http://msdn.microsoft.com/en-us/library/cc645993(v=SQL.105).aspx and check out the changes. For instance, did you know that SQL Server Express now supports 10GB databases? Well, then get over there and read what each edition does. Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

    Read the article

  • Using SQL Developer to Debug your Anonymous PL/SQL Blocks

    - by JeffS
    Everyone knows that SQL Developer has a PL/SQL debugger – check! Everyone also knows that it’s only setup for debugging standalone PL/SQL objects like Functions, Procedures, and Packages, right? – NO! SQL Developer can also debug your Stored Java Procedures AND it can debug your standalone PLSQL blocks. These bits of PLSQL which do not live in the database are also known as ‘Anonymous Blocks.’ Anonymous PL/SQL blocks can be submitted to interactive tools such as SQL*Plus and Enterprise Manager, or embedded in an Oracle Precompiler or OCI program. At run time, the program sends these blocks to the Oracle database, where they are compiled and executed. Here’s an example of something you might want help debugging: Declare x number := 0; Begin Dbms_Output.Put(Sysdate || ' ' || Systimestamp); For Stuff In 1..100 Loop Dbms_Output.Put_Line('Stuff is equal to ' || Stuff || '.'); x := Stuff; End Loop; End; / With the power of remote debugging and unshared worksheets, we are going to be able to debug this ANON block! The trick – we need to create a dummy stored procedure and call it in our ANON block. Then we’re going to create an unshared worksheet and execute the script from there while the SQL Developer session is listening for remote debug connections. We step through the dummy procedure, and this takes OUT to our calling ANON block. Then we can use watches, breakpoints, and all that fancy debugger stuff! First things first, create this dummy procedure - create or replace procedure do_nothing is begin null; end; Then mouse-right-click on your Connection and select ‘Remote Debug.’ For an in-depth post on how to use the remote debugger, check out Barry’s excellent post on the subject. Open an unshared worksheet using Ctrl+Shift+N. This gives us a dedicated connection for our worksheet and any scripts or commands executed in it. Paste in your ANON block you want to debug. Add in a call to the dummy procedure above to the first line of your BEGIN block like so Begin do_nothing(); ... Then we need to setup the machine for remote debug for the session we have listening – basically we connect to SQL Developer. You can do that via a Environment Variable, or you can just add this line to your script - CALL DBMS_DEBUG_JDWP.CONNECT_TCP( 'localhost', '4000' ); Where ‘localhost’ is the machine where SQL Developer is running and ’4000′ is the port you started the debug listener on. Ok, with that all set, now just RUN the script. Once the PL/SQL call is made, the debugger will be invoked. You’ll end up in the DO_NOTHING() object. Debugging an ANON block from SQL Developer is possible! If you step out to the ANON block, we’ll end up in the script that’s used to call the procedure – which is the script you want to debug. The Anonymous Block is opened in a new SQL Dev page You can now step through the block, using watches and breakpoints as expected. I’m guessing your scripts are going to be a bit more complicated than mine, but this serves as a decent example to get you started. Here’s a screenshot of a watch and breakpoint defined in the anon block being debugged: Breakpoints, watches, and callstacks - oh my! For giggles, I created a breakpoint with a passcount of 90 for the FOR LOOP to see if it works. And of course it does You Might Also EnjoyUsing Pass Counts to Turbo Charge Your PL/SQL BreakpointsSQL Developer Tip: Viewing REFCURSOR OutputThe PL/SQL Debugger Strikes Back: Episode VDebugging PL/SQL with SQL Developer: Episode IVHow to find dependent objects in your PL/SQL Programs using SQL Developer

    Read the article

  • Problem with MSDE 2000 5 minute keepalive over ISDN

    - by mcrick
    We have a SQL Server transactionally pushing replicate data to an MSDE 2000 SP3a subscriber over ISDN. Prior to a recent upgrade to bring us to the MSDE 2000 level we pushed to MSDE 1. We are finding that there is now a 5 minute keepalive being instigated from MSDE 2000 which we cannot account for. Further, we can find no way to either disable it or lengthen the keepalive interval. Not surprisingly, we are finding a marked increase in ISDN line costs due to these previously non-existent keepalive packets! Please note that we are assuming that it is an MSDE 2000 server issue, but it could equally be some behaviour related to the way that replication is operating on MSDE 2000. Unfortunately, as yet, we have not identified a replication configuration parameter that affects the keepalive in any way. Can anyone advise how we might indentify a root cause for this problem (and ideally a fix)?

    Read the article

  • Problem with MSDE 2000 5 minute keepalive over ISDN

    - by mcrick
    We have a SQL Server transactionally pushing replicate data to an MSDE 2000 SP3a subscriber over ISDN. Prior to a recent upgrade to bring us to the MSDE 2000 level we pushed to MSDE 1. We are finding that there is now a 5 minute keepalive being instigated from MSDE 2000 which we cannot account for. Further, we can find no way to either disable it or lengthen the keepalive interval. Not surprisingly, we are finding a marked increase in ISDN line costs due to these previously non-existent keepalive packets! Please note that we are assuming that it is an MSDE 2000 server issue, but it could equally be some behaviour related to the way that replication is operating on MSDE 2000. Unfortunately, as yet, we have not identified a replication configuration parameter that affects the keepalive in any way. Can anyone advise how we might indentify a root cause for this problem (and ideally a fix)?

    Read the article

  • SQL server timeout 2000 from C# .NET

    - by Johnny Egeland
    I have run into a strange problem using SQL Server 2000 and two linked server. For two years now our solution has run without a hitch, but suddenly yesterday a query synchronizing data from one of the databases to the other started timing out. I connect to a server in the production network, which is linked to a server containing orders I need data from. The query contains a few joins, but basically this summarizes what is done: INSERT INTO ProductionDataCache (column1, column2, ...) SELECT tab1.column1, tab1.column2, tab2.column1, tab3.column1 ... FROM linkedserver.database.dbo.Table1 AS tab1 JOIN linkedserver.database.dbo.Table2 AS tab2 ON (...) JOIN linkedserver.database.dbo.Tabl32 AS tab3 ON (...) ... WHERE tab1.productionOrderId = @id ORDER BY ... Obviously my first attempt to fix the problem was to increase the timeout limit from the original 5 minutes. But when I arrived at 30 minutes and still got a timeout, I started to suspect something else was going on. A query just does not go from executing in less than 5 minutes to over 30 minutes over night. I outputted the SQL query (which was originally in the C# code) to my logs, and decided to execute the query in the Query Analyzer directly on the database server. To my big surprise, the query executed correctly in less than 10 seconds. So I isolated the SQL execution in a simple test program, and observed the same query time out both on the server originally running this solution AND when running it locally on the database server. Also I have tried to create a Stored Procedure and execute this from the program, but this also times out. Running it in Query Analyzer works fine in less than a few seconds. It seems that the problem only occurs when I execute this query from the C# program. Has anyone seen such behavior before, and found a solution for it? UPDATE: I have now used SQL Profiler on the server. The obvious difference is that when executing the query from the .NET program, it shows up in the log as "exec sp_executesql N'INSERT INTO ...'", but when executing from Query Analyzer it occurs as a normal query in the log. Further I tried to connect the SQL Query Analyzer using the same SQL user as the program, and this triggered the problem in Query Analyzer as well. So it seems the problem only occurs when connecting via TCP/IP using a sql user.

    Read the article

< Previous Page | 32 33 34 35 36 37 38 39 40 41 42 43  | Next Page >