OMNI GROUPJoin Bytes!T-SQL/ CONTRACT TO PERM/ ATLANTAI'm looking for 1-2 TSQL developers for a 4 month contract to hirerole in Atlanta, GA. Ideally the candidate would be local or regional and aUS Citizen with 2-4 years of Microsoft TSQL development experience.Salary in the $55,000--$60,000 or so. annual range. Contract rate would beApproximately $36 hr W2 or 39hr 1099. One is responsible for their ownexpenses.Once perm, the company offers full benefits.If interested and qualified, answer the six questions below. EmailanswersWITH a resume to: Join Bytes!1. TSQL experience-------------------yrs2. MS SQL experience---------------yrs3. OO Languages----------------------4. Citizenship Status------------------5. Availability--------------------------6. Contract Rate ---------------pr hr..
I need to update a column(X) in database A.tableA with a column(Y) from database B.tableB where the value in another column(Z) in A.tableA = the value in a column(W) in B.tableB
Per my client, when it creates the qualifier for 'HCPS-DEN"' it needs to create the qualifier as 'AD' not 'HC'. Currently, with the present update script its inserting 'HC' on all. I need it to say when the 'HCPS-DEN' is used, insert the 'AD' not 'HC'. Everything else should be the HC.
I tried using a CASE statement: CASE WHEN Description = 'HCPC - DEN' THEN 'AD' ELSE 'HC' END
however I get this back:
Msg 207, Level 16, State 1, Line 10 Invalid column name 'Description'.
I was trying to plug this part in where HC is being entered. I think its missing an obvious Join or maybe there is a better way to write this. Any help is greatly appreciated!!
declare @qualid int if 1=1 BEGIN if not exists (select * from medlists where tablename='ProcedureCodeQualifier' and Description = 'HCPC - DEN') begin declare @listorder int select @listorder=max(listorder)+1 from medlists where tablename='ProcedureCodeQualifier'
insert into medlists select 'ProcedureCodeQualifier',NULL,'HC','HCPC - DEN',@listorder,NULL,NULL,NULL,NULL,NULL,NULL,NULL,@listorder,getdate(),'CYSScript',getdate(),dbo.GetLogonId()
update medlists set dotid=medlistsid where medlistsid=scope_identity() end
select @qualid=medlistsid from medlists where tablename='ProcedureCodeQualifier' and Description = 'HCPC - DEN'
update procedures set CPTProcedureCodeQualifierMId=@qualid where proceduresid in (8634) END ELSE BEGIN select @qualid =(select top 1 medlistsid from medlists where tablename='ProcedureCodeQualifier' and Description like 'Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes%') update procedures set CPTProcedureCodeQualifierMId=@qualid where proceduresid in (8634) END
Per my client, when it creates the qualifier for 'HCPS-DEN"' it needs to create the qualifier as 'AD' not 'HC'. Currently, with the present update script its inserting 'HC' on all. I need it to say when the 'HCPS-DEN' is used, insert the 'AD' not 'HC'. Everything else should be the HC.
I tried using a CASE statement: CASE WHEN Description = 'HCPC - DEN' THEN 'AD' ELSE 'HC' END
however I get this back:
Msg 207, Level 16, State 1, Line 10 Invalid column name 'Description'.
I was trying to plug this part in where HC is being entered. I think its missing an obvious Join or maybe there is a better way to write this. Description is being used after the first BEGIN. I know it needs to also go into my insert somehow, but I'm not sure how or if there is an easier way to do this. Any help is greatly appreciated!!
declare @qualid int if 1=1 BEGIN if not exists (select * from medlists where tablename='ProcedureCodeQualifier' and Description = 'HCPC - DEN') begin declare @listorder int select @listorder=max(listorder)+1 from medlists where tablename='ProcedureCodeQualifier'
insert into medlists select 'ProcedureCodeQualifier',NULL,'HC','HCPC - DEN',@listorder,NULL,NULL,NULL,NULL,NULL,NULL,NULL,@listorder,getdate(),'CYSScript',getdate(),dbo.GetLogonId()
update medlists set dotid=medlistsid where medlistsid=scope_identity() end
select @qualid=medlistsid from medlists where tablename='ProcedureCodeQualifier' and Description = 'HCPC - DEN'
update procedures set CPTProcedureCodeQualifierMId=@qualid where proceduresid in (8634) END ELSE BEGIN select @qualid =(select top 1 medlistsid from medlists where tablename='ProcedureCodeQualifier' and Description like 'Health Care Financing Administration Common Procedural Coding System (HCPCS) Codes%') update procedures set CPTProcedureCodeQualifierMId=@qualid where proceduresid in (8634) END
I have a Product Table. And now I have to create its Stored Procedures. I am asking the best practice regarding the methods Insert And Update. There are two options. 1. Create separate 2 procedures like InsertProduct and UpdateProduct. 2. Create just 1 procedure like ModifyProduct. In which programmatically check that either the record is present or not. If present then update and if not then insert. Just like Imar has done in his article http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=419 Can any one explain the better one. Waiting for helpful replies. http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=419 a
using custom tasks. My properties got saved properly the first time the task is added to the workspace. After that, changing values in the CustomUI updates the properties, but the package shows, that It doesn't need to get saved. So my properties don't get changed in the package XML. Moving my custom task on the workspace after changing properties, let the package go into "save me" state and my propertiy values get saved to XML.
So now, Im searching for a method or property I have to call or set to show the package it needs to get saved after closing my CustomUI.
Any hint?
Thanks
PS: When I change the property value in the task properties grid (lower right). The package gets notified about the need to get saved.
I have a master securities table which has 7 fields. As a part of the daily process I am uploading flat files into database tables. The flat files contains the master(static) security data as well as the analytics(transaction) data. I need to
1) separate the master (static) data from the flat files,
2) check whether that data is present in the master table, if not then insert that data into the master table
3) If data present then move that existing record to an history table and then update the main master table.
All the 7 fields need to be checked to uniquely identify a single record in the master table.
How can this be done? Whether we can us a combination of data flow items or write a sql procedure to do all this.
Hello:I didn't find any documentation that notes save point names are casesensitive, but I guess they are...Stored Proc to reproduce:/* START CODE SNIPPET */If Exists (Select * From sysobjects Where Type = 'P' and Name ='TestSaveTran')Drop Procedure dbo.TestSaveTranGoCreate Procedure dbo.TestSaveTranAsBeginDeclare@tranCount int--Transaction HandlingSelect @tranCount = @@TRANCOUNTIf (@tranCount=0)Begin Tran localtranElseSave Tran localtranBegin Try--Simulate Error While ProcessingRAISERROR('Something bad happened', 16, 1)/*If this proc started transaction then commit it,otherwise return and let caller handle transaction*/IF (@tranCount=0)Commit Tran localtranEnd TryBegin Catch--Rollback to save pointRollback Tran LOCALTRAN --<< NOTE case change--Log Error--Reraise ErrorEnd CatchEndGo--Execute Stored ProcExec dbo.TestSaveTran/*Should receive the following message:Cannot roll back LOCALTRAN. No transaction or savepoint of that namewas found.*//* END CODE SNIPPET */What is really strange, if there is a transaction open, then no erroris thrown. So if you execute as so:/* START CODE SNIPPET */Begin Tran--Execute Stored ProcExec dbo.TestSaveTran/* END CODE SNIPPET */There is no "Cannot roll back LOCALTRAN...." message.Questions:1-)Can someone confirm save point names are case sensitve and this isnot happening because of a server setting?2-)Is this a logic error that I am not seeing in the example codeabove?We have changed our code to store the save point name in a variable,which will hopefully mitigate this "problem".Thx.
I am new to sql sever management studio express, but a long time query analyzer user. This is a very basic question.
I want to change the default directory in sql server management studio express so that when I go to save a query, it is already pointed to the correct one. Where do I change that?
This program gets the values of A and B passed in. They are for table columns DXID and CODE. The textbox GET1 is initialized to B when the page is loaded. When I type another value in GET1 and try to save it, the original initialized value gets saved and not the new value I just typed in. A literal value, like "222" saves but the new GET1.TEXT doesn't.
I'm really new to MSDE so I just want to know...Is SQL Server 2000 a prerequisite for MSDE particularly for developers? If yes, then is it(SQL Server 2000) a prerequisite for clients?
The thing is, I can't find a tool where I can create databases after installing MSDE...the only way I can think of is also installing SQL Server 2000 and create the database from there...
Hi, I've just released Nautilus v1.0.6. I would apreciatte your opinion and comments. With Nautilus you can: -search tables without tipying the exact name. -browse records, filter and locate records -"Pivot" records to see it's related records (folowing the Foreign keys). -Generate scripts: create table, insert into, delete, update. -Build dynamic diagrams.
Can anyone please give me the equivalent tsql for sql server 2000 for the following two queries which works fine in sql server 2005
1 -- Full Table Structure
select t.object_id, t.name as 'tablename', c.name as 'columnname', y.name as 'typename', case y.namewhen 'varchar' then convert(varchar, c.max_length)when 'decimal' then convert(varchar, c.precision) + ', ' + convert(varchar, c.scale)else ''end attrib,y.*from sys.tables t, sys.columns c, sys.types ywhere t.object_id = c.object_idand t.name not in ('sysdiagrams')and c.system_type_id = y.system_type_idand c.system_type_id = y.user_type_idorder by t.name, c.column_id
2 -- PK and Index select t.name as 'tablename', i.name as 'indexname', c.name as 'columnname' , i.is_unique, i.is_primary_key, ic.is_descending_keyfrom sys.indexes i, sys.tables t, sys.index_columns ic, sys.columns cwhere t.object_id = i.object_idand t.object_id = ic.object_idand t.object_id = c.object_idand i.index_id = ic.index_idand c.column_id = ic.column_idand t.name not in ('sysdiagrams')order by t.name, i.index_id, ic.index_column_id
This sql is extracting some sort of the information about the structure of the sql server database[2005] I need a sql whihc will return the same result for sql server 2000
New to SQL so please be patient. I'd like to give my developers "See All/Do Nothing" rights to my production server. I want them be able to see everyting that I do, as SA, but not be able to change anything. Is this possible?
I will have a group of developers creating objects in a database. Currently they all create them with the SA account. I would like to have them mapped to the dbo or some method that when they create objects all objects are dbo.object name and not h1fed99.object name. Is there a good methor or practice to handle this
I'm currently trying to obtain an aggregate function from a table to provide a cumulative monthly value. I would like to create a view to obtian this from the underlying table i.e month=1 ,month=1,2 , month=1,2,3 Etc.
Always looking for people who are strong with microsoft technology for new oppurtunities in the Seattle area. If you are good, we can help you find your ideal next position.
I am looking for mid to senior level SQL developers for some sweet companies here in Seattle. A chance to work in a dynamic envirnoment with bleeding edge Microsoft technologies. Are you good? then we can help.
I am looking for strong SQL developers and/or DBA's for some really sweet companies here in Seattle. Anyone interested that is good and wants to hear about new oppurtunities? I would love to help you out.
This may be an intuitively obvious question, and if so, I apologize.
Speaking in terms of best practices here, what is the preferred method for allowing developers to work with databases in SQL Server? If they use Management Studio, then they have access to tools for perhaps messing with other databases, etc. that they should not (assuming it is not correctly secured). Likewise with Enterprise Manager. I can see where they would use Query Analyzer, but these two are now combined in Management Studio.
I'm just inquiring into how other DBA's do this. I realize there are DBA's that are developers and vice-versa, but what if there is a clear line of distinction and you want to keep the tools used in these roles separate?
Hi,I have just started a business and I was wondering if I could get someadvice about product selection. I am currently buiding my websiteusing asp.net connecting to sql server database.My question: Am I only required to purchase a SQL Server DevelopersLicence? I won't be hosting the site so I think this is correct butthought I should check.Cheers,Jack
I just bought a copy of SQL Server 2000 (with service pack 3a) that Iintended to install and run on XP Pro. My concern is that the requirementslist on the box do not include XP or XP Pro. Will SQL Server 2000 developeredition run on XP Pro?
Were looking from some feedback, thoughts, comments, suggestions on a permissions issue in our SQL Server 2005 environment. We have a Development (stand-alone server) and Production (activepassive cluster). Both running SP2. We're looking for the best way to manage permissions for the developers without giving them dbo privileges.
As background information, here's a note / response from a developer outlining the permission they need.
-----------------------------------------
"Our team needs enough permissions on DB database to:
Create and modify DB object such as tables, stored procedures, keys, triggers, views, ...
Be able to execute stored procedures and other basic DB objects
One of the issue I had when working on DatabaseA which was never resolved was that I could create tables, but had no rights to modify them once created.
I could modify them via scripts, but not via graphical interface which is a pain.
I think we should have full permissions to dev DB other than to drop DB, and modify system DB settings.
So that we can work within the created DB shell completely."
-----------------------------------------
Previous to supporting the current SQL Server 2005 environment, the developersapp owners had db_owner for their databases. Definitely not a best practice as with 2005 db_owner is ablke to delete databases. Moving away from this, we thought we would scale them back and only grant them the following database roles:
db_datareader
db_datawriter
db_ddladmin
With these roles, they were able to create the tables, views, stored procedures, etc...... but problems arose when they tried to modify the objects they created as well as execute stored procedures. It's going to be a pain to grant permissions on each stored procedure. More of a mystery is allowing them to make design changes within Studio Manager. Given they can already do this using scripts but not the GUI.
So there is an issue with using GUI tools to design the tables.
Here's a thread we found that tries to explain the reason why they can't use the GUI to make design changes.
Even if you have CREATE TABLE permission, there are limitations to the modifications you can make. Remember, as you modify an existing table or design a new one, your work can induce attendant modifications in other tables. For example, if you change the data type of a foreign-key column, the corresponding column in the primary-key table will be automatically modified by the Visual Database Tools. If you do not own the primary-key table, and you are not logged in as the system administrator, database owner, or a user that is a member of the db_owner role, your modification will fail.
When we created the accounts, we assigned the default schema to be 'dbo'. This was thought to simplify administration of the objects. In SQL Server 2000, this was a best practice. Now, in SQL Server 2005, they changed everything with the user schema separation.
So we have a developer (devuser) - created with default schema (dbo). Any object that are being created are owned by dbo. (ie... dbo.table1, dbo.storedproc1, etc..) So dbo owns the objects, not the user.
Does anyone have any ideas? Do we create a new schema and assign permissions? Do we create a new fixed database role for the developers? I'm curious as to how others are assigning permissions to developers on development and production servers.
What is the best practice in managing an SSIS development with multiple developers.
For example, we have 2 guys that will be developing various SSIS packages for a common data warehouse. We are most likely going to divide up the unit of work by the tables that need to get loaded. So, one guy will develop packages to load tables 1 thru 5 and the other guy will develop packages to load tables 6 thru 10.
Should each person work within his own project? (Not sure what a difference between a solution and a project is, so I may be thinking of a solution.) If so, can multiple people open the same project? I don't think you can.
I'm very new to SSIS and this would be the first time I'm doing something like this. I haven't even deployed a package to the server yet so I'm not even sure what implications/consideration I have before I take on this development effort I'm about to.
Is it possible to use SQL express to create a web application that is developed by more than one user? It seems to be registered on the <machinename>/SQLEXPRESS but the ASP.NET tool in visual studio seems to always want to create a sql express version in its app_data folder.
How can i set up a database such that 2 or more people can use that for developing the application. No doubt that SQL express with be suitable eventually, but initially we need to access the same database for development, but be on multiple machines. Can this be done, if so how?
I have problems with the concept of user-defined messages. I'm migrating from sybase ase to sql2005 and found out that there is only one global pool of messages. Do you give every project on this server a dedicated range of error-numbers?
Another problem: only the sysadmin oder serveradmin can call sp_addmessage. In my environment the developers own their databases and used to be able to create their own messages.
Now I try to let the developers call sp_addmessage by calling a "wrapper-procedure" which gets the needed rights.
create procedure sp__addmessage(@msgnum int, @severity smallint, @msgtext nvarchar(510), @lang sysname )WITH execute as OWNERASselect 'I am ' + suser_name(), user_name()exec sp_addmessage @msgnum, @severity, @msgtext, @lang gogrant execute sp__admessage to testusergo
When executing it as normal user (without sysadmin/serveradmin-roles) the output is: I am sa dboMsg 15247, Level 16, State 1, Procedure sp_addmessage, Line 18User does not have permission to perform this action.
Isn't it strange? Do you have a different idea how users/developers can create messages?
I like to get a feedback from other DBA's out there, I have a user with a consultant that need's Enterprise Manager installed on the user's desktop in order for them to develop code for the user.
Is the above a good reason to give out to the user the Enterprise Manager tools?
Please give me what is acceptable tools for the user/consultan.
since Sqlserver 7.0 looked so easy to our developers, they would like to perform development and administator tasks. Our environment will begin with 3 development groups, each with about 1-4 developers per group. We're might reach about 10-15 dbs with in a year. Most of the databases will be under 1 Gig(may be under 500 MB) and may be couple 2 Gig Dbs. We're not sure how many more databases we'll have.