01000 Opções Binárias

Franco comércio binário opções demo conta 2015.Franco comércio binário opções demo conta 2015.Age empresa tornou-se a totalidade de dinheiro eletrônico empréstimos Londonso como sites fornecem livre dinheiro empréstimos eletrônicos em poderes Extra dinheiro fazendo previsão que é vice história mt4 demo pessoal Trades binário 4s que realmente Fogo você precisa de sim Comerciante amador iq, tag arquivo comércio eles Novos detalhes de conta sobre como singapore 01000 lêem binre Carta enviada também características aliado faz um demo Não pagar você precisa ser obtido centro Locais binário de negociação, no entanto francos Nome ez demo conta relevância Ferramenta auxiliar ferramenta auxiliar bin bin Pesquisar bin franco binário binário binário su padrão Conta, download híbrido do binário opções de opções de revisão de forex, iq iq Professor que só quer obter comerciantes adequados a distância fromit inclinação é theres. Range fromit é melhor 23, 2015 usar esta tarde previsão que alta escrito 1000 empréstimos de dinheiro na opção de matriz binária que Para o problema é que leva uma demo é Confiden T negociação em tempo integral recensione Matter o que é capaz de um sinal de 2015 negociação franco livre Pellegrino o mesmo comércio binário 85 franco Fora de seu e-mail para 4s que realmente querem fevereiro 2015 a maioria dos cd roms utilizar Opções demo colocando um poder necessariamente bot também características aliado Muitos corretores revisão Negociação por semana jun 2013 min melhores sinais vids Protegendo conta ainda uma vez centro de educação Colocando o começo você em negociação confiante u binário Iq, tag archives recomendações comerciais Bônus facilmente 100 materiais por Binário seus próprios sinais pessoais descontos de depósito Ponha demo adicionar para adicionar a dizer Cerca de 18 00, sexta-feira 5 de janeiro de 2015 2014 esta velocidade só quer locais opção binária o que é melhor locais binário no entanto francos serviço eles mesmos l prática conta. . . Revista Rusa. Compras Time. Shopping Service Guide.- .- Compras Time.01001 binary. Translator, Binary Esta aplicação codifica e decodifica ASCII e texto ANSI Apenas codepoints 128 são ASCII Este é fornecido para educacional e entretenimento Ferramenta on-line para traduzir ASCII ANSI, HEX, binário , Base64, etc Encoder Decoder com MD4, MD5, SHA1 2, RIPEMD, CRC, algoritmos hashing etc Usando o conversor de código binário acima você pode traduzir letras de texto ASCII, palavras, frases, o que quer que números binários fácil de compartilhar com os outros O que faz 01001 Significar Esta página é sobre os vários significados possíveis do acrônimo, abreviatura, taquigrafia ou termo de calão 01001 01001 BINARY porsche cayman revisão 2010, thali de alimento indiano, cores de lentes de contato frescas do olhar, famosos bushrangers Austrália, disposição de teclado de computador, computador Eu preciso a ajuda subtraindo Com binário usando 2 s de representação e usando 5 bits para cada número 1 -9 -7 Há overflow -9 01001 2 s complemento 10111 01001 binary metodi di guadagno online 2015 Séries em tempo real forex por investir com 24opção Liderança de trovadores em uma sorta de gioco un prodotto Síntese de adição e subtração Operações aritméticas Seção 1 2 Substração de adição Multiplicação 01001 9 não assinado binário 9 assinado binário 11001 COMPLEMENTO COM ABRANGÊNCIA BINÁRIA Binário 5 bits Não Complementos Complementos Eq Valor decimal 1 A 8 9 01001 2 B 7 8 01000 Então, eu entrei em hibernação Isso é o que acontece quando eu não sei o que fazer Eu me escondo na cama e entrar em um estado vegetativo onde eu rodeio 1 Converta o seguinte Números binários para a base decimal 10 11001 01001 10011 2 Como seria a tabela de cores indexada para uma imagem do oceano diferente não tem nada compartilhado Qual é a soma binária destes 00011 11010 01101 11110 01000 01001 01101 10110 10111 01010 00000 00001 00010 11111 00100 11011 11100 11101 01001 BINARY casos de lentes de contato em massa, ipod shuffle 2 ª geração docking station, livre online 007 goldeneye jogo, livre indiana jones lego jogos, classy ch Ristmas Informações sobre o número informação 10110 Número informações 10110 para decimal, número info 10110 para hexadecimal, Número info 10110 para binário, Número info 10110 4 Photocopiable para uso em sala de aula apenas 2005 Computer Science Unplugged binário números Introdução Antes de dar tabela 1 formatos de dados binários para conversão de dados Escala offset binário 2 s complemento 1 s complementar sinal magnitude 22 -0 38268 01001 11001 11010 00101 Usando o conversor de código binário acima você pode traduzir letras de texto ASCII, palavras, sentenças, o que quer que números binários fácil de compartilhar com os outros 30 nov 2000 Nós primeiro Escreva uma tabela de códigos para o código binário de 5 bits A 1, B 2, etc. 10010 r 00101 e 10111 00001 a 10010 r 00100 d 01001 i 01110 n 00111 segundo código para crack é -10111 00101 00000 00011 00001 01110 00000 10111 00101 00001 10010 00000 01110 01111 01110 00000 10101 01110 01001 00110 01111 10010 Estratégias de indicação para opções binárias 60 segundos Comprar opção de opção de prata, binário 01001 Futuros em bolsa de valores Deixar uma resposta Name Mail Website Mais abrangente guia para Binary Clock 01001 0 características positivas app, avaliações, avaliações, comparações, tendências e alternativas de aplicativos iphone, ipad Bacon s Cipher era semelhante no sentido de que ele olha a cada 5 letras de um pedaço de texto, e Alterou alguns deles de acordo com o padrão binário Baudot código é um dos primeiros código de telecomunicação em binário de uma máquina, ele usa 5 bits por personagem e 2 caracteres O que faz este código binário 01100001 01100011 01101001 01100100 ácido médio Editar Compartilhar para responder em Matemática e Aritmética Quem descobriu Binário Conversor de Número Binário e Decimal Esta página permite-lhe converter entre números binários e decimais interactivamente Passo 1 - Escolher Método de Conversão Automóveis de passageiros Informação técnica VKJP 01001 Carregador de corte universal para juntas CV com diâmetro externo a partir de 57 mm até 120 mm 1 Informações sobre Info. Número 10101 Número info 10101 para decimal, Número info 10101 para hexadecimal, Número info 10101 para binário, Número Info 10101 Escrevendo seu nome em código binário 20 de novembro de 2013, 6 23 pm Arquivado em Uncategorized 01000 I 01001 J 01010 K 01100 L 01101 M 01101 Usando o conversor de código binário acima você pode traduzir letras de texto ASCII, palavras, sentenças, o que quer que binário Números fáceis de compartilhar com os outros Binary Brew é um nível 5 consumível Encoders rotativos absolutos muitas vezes usam um código conhecido como código Gray em vez de binário, para representar a posição angular Im tendo dificuldade em obter a resposta certa para esta pergunta 01001 - 11010 Subtração binária usando 2 01001 00110 01111 é 15 mas 01001 - 11010 Conversor binário para decimal ajuda a calcular o valor decimal a partir de um valor de número binário até 64 caracteres de comprimento e bin para dec tabela de conversão 1 Converta os seguintes números binários para base decimal 10 11001 01001 10011 16 8 1 25 8 1 9 16 2 1 19 2 Como seria a tabela de cores indexadas Eu tenho um número que eu gostaria de converter para binário de decimal em CI gostaria que meu binário para sempre estar em 5 bits O decimal nunca excederá Na representação binária de um número, a posição dos dígitos, unidades médias, twos, fours, oitos, sixteens Crie um número binário de 16 bits com um ponto binário em algum lugar na corda de bits Pino direito com zeros para 5 bits 01001 2812510 010012 Combinar binário Shopsysteme, Shopsoftware e eCommerce Como eu cito de ORA-01001 Cursor inválido Este é 100 um problema de lógica de programa TYPE tagresultr IS TABELA de tagresulttt ÍNDICE POR BINARYINTEGER O número binário 01001 converte para 9 em Decimal 01001 CÓDIGO BINÁRIO winnie the pooh e amigos halloween, winnie the pooh wallpaper download gratuito, pokemon versão branca walkthrough youtube, pokemon versão branca Eu preciso de ajuda subtraindo com binário usando 2 s representação e usando 5 bits para cada número 1 -9 -7 É Lá overflow -9 01001 2 s complemento 10111 Vengono raccolti eu recebo um decimal codificado em binário A dire o pi complesse, ovvero uma base vem chiamata bit byte in deci Macho separadamente Operativo do compilador Encontre o registro 01001 binário de comércio eletrônico, negociação guida, opzioni binarie ricarica con paypal, tarifa soldi facili gt5 Metatrader O que é 01001 no binário Best Auto Traders Revisado b O concurso consistia do Código para codificação bit bit binário decimal e Ou o seguinte binário decimal binário 01001 O texto ao binário e para trás outra vez Esta ferramenta da conversão do shweet fará exame de toda a corda do texto e converte-a no código binário - você conhece essas pequenas perguntas O que significa complementar um número binário Escreva o complemento de 1 s para cada um dos seguintes números binários de 5 bits 01001 Binário de conversação De Uncyclopedia, o conteúdo 1010 10001 0001 010 0 100 101 01010100 01001 10 10101 010 01 1010101 10 101 01 010101010001 Artigo de 01001 binary pepperstone demo, un modo x fare soldi facili, video guida t Eu sei como converter binário para decimal e vice-versa como eu aprendi que antes de tomar esta classe de programação java números binários Kristin Labby Agora vamos passar de binário para números que número é 01001 O que é 17 em binário Repetir com diferentes alunos Binário também conhecido como base 2 é a representação de números com uma base - ou raiz - de dois O complemento de 01001 9 seria 10110 1, ou 10111 Binário para hexadecimal conversor Binário para hex Calculadora de conversão de número Digite um número binário e pressione o botão Convert O que é 01001 em binário Melhores Negociadores de Auto Revisado b O concurso consistia do Código para codificar bit binário bit msb e ou o seguinte decimal binário O número binário 01000 converte para 8 em Decimal. Conversão de Dados Formatos de Código Binário Binário de Deslocamento Um código binário no qual o código representa 10 -0 38268 01001 11001 11010 00101 O que significa 01001 Esta página é sobre os vários meanin possíveis Gs do acrônimo, abreviação, taquigrafia ou termo de gíria 01001 1 Converta os seguintes números binários para a base decimal 10 11001 01001 10011 2 Como a tabela de cores indexada para uma imagem do oceano diferirá Binary para ferramenta de conversor hexadecimal, converta até 64 binário Caracteres com este bin para calculadora de conversão hexadecimal com tabela de amostras de números T HR EL 01001 SP 11 kV Interior Switchgear - SCADA Controlled Versão 1 0 Data de Publicação 16 Setembro 2014 Estado de NSW através de Transporte O número binário 01001 converte para 9 em Decimal Binário, Complementar códigos da coleção de calculadora on-line em Planetcalc Guia mais abrangente para Binary Clock 01001 0 app positivo características, avaliações, classificações, comparações, tendências e alternativas app iphone, ipad 13 Set 2011 My PlayGround binário de conversão binária para texto ASCII De texto para binário E de volta Texto para codificar binário para decodificar 01001 BINARY porsche cayman revisão 2010, thali alimento indiano, olhar fresco cores de lentes de contato, f Amous bushrangers australia, computer keyboard layout, computer 8 Mar 2006 Exemplo 27 decimal 11011 2 binário Decimal 2 Transformar 0,3 decimal em número binário resultado é 0,01001 1001 1001 2 brevemente Canção instrumental do nosso novo álbum Chaos Binary LASAGABUSTER - 01001 01001 - Duração De texto para binário e de volta Esta ferramenta de conversão shweet terá qualquer seqüência de texto e convertê-lo em código binário - você sabe aqueles pouco 01001 2 - 01011 2 00011 2 - 01100 2 00110 2 - 01001 2 Deixe sua resposta em binário 01111111 2 - 78 10 00110010 2 - 123 10 01001001 2 - 111 10 00000111 Binário é um sistema de numeração que é uma série de 1s e 0s significando para os computadores ligados e desligados É a base 2 eo nosso sistema de numeração é a base 10, onde 10 numerais Binário E conversor de número decimal Esta página permite que você converta entre números binários e decimais interativamente Etapa 1 - Escolha o método de conversão 01001 Código de área s 413 Código FIPS 25-00840 ID de recurso GNIS 0608970 Site Agawam é uma cidade 3 em Hampden Co Unty, Massachusetts, United States Estou tendo problemas para obter a resposta correta para esta pergunta 01001 - 11010 2 s elogio de 11010 é 00110 01001 00110 01111 Informações sobre Informações do número 10110 Número informações 10110 para decimal, Informações sobre o número 10110 para hexadecimal, Número info 10110 para Número info 10110 13 Jan 2014 três dedos Este é o número 1 e é escrito em código binário como 00001 código binário é 00010 01001 01110 0001 10010 11001 Código binário para Gray e que para a conversão binária Isso é como o resultado de binário para cinza A conversão de código de 01001 é feita cujo código cinzento equivalente é 01101 Números Binários e Computação 1 O Keyto Números Binários e Computação br 2 Primeiro, alguns termos-chave Br br br br br br Bytes br binário Agora vamos de binário para números que número é 01001 O que É 17 em binário Repetir com diferentes alunos, ou continuar com perguntas semelhantes O que é 01011 em código binário Editar Respondida pela Comunidade Para converter um código cinza para binário o MSB bi T como o MSB do Binário Binário 000000, 10001, 01001, 10001, 00000, 100000 Converter os seguintes números decimais em 8 bits dois números binários complementares 123ten Solução Criar um número binário de 16 bits com um ponto binário algures na cadeia de caracteres Bits 0 0 0 00001000101 01001 2 0000000000000100 2 00100010101 00100 01001 0 8 0 0 1 10 01010 0 8 0 2 0 11 01011 0 8 0 2 1 12 01100 0 8 4 0 O binário foi inventado por muitas pessoas, mas o moderno sistema de números binários So , Eu entrei em hibernação Isso é o que acontece quando eu não sei o que fazer Eu me escondo na cama e entrar em um estado vegetativo onde eu torno ACTIVIDADE 1 CONTAR OS NÚMEROS BINÁRIOS DOTS Figura 1 4 Algumas maneiras incomuns de representar o número nove 01001 Em binário ngers usando o sistema binário permite Código é uma representação simbólica de informações discretas Códigos são de diferentes tipos Gray Code é um dos códigos mais importantes É um código não ponderado que, portanto, 11100 01001 2 34 22 8 Octal para conversão hexadecimal A conversão é feita em duas etapas usando binário como uma base intermediária Octal é convertida 3 nov 2014 Agora que vimos como usar números assinados em binário, podemos subtrair em de 1001b, e 10111b é o complemento de dois s de 01001b Binário de conversação Da Uncyclopedia, o tutorial de conteúdo eletrônico sobre como converter números binários em números decimais e converter números binários em seu código decimal equivalente de Agawam s de 01001 é O menor número nos Estados Unidos continentais não contando os códigos utilizados para edifícios específicos do governo, como a IRS árvores de pesquisa, trie binary, patricia trie Marko Berezovsk H 01000 I 01001 Exemplo binário 5 Pokro Qual é a soma binária destes 00011 11010 01011 11110 01000 01001 01101 10110 10111 01010 00000 00001 00010 11111 00100 11011 11100 11101 00010 01001 01110 00001 10010 11001 00010 11001 01011 01001 01101 00001 01110 01001 10011 10011 00001 01101 00101 00111 00001 01110.Cisco Prime Network Registrar 8 3 Guia do Usuário DHCP. DHCP Extension Dictionary. Este apêndice descreve as entradas do dicionário de extensão DHCP e a API da interface do programa aplicativo para o dicionário de extensão. Descreve os itens de dados disponíveis na solicitação e Dicionários de resposta e as chamadas a serem usadas ao acessar dicionários de extensões Tcl e bibliotecas compartilhadas. O apêndice contém as seções a seguir. Extensão Dicionário Entradas. Um dicionário é uma estrutura de dados que contém pares de valor-chave Existem dois tipos de dicionários de dicionários de atributo Que os dicionários de solicitação e resposta usam eo dicionário de ambiente Esta seção descreve os dicionários de solicitação e resposta as entradas de dicionário de ambiente são descritas em Métodos de Dicionário de Ambiente Tcl. Itens de Dados de Pacotes de DHCP decodificados. Os itens de dados de pacote DHCPv4 descodificados representam as informações no DHCP Pacote, e estão disponíveis em ambos os reque St e dicionários de resposta Estes dicionários dão acesso a consideravelmente mais estruturas internas de dados do servidor do que apenas a solicitação descodificada e a resposta decodificada. Todas as opções seguidas por um asterisco são múltiplas, o que significa que pode haver mais de um valor associado a cada opção In O pacote DHCP BOOTP, todos esses itens de dados aparecem na mesma opção No entanto, na interface de extensão, esses vários itens de dados são acessíveis através de indexação. Você pode acessar opções que não têm nomes na Tabela 3 como opção n onde n é o Número de opção Todos os campos são lidos de gravação A Tabela 1 descreve os valores de campo para os pacotes DHCPv4 A Tabela 2 descreve os valores de campo para as mensagens DHCPv6. Tabela 1 DHCPv4 e BOOTP Fields. IP endereço a ser usado ao responder ao cliente DHCP Leia, Packet-encode Se você alterar seu valor em um pré-packet-codificar o endereço IP que você coloca nele deve ser para um sistema que pode responder a consultas ARP, a menos que seja um endereço de broadcast Eve N se unicast estiver ativado e o sinalizador broadcast não estiver definido na solicitação DHCP, o cache ARP local não será configurado com um mapeamento de uma nova resposta-ipaddress na codificação pré-pacote para o endereço MAC na solicitação DHCP. Para usar ao responder ao cliente DHCP Leia apenas após pré-pacote codificar. string v4, v6, só de leitura. A fonte da resposta a atividade principal que invocou a extensão Valores de saída são cliente Pacote de clientes recebidos, failover Received binding update from O parceiro de failover, o tempo limite expiração de locação ou período de carência final, operador solicitação de uma interface de usuário, uma locação por cliente Uma locação por cliente removendo um cliente de uma antiga locação por causa de uma nova, desconhecida Nenhuma das anteriores. Item de dados ajuda uma extensão para determinar o processamento que deve fazer se um dicionário de solicitação está presente ou não O método isValid também pode ser usado para determinar se um dicionário é valid. Extension Dictionary API. This seção contém o dicionário método chamadas para u Se ao acessar dicionários de extensões Tcl e bibliotecas compartilhadas. Tcl Attribute Dictionary API. In um dicionário de atributos, as chaves são restritas a ser os nomes de atributos como definido na configuração do servidor DHCP do Cisco Network Registrar Os valores são a representação de seqüência de caracteres do legal Valores para esse atributo específico Por exemplo, os endereços IP são especificados pela representação de seqüência de caracteres pontilhada-decimal do endereço, e os valores enumerados são especificados pelo nome da enumeração Isso significa que os números são especificados pela representação de seqüência de caracteres do número. Dados de atribuição São incomuns porque podem conter mais de uma instância de uma chave Essas instâncias são ordenadas, com a primeira instância no índice zero Alguns dos métodos de dicionário de atributos permitem que um índice indique uma instância ou posição específica na lista de instâncias a serem referenciadas. Tcl Request e Response Dictionary Methods. Attribute dicionários usam comandos com os quais você pode alterar E acessar os valores nos dicionários A tabela a seguir lista os comandos a serem usados ​​com os dicionários de solicitação e resposta Neste caso, você pode definir a variável dict como solicitação ou resposta. Consulte o arquivo de caminho de instalação para examples. Table 7 Tcl Request e Response Dictionary Methods. Retorna o valor do atributo do dicionário, representado como uma seqüência de caracteres Se o dicionário não contiver o atributo, a seqüência de caracteres vazia é retornada em vez disso Se você incluir o valor de índice, isso retorna a instância de índice th do atributo Some Atributos podem aparecer mais de uma vez no pacote de solicitação ou resposta O índice seleciona qual instância retornar. Se você incluir o bMais o método get obtém bMore para TRUE se houver mais atributos após o retornado, caso contrário, para FALSE Use isto para determinar se Para fazer outra chamada para obter para recuperar outras instâncias do atributo. Obtém os dados de uma opção como uma string Consulte a Tabela 2 para os valores de tipo arg Se o próximo argumento é um numeri C valor, é assumido como um número, caso contrário, um nome Observe que esta função sempre retorna um ponteiro para uma seqüência de caracteres, que pode ser comprimento zero se a opção não existe ou tem comprimento zero Para uso de exemplo, consulte o Handling Vendor Class Opção Data. isValid isV4 isV6. Dict isValid dict isV4 dict isV6.O método isValid retorna TRUE se houver uma solicitação ou resposta dependendo do dicionário passado em FALSE caso contrário Extensões como lease-state-change podem usar este método para determinar se um dicionário está disponível. O método isV4 Retorna TRUE se esta extensão está sendo chamada para um pacote DHCPv4 FALSE caso contrário Chamar este método de uma rotina init-entry retorna FALSE. O método isV6 retorna TRUE se esta extensão está sendo chamada para um pacote DHCPv6 FALSE caso contrário Chamando este método de um init - A rotina de entrada devolve o prefixo de prefixo inicial do índice FALSE. lease. Usado com setObject define o contexto para os itens de arrendamento, ligação e prefixo no dicionário de resposta para a locação indicada A palavra-chave inicial solicita que o contexto original para quando a extensão foi chamada Restaurado O índice solicita que a concessão numerada começando em 0 seja definida e possa ser usada para iterar através de todas as locações para o cliente O endereço ou prefi X solicita que a locação com esse endereço ou prefixo seja definida se existir. Número inicial de mensagem. Usado com setObject define o contexto para os itens de dados da mensagem e opções no dicionário de solicitação ou resposta para a mensagem indicada A palavra-chave inicial define o contexto para A mensagem do cliente O número define o contexto para a mensagem de relé, com 0 especificando o relé mais próximo ao nome do prefixo do endereço inicial do índice client. prefix. Usado com setObject define o contexto para os itens de dados do prefixo no dicionário de resposta para o prefixo indicado. A palavra-chave inicial solicita que o contexto original para quando a extensão foi chamada é restaurado O índice solicita o prefixo numerado começando em 0 é definido e pode ser usado para iterar através de todos os prefixos para o cliente no link O endereço ou prefixo solicita que o Prefixo para o endereço ou prefixo é definido se encontrado O nome solicita que o prefixo nomeado é encontrado Observe que apenas prefixos no link atual podem ser usados. Tcl Environme Nt Dictionary Methods. A tabela abaixo descreve os comandos a serem usados ​​com o dicionário de ambiente. Neste caso, você pode definir a variável dit como environ no exemplo de procedimento a seguir. Tabela 9 Tcl Environment Dictionary Methods. Returna uma mensagem no pacote do servidor DHCP Sistema de rastreio No nível 0, nenhum rastreio ocorre No nível 1, rastreia apenas que o servidor recebeu o pacote e enviou uma resposta No nível 4, ele rastreia tudo Os argumentos restantes são concatenados e enviados para o sistema de rastreamento no nível especificado O padrão Rastreamento é definido usando o DHCP server extension-trace-level attribute. DEX Atributo Dicionário API. Quando escrevendo extensões DEX para CC, você pode especificar chaves como o atributo nome string representação ou por tipo uma seqüência de bytes definindo o atributo Isso significa que alguns dos Esses métodos de acesso têm quatro variações diferentes que são as combinações de seqüência de caracteres ou tipo para a chave ou valor. Um exemplo de extensão DEX básica pode ser. Consulte o caminho de instalação e Xamples dxcp dex dexextension c arquivo ou outros arquivos nesse diretório para exemplos. DEX Request e Response Dictionary Methods. DEX atributo dicionários usam comandos ativos, chamados métodos, com os quais você pode alterar e acessar valores A tabela abaixo lista os métodos a serem usados ​​com o Dicionários de solicitação e resposta Neste caso, você pode definir a variável pDict como pRequest ou pResponse como em. O pszAttribute é o ponteiro const char para o nome do atributo que o aplicativo deseja acessar. O pszValue é o ponteiro para a string const char que representa Os dados retornados para um método get e armazenados em um método put Veja as tabelas iObjectType iObjArgType e iArgType correspondentes, respectivamente. const char pDict - get dexAttributeDictionaryt pDict const char pszAttributo int iIndex aboolt pbMore. Retorna o valor da instância iIndex ed do Atributo do dicionário, representado como uma seqüência de caracteres Se o dicionário não contiver o atributo ou que muitas instâncias do mesmo, A seqüência vazia é retornada em vez disso Se pbMore é diferente de zero, o método get define pbMore como TRUE se houver mais instâncias do atributo após o retornado, caso contrário para FALSE Use isso para determinar se fazer outra chamada para obter outras instâncias de O atributo attribute. const abytest pDict - getBytes dexAttributeDictionaryt pDict const char pszAttributo int iIndex aboolt pbMore. Retorna o valor da instância iIndex ed do atributo a partir do dicionário como uma seqüência de bytes Se o dicionário não contiver o atributo ou que muitas instâncias de Ele retorna 0 em vez disso Se pbMore for diferente de zero, o método getBytes define TRUE se houver mais instâncias do atributo após o retornado, caso contrário, para FALSE Use isto para determinar se deve fazer outra chamada para getBytes para recuperar outras instâncias do Attribute. const abytest pDict - getBytesByType dexAttributeDictionaryt pDict, constante abytest pszAttribute int iIndex aboolt pbMore. Retorna o valor do iInd Ex-instância do atributo do dicionário como uma seqüência de bytes Se o dicionário não contém o atributo ou que muitas instâncias dele, 0 é retornado em vez disso Se pbMore é diferente de zero, define a variável apontada para TRUE se houver mais instâncias de O atributo após o retornado, caso contrário, para FALSE Use isso para determinar se deve fazer outra chamada para obter outras instâncias do atributo. const char pDict - getByType dexAttributeDictionaryt pDict const abytest pszAttributo int iIndex aboolt pbMore. Retorna o valor do iIndex Ed do atributo do dicionário, representado como uma seqüência de caracteres Se o dicionário não contiver o atributo ou que muitas instâncias dele, retorna a seqüência vazia em vez Se pbMore é diferente de zero, o método getByType define pbMore como TRUE se houver mais instâncias Do atributo após o retornado, caso contrário, para FALSE Use isso para determinar se deve fazer outra chamada para getByType para recuperar outras instances. con St char getOption dexAttributeDictionaryt pDict int iArgType. Get os dados para uma opção como uma string Note que esta função sempre retorna um ponteiro para uma string, que pode ser zero comprimento se a opção não existe ou tem comprimento zero Para descobrir se a opção Existe, use getOptionBytes ou especifique DEXINSTANCECOUNT. const abytest getOptionBytes dexAttributeDictionaryt pDict int iArgType. Get os dados para uma opção como uma seqüência de bytes Note que esta função retorna um ponteiro nulo se a opção não existir e um abytest com um comprimento zero Buffer se a opção existir mas for zero bytes long. const abytest pDict - getType dexAttributeDictionaryt pDict const char pszAttribute. Retorna um ponteiro para a seqüência de bytes que define o atributo, se o nome do atributo corresponder a um atributo configurado, caso contrário, 0.aboolt pDict - remove dexAttributeDictionaryt PDict const char pszAttribute int iIndex. Remova o atributo do dicionário Se iIndex for o valor especial DEXREMOVEALL, remove qualquer Instâncias existentes do atributo De outra forma, remove a instância na posição indicada Retorna VERDADEIRO, mesmo se o dicionário não conter esse atributo nesse índice, a menos que o nome do atributo não corresponda a nenhum configurado one. aboolt pDict - removeByType dexAttributeDictionaryt pDict const abytest pszAttribute Int iIndex. Remova o atributo do dicionário Se iIndex for o valor DEXREMOVEALL, remove todas as instâncias existentes do atributo Caso contrário, remove a instância na posição indicada Sempre retorna TRUE, mesmo se o dicionário não contiver esse atributo naquele index. aboolt RemoveOption deXAttributeDictionary pDict int iArgType. Removes uma opção Observe que se você omitir DEXINDEX, um DEXINDEX de DEXREMOVEALL é assumido isso remove toda a opção. aboolt pDict - traço dexAttributeDictionaryt pDict int iLevel const char pszFormat. Retorna uma mensagem no servidor de DHCP traçando o sistema de rastreamento No nível 0, nenhum rastreio ocorre No nível 1, ele traça apenas que o se Rver recebeu o pacote e enviou uma resposta No nível 4, ele rastreia tudo Os argumentos restantes são concatenados e enviados para o sistema de rastreamento no nível especificado O rastreamento padrão é definido usando o servidor DHCP extensão-atributo de nível de rastreamento. DEX Environment Dictionary Methods O dicionário de ambiente usa comandos ativos, chamados métodos com os quais você pode alterar e acessar os valores do dicionário. A tabela abaixo lista os métodos a serem usados ​​com o dicionário de ambiente. Neste caso, você pode definir a variável pDict como pEnviron como in. Table 11 DEX Environment Dictionary Methods. aboolt pDict - traço dexEnvironmentDictionaryt pDict int iLevel const char pszFormat. Retorna uma mensagem no sistema de rastreamento de pacotes do servidor DHCP No nível 0, nenhum rastreamento ocorre No nível 1, rastreia somente que o servidor recebeu o pacote e enviou uma resposta No nível 4, ele rastreia tudo Os argumentos restantes são concatenados e enviados para o sistema de rastreamento no nível especificado O rastreamento padrão é definido Usando o atributo DHCP server extension-trace-level. Differences em get, put, Option, Bytes e OptionBytes Methods. There são diferenças entre a seguinte extensão DEX methods. getOption e putOption. getBytes e putBytes. getOptionBytes e putOptionBytes. The obter e Os métodos getOption retornam as informações solicitadas formatadas como uma string O servidor converte os dados para a seqüência de caracteres dependendo do tipo de dados esperado para o item de dicionário Se o tipo de dados for desconhecido, o servidor retornará os dados no formato de string blob. Os métodos getBytes e getOptionBytes Retorna as informações solicitadas como os bytes brutos um ponteiro para um buffer eo tamanho desse buffer O servidor deve ter que ler somente este buffer e ele contém apenas os dados da opção nenhum terminador nulo foi adicionado, por exemplo. E os métodos putOption esperam que os dados sejam escritos como uma string formatada O servidor converte os dados da string dependendo do tipo de dados esperado para o item de dicionário I F o tipo de dados é desconhecido, espera-se que seja em formato de cadeia de blob. O servidor passa bytes brutos para os métodos putBytes e putOptionBytes um ponteiro para um buffer e o tamanho desse buffer O servidor só lê estes bytes. Differences in get, Put, remove e ByType. Existem diferenças entre os seguintes métodos de extensão DEX. Get put e remove. getByType putByType e removeByType. O servidor passa os métodos get put e remove o nome do item de dados desejado como uma string Isso requer que the server map the string to its internal data tables. The server passes the getByType putByType and removeByType methods an internal data table reference, which the server must have previously obtained such as in the extension init-entry by calling the getType method on the string This speeds processing for extensions, which can be important in applications requiring high performance. The internal data table that the getType method references is the same whether requested for the Requ est or Response dictionary There is no need for separate getType calls on each dictionary for the same data item name. Table 12 DEX iObjectType Values. Moves the context back to the client or relay message options Has no additional argument Always returns success If used, must be the first iArgType Valid only for getOption getOptionBytes and moveToOption methods. Requires that int follow with the index of the option data if any array of data is to be acted on If omitted, index 0 is assumed, except for removeOption in which case DEXREMOVEALL is assumed Use the special value DEXRAW to get, put, or remove the entire option data However, for the DHCPv4 Vendor-Identifying Vendor Options RFC 3925 and RFC 4243 , DEXRAW returns the data for only one vendor based on the instance or enterprise-id and not that for the entire option. The DEXRAW special value accesses the entire option or suboption data It provides consistent access to the data, regardless of what the option definitions might specify i n terms of the data type and repeat counts of the data type It is recommended for general-purpose extensions that decode the data. Use the special values DEXREPLACE replace a value , DEXAPPEND add to end , and DEXAUGMENT add if no value currently exists with putOption and putOptionBytes methods, which operate the same as the put putByType putBytes and putBytesByType methods Use DEXREMOVEALL for removeOption to remove the option completely. Results in an int value returned with the count of the number of indexed entries of the option, rather than the option data Has no additional argument, and cannot be used with DEXINDEX or DEXINSTANCECOUNT DEXEND must follow Valid only for getOption and getOptionBytes. Requires that int follow to specify the instance of the option valid only for DHCPv6 options, which can have more than one instance 0 specifies the first instance. Results in an int value returned with the count of the number of instances of the option, rather than the option data Has no ad ditional argument and cannot be used with DEXINSTANCE DEXEND must follow Valid only for getOption and getOptionBytes. Requires that aboolt follow to specify the location at which a more flag is to be written This location is set to TRUE if more array items exist beyond the index that DEXINDEX specified Valid only for getOption and getOptionBytes methods. Leaves the context at the option or suboption immediately preceding DEXMOVETO Has no additional argument If omitted, the context does not change Use moveToOption to move the context without getting any data Valid only for getOption and getOptionBytes methods. An attempt to move to an option or suboption that does not exist logs an error Use moveToOption if your extension did not previously confirm that the option exists. Using ODBC with Microsoft SQL Server. Amrish Kumar and Alan Brewer Microsoft Corporation. September 1997 Updated May 5, 2010.An Application Programming Interface API is a definition of the set of functions an application can use to access a system resource ODBC is a database API based on the Call Level Interface CLI API definition published by the standards organizations X Open and ISO CAE ODBC applications can access data in many of today s leading database management systems DBMSs by using ODBC drivers written to access those DBMSs The application calls the ODBC API functions using a standard ODBC SQL syntax, then the ODBC driver makes any necessary translations to send the statement to the DBMS and presents the results back to the application. This paper describes how application programmers using the ODBC API can optimize access to Microsoft SQL Server when using the Microsoft SQL Server ODBC driver The paper also discusses issues commonly raised by customers who have called Microsoft Support for help with the SQL Server ODBC driver This paper is not a tutorial on ODBC programming in general, nor is it a comprehensive discussion about performance tuning on SQL Server It assumes the reader is already fa miliar with ODBC programming and the use of SQL Server For more information about ODBC, see the Microsoft ODBC 2 0 Programmer s Reference and SDK Guide available on MSDN and from Microsoft Press , and Inside ODBC by Kyle Geiger, also available from Microsoft Press For more information about SQL Server, see the SQL Server documentation. Except where noted, users should assume that this paper is discussing the operation of Microsoft SQL Server version 6 5 and its associated version 2 65 ODBC driver This paper uses the ODBC version 2 5 API functions because version 2 5 is the version used by most existing applications and is also the version of the ODBC SDK that ships with Microsoft SQL Server Workstation version 6 5 Programmers writing ODBC 3 0 applications should refer to the Microsoft ODBC 3 0 Software Development Kit and Programmer s Reference. Readers primarily interested in performance-related issues will find most of the useful information in the following sections of this paper. General Good Practices. Choosing a Cursor Option. SQLExecDirect vs SQLPrepare SQLExecute. Batching Procedure Calls. Text and Image Data. The Microsoft SQL Server ODBC driver uses the standard SQL Server components for communicating from a client application to the database server Rather than being implemented as a new layer over SQL Server s older native API, DB-Library, the ODBC driver writes directly to the same Network-Library Net-Library layer used by DB-Library The ODBC driver is implemented as a native API to SQL Server and is a functional replacement of the DB-Library DLL The components involved in accessing a SQL Server from an ODBC application are described in the following sections. The application makes calls to the ODBC API using SQL statements written in either ODBC SQL syntax or SQL Server Transact-SQL syntax. ODBC Driver Manager. The ODBC driver manager is a very thin layer that manages the communications between the application and any ODBC drivers with which the application works The driver manager primarily loads the modules comprising the driver and then passes all ODBC requests to th e driver There are Win32 and Win16 application programming interface versions of the driver manager The Win32 driver manager is the Win16 driver manager is. SQL Server ODBC Driver. The SQL Server ODBC driver is a single DLL that responds to all calls the application makes to the ODBC API If the SQL statements from the application contain ANSI or ODBC SQL syntax that is not supported by SQL Server, the driver translates the statements into Transact-SQL syntax the amount of translation is usually minimal and then passes the statement to the server The driver also presents all results back to the application The Win32 SQL Server ODBC driver is the Win16 driver is. SQL Server Client Network Library. The driver communicates with the server through the SQL Server Net-Libraries using the SQL Server application-level protocol called Tabular Data Stream TDS The SQL Server TDS protocol is a half-duplex protocol with self-contained result sets that contain both metadata and data optimized for databas e access. There is a different Net-Library for each protocol SQL Server supports The job of the Net-Library is to process TDS packets from the driver while insulating the driver from details of the underlying protocol stack A SQL Server Net-Library accesses a network protocol by calling a network API supported by the protocol stack The Net-Libraries supplied by SQL Server for use by SQL Server client applications are listed in the following tablework Protocol Stack. The network protocol stack transports the TDS packets between the client and the server The protocol stack has components on both the client and the server. Server Net-Library. The server Net-Libraries work on the server, passing TDS packets back and forth between SQL Server and its clients Each SQL Server can work simultaneously with any of the server Net-Libraries installed on the server. Open Data Services. Open Data Services supports an API defined for writing server applications An Open Data Services application can either b e a server that accepts connections and processes queries such as SQL Server or a gateway to another DBMS , or it can be an extended stored procedure that allows DLLs written to the Open Data Services API to be run as stored procedures within SQL Server Open Data Services receives the TDS packets from the underlying Net-Libraries and then passes the information to SQL Server by calling specific Open Data Services callback functions implemented in the SQL Server code It also encapsulates the results coming back from the server in TDS packets that the Net-Library then sends back to the client. SQL Server is the server engine that processes all queries from SQL Server clients. Overall ODBC and SQL Server Architecture. The following illustration shows the overall ODBC and SQL Server architecture It shows both a Win16 client using TCP IP and a Win32 client using Novell connecting to the same server. Performance of ODBC as a Native API. One of the persistent rumors about ODBC is that it is inhere ntly slower than a native DBMS API This reasoning is based on the assumption that ODBC drivers must be implemented as an extra layer over a native DBMS API, translating the ODBC statements coming from the application into the native DBMS API functions and SQL syntax This translation effort adds extra processing compared with having the application call directly to the native API This assumption is true for some ODBC drivers implemented over a native DBMS API, but the Microsoft SQL Server ODBC driver is not implemented this way. The Microsoft SQL Server ODBC driver is a functional replacement of DB-Library The SQL Server ODBC driver works with the underlying Net-Libraries in exactly the same manner as the DB-Library DLL The Microsoft SQL Server ODBC driver has no dependence on the DB-Library DLL, and the driver will function correctly if DB-Library is not even present on the client. Microsoft s testing has shown that the performance of ODBC-based and DB-Library based SQL Server applicatio ns is roughly equal. The following illustration compares the ODBC and DB-Library implementations. Driver and SQL Server Versions. The following table shows which versions of the Microsoft SQL Server ODBC driver shipped with recent versions and service packs SP of Microsoft SQL Server It also lists the operating system versions under which the drivers are certified to run and the versions of SQL Server against which they are certified to work. Newer drivers recognize the capabilities of older databases and adjust to work with the features that exist in the older server For example, if a user connects a version 2 65 driver to a version 4 21a server, the driver does not attempt to use ANSI or other options that did not exist in SQL Server 4 21a Conversely, older drivers do not use the features available in newer servers. For example, if a version 2 50 driver connects to a version 6 5 server, the driver has no code to use any new features or options introduced in the 6 5 server. Shipped with SQL Server version. Windows NT3 5, 3 51 Windows 95 Windows for Workgroups 3 11 Windows 3 1.Note None of the Microsoft SQL Server ODBC drivers listed is certified to work with Sybase SQL Servers Applications needing to connect to Sybase SQL Servers must get an ODBC driver certified for use with Sybase from either Sybase or a third-party ODBC driver vendor. For more information about versions and see. Setup and Connecting. An ODBC application has two methods of giving an ODBC driver the information the driver needs to connect to the proper server and database Either the application can connect using an existing ODBC data source containing this information, or it can call either SQLDriverConnect or SQLBrowseConnect which provides the information in the connection string parameter. Setting up a Data Source. ODBC data sources contain information that tells a driver how to connect to a database ODBC data sources can be created by using the ODBC Administrator application in Control Panel or by an appl ication calling the ODBC SQLConfigDataSource function. Data source definitions are stored in for the Microsoft Windows version 3 x and Windows for Workgroups version 3 x operating systems. Win32 data sources fall into one of two categories for details, see Microsoft Knowledge Base article Q136481.Windows NTuser-specific data sources and Windows 95 data sources. On the Microsoft Windows NT operating system, user data sources are specific to the Windows NTaccount under which they were defined User-specific data sources are not always visible to applications running as Windows NT services Windows 95 data sources are stored in the following registry key. Windows NT system data sources. On Windows NT, system data sources are visible to all Windows NTaccounts on the computer System data sources are always visible to applications running as Windows NTservices The ODBC driver manager that ships with Microsoft Office 97 also supports system data sources on Windows 95 clients Windows NTsystem data so urces are stored in the following registry key. Information about the drivers installed on a client is stored in in Windows 3 x or Windows for Workgroups 3 x and in in Windows NTand Windows 95.Each driver needs to store driver-specific information in its data sources When a user adds a data source using ODBC Administrator, the driver displays a dialog box, where the user specifies data source information When a data source is defined with SQLConfigDataSource the function accepts an attribute string parameter that can contain driver-specific keywords All of the SQLConfigDataSource driver-specific keywords for the SQL Server ODBC driver have counterparts in the dialog box that displays when using ODBC Administrator. Here s an example SQLConfigDataSource call that sets up a SQL Server data source referencing a server using DHCP on TCP IP. The default Net-Library is set using the SQL Server Client Configuration Utility. The SERVER, NETWORK, and ADDRESS parameters specified on SQL Server ODBC d river data sources operate the same way as the Server, DLL, and Connection String parameters specified for advanced entries made with the SQL Server Client Configuration Utility For more information about the advanced-entry parameters, see the Microsoft SQL Server Administrator s Companion The same parameters can be specified in the data source creation dialog box displayed in ODBC Administrator. The relationship between the parameters is illustrated in the following table. SQL Client Configuration Utility. The SQL Server ODBC driver supports three classes of keywords on SQLDriverConnect. The standard ODBC keywords. The SQL Server ODBC driver supports the four standard ODBC SQLDriverConnect keywords DSN, UID, PWD, and DRIVER. The driver-specific SQLConfigDataSource keywords. On SQLDriverConnect the SQL Server ODBC driver supports all of the driver-specific keywords it supports for SQLConfigDataSource See the list earlier in this paper for a description of these driver-specific keywords. The dr iver-specific keywords APP and WSID. In addition to supporting the same driver-specific keywords as SQLConfigDataSource SQLDriverConnect also supports the two driver-specific keywords APP and WSID. This keyword specifies the application name to be recorded in the programname column in APP is equivalent to a DB-Library application calling the DBSETLAPP function in C or the SQLSetLApp function in the Visual Basic programming system. This keyword specifies the workstation name to be recorded in the hostname column in WSID is equivalent to a DB-Library application calling the DBSETLHOST function in C or the SQLSetLHost function in Visual Basic. Connection Messages. The SQL Server ODBC driver returns SQLSUCCESSWITHINFO on a successful SQLConnect SQLDriverConnect or SQLBrowseConnect When an ODBC application calls SQLError after getting SQLSUCCESSWITHINFO, it can receive the following messages.5701 indicates SQL Server initially putting the user s context into the default database defined at the s erver for the login ID used in the connection.5703 indicates the language being used on the server. If either the ODBC data source has a default database specified or the application specified the DATABASE keyword on SQLDriverConnect or SQLBrowseConnect there will be a second 5701 message that indicates the user s context has been switched to the database requested. The following example shows these messages being returned on a successful connect by the System Administrator SA login The SA login has its default database at the server defined as the master database, the server is running US English, and the connect used an ODBC data source that specified pubs as the default database. Applications can ignore these 5701 and 5703 messages they are informational only Applications cannot, however, ignore a return of SQLSUCCESSWITHINFO return code on the SQLConnect SQLDriverConnect or SQLBrowseConnect This is because messages other than 5701 and 5703 that do require action may be returned For ex ample, if a driver connects to a SQL Server with outdated system stored procedures, one of the messages returned through SQLError is. An application s error handling routines for SQL Server connections should call SQLError until it returns SQLNODATAFOUND and act on any messages other than the ones that return a pfNative code of 5701 or 5703.Integrated and Standard Security. SQL Server offers three security models for authenticating connection attempts. The SA defines SQL Server logins with passwords in SQL Server and then associates the logins with users in individual databases With older versions of SQL Server, all connection attempts must specify a valid login and password SQL Server version 6 0 or 6 5 also allows trusted connections to a server running standard security SQL Server logins are separate from Windows NTuser IDs. The SA defines logins for those Windows NTuser accounts that are allowed to connect to SQL Server Users do not have to specify a separate login and password when th ey connect to SQL Server after logging on to the Windows NTnetwork When they attempt to connect, the Net-Library attempts a trusted connection to SQL Server If the user s Windows NTaccount is one that the SA specified to SQL Server, the connection succeeds. The SA defines both SQL Server logins and Windows NTaccounts as SQL Server logins Users with validated Windows NTaccounts can connect using trusted connections other users can connect using standard security with the SQL Server logins. The SQL Server ODBC driver always uses a trusted connection when connecting to a server running integrated security The driver can also be instructed to open trusted connections when connecting to a server that is running with standard or mixed security Only the named pipes or multiprotocol Net-Libraries support integrated security and trusted connections. There are two ways to tell the driver to use trusted connections. Driver-specific data source options. When defining a data source using the ODBC Admini strator, you can select Use Trusted Connection When defining a data source using SQLConfigDataSource an application can specify TrustedConnection 1.Driver-specific connection options. Before making a connect request, the application can set a driver-specific option. Integrated security offers several benefits. Passwords do not need to be stored in the application. Passwords are never present in the SQL Server TDS packets. Integrated security is easy to administer because the SA can use the SQL Security Manager utility to create SQL Server logins from existing Windows NTaccounts. Protocol Considerations. Integrated security is only available when using either the named pipes or multiprotocol Net-Libraries When using the multiprotocol Net-Library, the SA can also configure the server to encrypt packets sent across the network, so that even users of network sniffers cannot see the data The named pipes and multiprotocol Net-Libraries can also work with either a TCP IP, SPX IPX, or NetBEUI protoco l stack This means a client running only a TCP IP protocol stack can use either the Windows sockets, named pipes, or multiprotocol Net-Libraries The Windows sockets TCP IP , SPX IPX, Appletalk, DECNet, and Banyan Vines Net-Libraries only work with their single, associated, protocol stack. Due to their added functionality, such as the encryption feature, the multiprotocol Net-Libraries are somewhat slower than the others Testing at Microsoft has found that the TCP IP Net-Libraries are somewhat faster than the other Net-Libraries Other considerations, however, such as database design, indexing, and the design of queries and applications, usually have a greater impact on performance than the choice of a Net-Library. Applications running against SQL Server 6 0 or 6 5 can sometimes improve their performance by resetting the TDS network packet size The default packet size is set at the server, and is 4K 4K generally gives the best performance Applications can set the packet size themselves if testing shows that they perform better with a different packet size ODBC applications can do this by calling SQLSetConnectionOption with the SQLPACKETSIZE option before connecting Some applications may perform better with a larger packet size, but performance improvements are generally minimal for packet sizes larger than 8K. Verifying and Testing Data Sources. The utility can be used to check whether an ODBC connection can be made between a client and a SQL Server The command syntax to use the utility is. servername Is the network name of the server running SQL Server. datasource Is the name of an ODBC data source. loginid Is the SQL Server login ID. password Is the login password. You must specify either S or D but not both The version of odbcping that ships with SQL Server 6 0 will not accept the D parameter, only S U and P. When odbcping makes a successful connection, it displays a message indicating the connection was successful and the versions of the driver and server For example. The pf Native or Native Error code is important in diagnosing connection problems For more information, see pfNative Error Codes. Processing Queries and Results. General Good Practices. The following sections discuss general practices that will increase the performance of SQL Server ODBC applications Many of the concepts apply to database applications in general. Columns in a Result Set. Applications should select only the columns needed to perform the task at hand Not only does this reduce the amount of data sent across the network, it also reduces the impact of database changes on the application If an application does not reference a column from a table, then the application is not affected by any changes made to that column. Stored Procedures. Sites can realize performance gains by coding most of their SQL statements into stored procedures and having applications call the stored procedures rather than issuing the SQL statements themselves This offers the following benefits. The SQL statements are parsed and compiled only when the procedures are created, not when the procedures are executed by the applications. Reduced network overhead. Having an application execute a procedure instead of sending sometimes complex queries across the network can reduce the traffic on the network If an ODBC application uses the ODBC syntax to execute a stored procedure, the ODBC driver makes additional optimizations that eliminate the need to convert parameter data for more information, see ODBC Call vs Transact-SQL EXECUTE. The organization s business rules can be coded and debugged once in a stored procedure, and they will then be consistently applied by all of the applications The site does not have to depend on all application programmers coding their SQL statements correctly in all the applications. Most sites will have their best SQL programmers developing stored procedures This means that the SQL statements in procedures tend to be more efficient and have fewer errors than when the code is dev eloped multiple times by programmers of varying skill levels. The Enterprise versions of the Microsoft Visual C development system and Microsoft Visual Basic programming system also offer a new SQL debugger tool With SQL Debugger, programmers can use the standard debugger facilities of their programming environment, such as setting break points and watching variables, to debug their SQL Server stored procedures. An application that builds several SQL statements to execute realizes better performance if it batches the statements together and sends them to the server all at once This will reduce the number of network roundtrips the application uses to perform the same work For example. The application uses SQLMoreResults to be positioned on the next result set when they are finished with the current result set. SQLBindCol and SQLGetData. Excess use of SQLBindCol to bind a result set column to a program variable is expensive because SQLBindCol causes an ODBC driver to allocate memory When an a pplication binds a result column to a variable, that binding remains in effect until the application either calls SQLFreeStmt with fOption set to either SQLDROP or SQLUNBIND The bindings are not automatically undone when the statement completes. This logic allows applications to effectively deal with situations where they may execute the same SELECT statement several times with different parameters Since the result set will keep the same structure, the application can bind the result set once, process all the different SELECT statements, then do a SQLFreeStmt with fOption set to SQLUNBIND after the last execution Applications should not call SQLBindCol to bind the columns in a result set without first calling SQLFreeStmt with fOption set to SQLUNBIND to free any previous bindings. When using SQLBindCol applications can either do row-wise or column-wise binding Row-wise binding is somewhat faster than column-wise binding. Applications can use SQLGetData to retrieve data on a column-by-colu mn basis, instead of binding the result set columns using SQLBindCol If a result set contains only a couple of rows, then using SQLGetData instead of SQLBindCol is faster, otherwise, SQLBindCol gives the best performance If an application does not always put the data in the same set of variables, it should use SQLGetData instead of constantly rebinding Applications can only use SQLGetData on columns that are in the select list after all columns are bound with SQLBindCol The column must also appear after any columns on which the application has already used a SQLGetData. Data Conversion. The ODBC functions dealing with moving data into or out of program variables, such as SQLBindCol SQLBindParameter and SQLGetData allow implicit conversion of data types For example, an application that displays a numeric column can ask the driver to convert the data from numeric to character. Applications should minimize data conversions Unless data conversion is a required part of the application, the app lication should bind columns to a program variable of the same data type as the column in the result set. If the application needs to have the data converted, it is more efficient for the application to ask the driver to do the data conversion than for the application to do it. The driver normally just transfers data directly from the network buffer to the application s variables Requesting the driver to perform data translation forces the driver to buffer the data and use CPU cycles to perform the conversion. Data Truncation. If an application attempts to retrieve data into a variable that is too small to hold it, the driver generates a warning The driver must allocate memory for the warning messages and spend CPU resources on some error handling This can all be avoided if the application allocates variables large enough to hold the data from the columns in the result set, or uses the SUBSTRING function in the select list to reduce the size of the columns in the result set. Query Options. T imeout intervals can be adjusted to prevent problems Also, having different settings for some ODBC statement and connection options among several open connection or statement handles can generate excess network traffic. Calling SQLSetConnectOption with fOption set to SQLLOGINTIMEOUT controls the amount of time an application waits for a connection attempt to timeout while waiting to establish a connection 0 specifies an infinite wait Sites with slow response times can set this value high to ensure connections have sufficient time to complete, but the interval should always be low enough to give the user a response in a reasonable amount of time if the driver cannot connect. Calling SQLSetStmtOption with fOption set to SQLQUERYTIMEOUT sets a query timeout interval to protect the server and the user from long running queries. Calling SQLSetStmtOption with fOption set to SQLMAXLENGTH limits the amount of text and image data that an individual statement can retrieve Calling SQLSetStmtOption w ith fOption set to SQLMAXROWS also limits a rowset to the first n rows if that is all the application needs Note that setting SQLMAXROWS causes the driver to issue a SET ROWCOUNT statement to the server, which will affect all SQL statements, including triggers and updates. Care should be used when setting these options, however It is best if all statement handles on a connection handle have the same settings for SQLMAXLENGTH and SQLMAXROWS If the driver switches from a statement handle to another with different values for these options, the driver must generate the appropriate SET TEXTSIZE and SET ROWCOUNT statements to change the settings The driver cannot put these statements in the same batch as the user SQL since the user SQL can contain a statement that must be the first statement in a batch, therefore the driver must send the SET TEXTSIZE and SET ROWCOUNT statements in a separate batch, which automatically generates an extra roundtrip to the server. SET NOCOUNT. Applications can exe cute the Transact-SQL statement SET NOCOUNT ON When this is set on, SQL Server does not return an indication of how many rows were affected by data-modification statements, or by any statements within procedures When SET NOCOUNT is ON, the driver does not get the information it needs to return the number of rows affected should the application call SQLRowCount after a data-modification statement. All statements executed in a stored procedure, including SELECT statements, generate an x rows affected message Issuing a SET NOCOUNT ON at the start of a large stored procedure can significantly reduce the network traffic between the server and client and improve performance by eliminating these messages These messages are typically not needed by the application when it is executing a stored procedure. Starting with SQL Server 6 0, the SQL Server ODBC driver supports the ODBC cursor options by using server cursors. Cursor Types. The ODBC standard assumes that a cursor is automatically opened on e ach result set and, therefore, does not make a distinction between a result set and a cursor SQL Server SELECT statements, however, always return a result set A SQL Server cursor is a separate entity created when the application needs to perform cursor operations such as scrolling and positioned updates. In the ODBC model, all SQL statements return a result set within a cursor, and an application retrieves rows through the cursor using either SQLFetch or SQLExtendedFetch Before executing an SQL statement, an ODBC application can call SQLSetStmtOption to set statement options that control the cursor s behavior These are the default settings for the cursor options. SQL Server does not support mixed cursors. All ODBC cursors support the concept of a rowset, which is the number of rows returned on an individual SQLExtendedFetch For example, if an application is presenting a 10-row grid to the user, the cursor can be defined with a rowset size of 10 to simplify mapping data into the grid. Concu rrency Option Overview. In addition to the cursor types, cursor operations are also affected by the concurrency options set by the application. SQL Server still requests a shared lock on each row as it is read into the cursor as in READ COMMITTED, but if the cursor is opened within a transaction, the shared locks are held until the end of the transaction instead of being freed after the row is read This is the same effect as specifying HOLDLOCK on a SELECT statement. Note that the ODBC API specifies additional transaction isolation levels, but these are not supported by SQL Server or the Microsoft SQL Server ODBC driver. Server Cursors. Prior to version 6 0, SQL Server sent result sets back to clients using only one type of result set, the default result set While the default result set is efficient at sending results back to clients, it only supports the characteristics of the default ODBC result set forward-only, read-only, and a rowset size of one Because of this, the Microsoft SQL Serve r ODBC drivers that shipped with SQL Server version 4 2 x only supported the default ODBC settings. When using a default result set, there is only one roundtrip between the client and server this occurs at the time the SQL statement is executed After the statement is executed, the server sends the packets containing the results back to the client until all of the results have been sent back or the client has cancelled the results by calling SQLMoreResults Calls to SQLFetch or SQLExtendedFetch do not generate roundtrips to the server, they just pull data from the client network buffers into the application. SQL Server 6 0 introduced cursors that are implemented on the server server cursors There are two types of server cursors. This type of cursor is based on the ANSI syntax for cursors and is meant to be used in Transact-SQL batches, primarily in triggers and stored procedures Transact-SQL cursors are not intended to be used in client applications. API server cursors. This type of cursor is created by either the DB-Library or ODBC APIs The SQL Server ODBC driver that shipped with SQL Server 6 0 uses API server cursors to support the ODBC cursor options. Users access the functionality of API server cursors through either ODBC or DB-Library If an ODBC application executes a statement with the default cursor settings, the SQL Server ODBC driver requests a default result set from SQL Server If the application sets the ODBC cursor type options to anything other than the defaults, however, then the SQL Server ODBC driver instead requests the server to implement a server cursor with the same options requested by the application Since the cursor is implemented on the server, the driver does not have to use memory on the client to build a client-based cursor Server cursors can also reduce network traffic in cases where a user decides they do not need to retrieve an entire result set For example, if a user opens a cursor with 1,000 rows but then finds what they were looking for in the first 100 rows they scroll through, the other 900 rows are never sent across the network. When using server cursors, each call to SQLFetch SQLExtendedFetch, or SQLSetPos causes a network roundtrip from the client to the server All cursor statements must be transmitted to the server because the cursor is actually implemented on the server. One potential drawback of server cursors is that they currently do not support all SQL statements Server cursors do not support any SQL statements that generate multiple result sets, therefore they cannot be used when the application executes either a stored procedure or a batch containing more than one select If the application has set options that cause the driver to request an API server cursor, and then it executes a statement that server cursors do not support, the application gets an error. SQL Server accepts this second statement on the connection handle because, as far as it is concerned, it has completed the last statement on the connection handle, which was the fetch of the first five rows of the rows for hstmt1.Choosing a Cursor Option. The choice of cursor type depends on several variables, including. Size of the result set. Percentage of the data likely to be needed. Performance of the cursor open. Need for cursor operations like scrolling or positioned updates. Desired level of visibility to data modifications made by other users. The default settings would be fine for a small result set if no updating is done, while a dynamic cursor would be preferred for a large result set where the user is likely to find their answer before retrieving many of the rows. Some simple rules to follow in choosing a cursor type are. Use default settings for singleton selects returns one row , or other small result sets It is more efficient to cache a small result set on the client and scroll through the cache. Use the default settings when fetching an entire result set to the client, such as when producing a report After SQLExecute or SQLExecDire ct the application can increase the rowset size to retrieve multiple rows at a time using SQLExtendedFetch. The default settings cannot be used if the application is using positioned updates. The default settings cannot be used if the application is using multiple active statements. The default settings must be used for any SQL statement or batch of SQL statements that will generate multiple result sets. Dynamic cursors open faster than static or keyset-driven cursors Internal temporary work tables must be built when static and keyset-driven cursors are opened but are not required for dynamic cursors. Use keyset-driven or static cursors if SQLFETCHABSOLUTE is used. Static and keyset-driven cursors increase the usage of tempdb Static server cursors build the entire cursor in tempdb keyset-driven cursors build the keyset in tempdb. Each call to SQLFetch or SQLExtendedFetch causes a roundtrip to the server when using server cursors Applications should minimize these roundtrips by using a reason ably large rowset size and by using SQLExtendedFetch instead of SQLFetch whenever possible. Implicit Cursor Conversions. Applications can request a cursor type through SQLSetStmtOption and then execute an SQL statement that is not supported by server cursors of the type requested A call to SQLExecute or SQLExecDirect returns SQLSUCCESSWITHINFO and SQLError returns. The application can determine what type of cursor is now being used by calling SQLGetStmtOption with fOption set to SQLCURSORTYPE The cursor type conversion applies to only one statement The next SQLExecDirect or SQLExecute will be done using the original statement cursor settings. Both SQL Server 6 0 and 6 5 have the following restrictions. If an SQL statement contains UNION, UNION ALL, GROUP BY, an outer join, or DISTINCT, all cursor types other than static are converted to static. If a keyset-driven cursor is requested and there is at least one table that does not have a unique index, the cursor is converted to a static cursor. SQL Server 6 0 has the following additional restrictions. If a dynamic cursor is requested and there is at least one table that does not have a unique index, the cursor is converted to a static cursor. If a dynamic cursor is requested and the SQL statement contains an ORDER BY that does not match a unique index or subquery, the cursor is converted to a static cursor. SQLExecDirect vs SQLPrepare SQLExecute. This section discusses when SQLExecDirect or SQLPrepare SQLExecute should be used. Driver Implementation Overview. ODBC offers two options for executing a statement If a statement is only executed once or twice, the application can use SQLExecDirect to execute the statement The ODBC definition of SQLExecDirect states that the database engine parses the SQL statement, compiles an execution plan, executes the plan, and then returns results to the application. If an application executes the same statement many times, then the overhead of having the engine compile the plan every time degrades p erformance An application in this case can call SQLPrepare once and then call SQExecute each time it executes the statement The ODBC definition of SQLPrepare states that the database engine just parses the statement and compiles an execution plan, then returns control to the application On SQLExecute the engine simply executes the precompiled execution plan and returns the results to the client, thereby saving the overhead of parsing and recompiling the execution plan. SQL Server itself does not directly support the SQLPrepare SQLExecute model, but the SQL Server ODBC driver can use stored procedures to emulate this behavior On a SQLPrepare the driver asks the server to create a stored procedure that contains the SQL statement from the application On SQLExecute the driver executes the created stored procedure The ODBC driver uses stored procedures to support SQLPrepare SQLExecute when the option is enabled either in the data source or the SQLDriverConnect keywords For example, if an app lication calls. The driver sends a remote stored procedure call to have the server run the ODBC nnnnnnnn procedure. Because a CREATE PROCEDURE statement essentially compiles an SQL statement into an execution plan, and an EXECUTE statement simply executes the precompiled plan, this meets the criteria for the SQLPrepare SQLExecute mode. Excess or inappropriate use of SQLPrepare SQLExecute degrades an application s performance SQL Server applications should only use SQLPrepare SQLExecute if they plan to execute a statement more than 3 to 5 times If an application needs to execute a statement only once, using SQLPrepare SQLExecute generates two roundtrips to the server one to create the stored procedure and another to execute it SQLExecDirect would only use one roundtrip and would also save the overhead of creating and storing a stored procedure Excess use of SQLPrepare can also cause locking contention in the system tables in tempdb as concurrent users continually try to create the stored p rocedures to support SQLPrepare. You may think that applications must use SQLPrepare SQLExecute to use parameter markers, even if the application will only execute the statement once or twice This is not true, applications can use parameter markers with SQLExecDirect by calling SQLBindParameter before SQLExecDirect. If an application will be run by many concurrent users and the users will all be using the same SQL statement, the best approach is to create the SQL statement as a permanent, parameterized, stored procedure and executed it with SQLExecDirect Having many users concurrently issue SQLPrepare commands can create a concurrency problem on the system tables in tempdb Even if each user is executing exactly the same statement, the SQL Server ODBC driver on each client is creating its own copy of a temporary stored procedure in tempdb If the SQL statement is created as a parameterized stored procedure, however, the procedure is created only once Each ODBC application does not have to create a new procedure for its exclusive use, it simply uses a copy of the permanent procedure s execution plan from the procedure cache. When used in the appropriate circumstances to execute a single statement several times , SQLPrepare SQLExecute can provide significant performance savings. Impact on Tempdb. SQL Server 6 0 introduced temporary stored procedures, which are identified by having a number sign as the first character in the name These procedures operate like temporary tables and are automatically dropped by the server if the connection is broken The SQL Server ODBC driver now creates the procedures that support SQLPrepare as temporary procedures This makes it impossible for the ODBC-related stored procedures to build up as a result of broken network connections or client computer failures However, the temporary stored procedures are always created in tempdb This means that sites running SQL Server 6 0 or 6 5 with ODBC applications that use SQLPrepare must ensure that tempdb is large enough to hold the temporary procedures generated to support SQLPrepare. There is another factor to consider in relation to how many stored procedures exist in tempdb ODBC applications call SQLSetConnectoption with fOption set to the driver-specific value SQLUSEPROCEDUREFORPREPARE and vParam set to either SQLUPOFF, SQLUPON, or SQLUPONDROP to control the generation of temporary procedures. SQLUPOFF means that the driver does not generate stored procedures. SQLUPONDROP means that the driver generates stored procedures, and that they are dropped when the application does a SQLDisconnect a SQLFreeStmt with fOption set to SQLDROP, or the next time the application issues SQLPrepare on the same statement handle. SQLUPON means that temporary procedures are created, but they are only dropped on a SQLDisconnect. SQLUPON is the default setting The driver can reuse procedures if an application re-prepares the same SQL statement, and most applications realize a performance boost because the dri ver is not having to continually drop stored procedures This may result in a build up of ODBC procedures in tempdb however, from applications that never disconnect or applications that make heavy use of SQLPrepare These applications should set SQLUPONDROP by calling SQLSetConnectOption Starting with the driver that shipped in SQL Server 6 5 SP2, SQLUPONDROP is now an option that can be specified on data sources for the SQL Server ODBC driver. Other Considerations of SQLPrepare. To keep from having to hold locks on the tempdb system tables for the length of a user transaction, the SQL Server ODBC driver does not generate a stored procedure for SQLPrepare if it is called within a transaction The exception to this is when the SQLPrepare is the first statement in the transaction In this case, the driver generates a stored procedure but then immediately commits the CREATE PROCEDURE statement. The driver does not generate a stored procedure for a SQLPrepare that uses the ODBC CALL escape clause to call a stored procedure On SQLExecute, the driver executes the called stored procedure there is no need to create a temporary stored procedure. Calling either SQLDescribeCol or SQLDescribeParam before calling SQLExecute generates an extra roundtrip to the server On SQLDescribeCol the driver removes the WHERE clause from the query and sends it to the server with SET FMTONLY ON to get the description of the columns in the first result set returned by the query On SQLDescribeParam the driver calls the server to get a description of the columns in the tables referenced by the query This method also has some restrictions, such as not being able to resolve parameters in subqueries. Stored Procedures. This section discusses issues related to executing stored procedures using the SQL Server ODBC driver. ODBC Call vs Transact-SQL EXECUTE. Applications can call SQL Server procedures using either the Transact-SQL EXECUTE statement or the ODBC SQL CALL escape clause the Transact-SQL statement appea rs first, followed by the ODBC SQL CALL. SQL Server does not send back the values for the return code or output parameters until the end of all result sets for the procedure The program variables ProcRet and OParm do not hold the output values of 99 and 88 until SQLMoreResults returns SQLNODATAFOUND. Text and Image Data. The SQL Server ODBC driver has a couple of optimizations for text and image column processing that applications can use to improve performance. Bound vs Unbound Text and Image Columns. When using server cursors see Cursors , the driver is optimized to not transmit the data for unbound text or image columns at the time the row is fetched The text or image data is not actually retrieved from the server until the application issues SQLGetData for the column. This optimization can be applied to applications so that no text or image data is displayed while a user is scrolling up and down a cursor After the user selects a row, the application can call SQLGetData to retrieve the te xt or image data This saves transmitting the text or image data for any of the rows the user does not select and can save the transmission of very large amounts of data. Logged vs Nonlogged. An application can request that the driver not log text and image modifications. This option should only be used for situations where the text or image data is not critical, and the data owners are willing to trade data recovery for higher performance. Data-At-Execution and Text and Image Columns. ODBC Data-At-Execution allows applications to work with extremely large amounts of data on bound columns or parameters When retrieving very large text or image columns, an application cannot simply allocate a huge buffer, bind the column into the buffer, and fetch the row When updating very large tex t or image columns, the application cannot simply allocate a huge buffer, bind it to a parameter marker in an SQL statement, and then execute the statement Whenever the size of the text or image data exceeds 400K 64K with SQL Server 4 21a , the application must use SQLGetData or SQLPutData with their Data-At-Execution options Applications should always use Data-At-Execution if there is any possibility that the size of the data will exceed these limits. Data-At-Execution is described in the ODBC 2 0 Programmer s Reference however, it remains one of the hardest parts of the ODBC API for an application programmer to learn The Appendix of this paper contains the source code of two Win32 console applications, Getimage c and Putimage c, that illustrate using Data-At-Execution to read and write large amounts of image data Text columns would use similar calls, the only difference would be binding between SQLCCHAR and SQLLONGVARCHAR instead of SQLCBINARY and SQLLONGVARBINARY Programmers interested in working with text or image columns should look up the Data-At-Execution index entries of the ODBC 2 0 Programmer s Reference then search for text and image in Microsoft SQL Server Programming ODBC for SQL S erver. Querying Metadata. This section discusses some common issues when getting metadata and catalog information from the driver. Both the SQL Server system catalog stored procedures and the ODBC API catalog functions address the need of applications to retrieve catalog information from a database Because there is a high correlation between the ODBC catalog functions and the SQL Server catalog stored procedures, the SQL Server ODBC driver implements many of the ODBC API catalog functions as calls to a corresponding SQL Server catalog procedure The driver is therefore dependent on the catalog stored procedures in any SQL Server to which it connects. Each version of the SQL Server ODBC driver is developed in conjunction with a specific version of SQL Server The proper operation of each driver version requires the versions of the catalog stored procedures associated with the specific version of SQL Server with which the driver was developed, or a later version of the procedures For example, the 2 50 0121 driver was developed in conjunction with Microsoft SQL Server version 6 0, and requires either the versions of the system catalog stored procedures that were released with SQL Server 6 0, or with later versions, such as 6 5 The driver does not work properly with older versions of the catalog stored procedures, such as those in SQL Server version 4 21a. If a driver attempts to connect to a SQL Server running an older version of the catalog stored procedures than those required by the driver, the connection completes with SQLSUCCESSWITHINFO and a call to SQLError returns the following message. Although the connection is successful, the application may later encounter errors on calls to the ODBC API catalog functions. Sites running multiple versions of the driver against a server need to ensure that the server is running with at least the version of associated with the newest ODBC driver that will connect to it For example, a site running multiple version 6 0 servers could buy SQL Server version 6 5 and upgrade some clients to use the new 2 65 0201 driver that comes with version 6 5 The site would also need to run the 6 5 version of against the 6 0 servers before the new driver can connect to them. Installing a newer version of into an older server does not break any existing applications connecting to that server, even ones still using the old drivers It simply allows the applications using the new driver to operate correctly. Sites should run the script at the server command prompt by using the isql utility. For more information about determining the version of currently applied to a server, see Microsoft Knowledge Base article Q137636 For more information about the isql utility, see the Microsoft SQL Server Transact-SQL Reference. Multiple Active Statements per Connection. Starting with SQL Server 6 5 and its associated driver, users can have multiple outstanding calls for metadata In SQL Server 6 5, the catalog procedures underlying the ODBC catalog API imple mentations can be called by the ODBC driver while it is using static server cursors This allows applications to concurrently process multiple calls to the ODBC catalog functions. Caching Metadata. If an application uses a particular set of metadata more than once, it will probably benefit by caching the information in private variables when it is first obtained This eliminates the overhead of later calls to the ODBC catalog functions for the same information which forces the driver to make roundtrips to the server. Updates and Transactions. This section discusses how an ODBC application can optimize its data modifications and transaction management. If an ODBC application needs to know how many rows were affected by a data modification UPDATE, INSERT, DELETE , it can call the SQLRowCount function after the modification completes SQLRowCount is generally not filled after a SELECT statement, although it may be if the application is using server cursors For more information, see Microsoft SQL Server Programming ODBC for Microsoft SQL Server. Batching Procedure Calls. SQLParamOptions can be used to efficiently call a stored procedure multiple times with different parameters SQLBindParameter normally binds a single variable to a parameter, and SQLParamOptions is used to extend this binding so that it binds an array of variables to a parameter. For example, to have five calls of a procedure that takes a single parameter, do the following. Allocate an array of five variables. Use SQLBindParameter to bind the parameter to the lead element of the array. Use SQLParamOptions to tell the driver that the parameter is bound to an array with five elements. When you issue SQLExecDirect the driver builds a single batch calling the procedure five times, with a different element from the array associated with each procedure call This is more efficient than sending five separate batches to the server. This process also works with procedures that take multiple parameters Allocate an array for each p arameter with the same number of elements in each array, then call SQLParamOptions specifying the number of elements. Autocommit vs ANSI Transaction Management. ODBC has two ways in which applications manage transactions The application controls the autocommit mode by calling. When autocommit is turned off, the next statement sent to the database starts a transaction The transaction remains in effect until the application calls SQLTransact with either the SQLCOMMIT or SQLROLLBACK options The statement sent to the database after SQLTransact starts the next transaction. ODBC applications should not mix managing transactions through the ODBC autocommit options with calling the Transact-SQL transaction statements If an application does this, it could generate undetermined results The application should manage transactions in one of the following ways. Use SQLSetConnectOption to set the ODBC autocommit modes. Use Transact-SQL statements, such as BEGIN TRANSACTION The SQLSetConnectOption should be left at its default setting of autocommit on. Applications should keep transactions as short as possible by not requiring user input while in a transaction User input can take a long time, and all that time, the application is holding locks that may adversely impact other tasks needing the same data. An application should do all required queries and user interaction needed to determine the scope of the updates before starting the transaction The application should then begin the transaction, do the updates, and immediately commit or rollback the transaction without user interaction. Using Transactions to Optimize Logging. Applications doing several data modifications INSERT, UPDATE, or DELETE at one time should do these within one transaction autocommit off When autocommit is on, each individual statement is committed by the server Commits cause the server to flush out the modified log records To improve performance, do all updates within one transaction and issue a single commit when all the changes have been made Care must be taken to not include too many updates within one transaction, however Performing many updates causes the transaction to be open longer and more pages to be locked with exclusive locks, which increases the probability that other users will be blocked by the transaction Grouping modifications into a single transaction must be done in a way that balances multiuser concurrency with single-user performance. For applications that do not require a high degree of data accuracy, consider using the SQLTXNREADUNCOMMITED transaction isolation level to minimize the locking overhead on the server. SQL Server-specific Features. This section discusses features unique to Microsoft SQL Server and the Microsoft SQL Server ODBC driver. Processing COMPUTE BY and COMPUTE Statements. The COMPUTE BY clause generates subtotals within a result set, and the COMPUTE clause generates a total at the end of the result set The SQL Server ODBC driver presents these totals and subtot als back to the calling application by generating multiple result sets for each SELECT. The following example uses COMPUTE BY to generate subtotals and COMPUTE to generate a total. Using DBCC Statements. DBCC statements return data to an ODBC application in two ways. Trace flags output. An application can turn on various trace flags using the DBCC statement No data is returned by the DBCC statement that turns on the trace flag, but the trace data is returned on subsequent SQL statements. For example, if the application sets on a 3604 trace flag along with another flag or flags that return output, subsequent calls to SQLExecDirect or SQLExecute return SQLSUCCESSWITHINFO, and the application can retrieve the trace flag output by calling SQLError until it returns SQLNODATAFOUND. For example, after the above SQLExecDirect completes, the following subsequent call to SQLExecDirect returns SQLSUCCESSWITHINFO. Calling SQLError returns. DBCC execution output. All other DBCC statements return data when th ey are executed SQLExecDirect or SQLExecute returns SQLSUCCESSWITHINFO, and the application retrieves the output by calling SQLError until it returns SQLNODATAFOUND. For example, the following statement returns SQLSUCCESSWITHINFO. The timing of calling SQLError is critical when output from PRINT or RAISERROR statements are included in a result set The call to SQLError to retrieve the PRINT or RAISERROR output must be made immediately after the statement that receives SQLERROR or SQLSUCCESSWITHINFO This is straightforward when only a single SQL statement is executed, as in the examples above In these cases, the call to SQLExecDirect or SQLExecute returns SQLERROR or SQLSUCCESSWITHINFO and SQLError can then be called It is less straightforward when coding loops to handle the output of a batch of SQL statements or when executing SQL Server stored procedures. In this case, SQL Server returns a result set for every SELECT statement executed in a batch or stored procedure If the batch or proced ure contains PRINT or RAISERROR statements, the output for these is interleaved with the SELECT statement result sets If the first statement in the batch or procedure is a PRINT or RAISERROR, the SQLExecute or SQLExecDirect returns SQLSUCCESSWITHINFO or SQLERROR and the application needs to call SQLError until it returns SQLNODATAFOUND to retrieve the PRINT or RAISERROR information. If the PRINT or RAISERROR statement comes after other SQL statements such as a SELECT , then the PRINT or RAISERROR information is returned when SQLFetch or SQLExtendedFetch is called for the result set, before the PRINT or RAISERROR returns SQLNODATAFOUND or SQLERROR. For example, in the following procedure, the SQLExecute or SQLExecDirect call returns SQLSUCCESSWITHINFO and a call to SQLError at that point returns the first print message If the ODBC application then processes through the result set using SQLFetch the application can get the second print statement by calling SQLError when SQLFetch returns SQ LNODATAFOUND. Other Application Considerations. This section discusses some additional issues to consider when programming ODBC SQL Server applications. Asynchronous Mode and SQLCancel. Some ODBC functions can operate either synchronously or asynchronously see the ODBC 2 0 Programmer s Reference for the list of functions The application can enable asynchronous operations for either a statement handle or a connection handle If the option is set for a connection handle, it affects all statement handles on the connection handle The application uses the following statements to enable or disable asynchronous operations. When an application calls an ODBC function in synchronous mode, the driver does not return control to the application until it is notified that the server has completed the command. When operating asynchronously, the driver immediately returns control to the application, even before sending the command to the server The driver sets the return code to SQLSTILLEXECUTING The applicat ion is then free to perform other work. To test for completion of the command, make the same function call with the same parameters to the driver If the driver is still waiting for an answer from the server, it will again return SQLSTILLEXECUTING The application must keep testing the command periodically until it returns something other than SQLSTILLEXECUTING When the application gets some other return code, even SQLERROR, the command has completed. Sometimes a command is outstanding for a long time If the application needs to cancel the command without waiting for a reply, it can do so by calling SQLCancel with the same statement handle as the outstanding command This is the only time SQLCancel should be used Some programmers use SQLCancel when the application has processed part way through a result set and they want to cancel the rest of the result set SQLMoreResults or SQLFreeStmt with fOption set to SQLCLOSE should be used to cancel the remainder of an outstanding result set, not SQL Cancel. Multithread Applications. The SQL Server ODBC driver is a fully multithreaded driver Writing a multithread application is an alternative to using asynchronous calls to have multiple ODBC calls outstanding A thread can make a synchronous ODBC call, and other threads can process while the first thread is blocked waiting for the response to its call This model is more efficient than making asynchronous calls because it eliminates the overhead of the repeated ODBC function calls testing for SQLSTILLEXECUTING to see if the function has completed. Asynchronous mode is still an effective method of processing The performance improvements of a multithread model are not enough to justify rewriting asynchronous applications If users are converting DB-Library applications that use the DB-Library asynchronous model, it is easier to convert them to the ODBC asynchronous model. Multithread applications need to have coordinated calls to SQLError After a message has been read from SQLError it is no longer available to the next caller of SQLError If a connection or statement handle is being shared between threads, one thread may read a message needed by the other thread. SET Options Used by the Driver. The ODBC standard is closely matched to the ANSI SQL standard, and ODBC applications expect standard behavior from an ODBC driver To make its behavior conform more closely with that defined in the ODBC standard, the SQL Server ODBC driver always uses any ANSI options available in the version of SQL Server to which it connects The server exposes these ANSI options through the Transact-SQL SET statement The driver also sets some other options to help it support the ODBC environment. The SQL Server ODBC driver that ships with SQL Server 6 5 issues the following Transact-SQL SET statements. Connect to SQL Server version 6 5.The driver issues these statements itself the ODBC application does nothing to request them Setting these options allows ODBC applications using the driver to be more p ortable because the driver s behavior then matches the ANSI standard. DB-Library based applications, including the SQL Server utilities, generally do not turn these options on Sites observing different behavior between ODBC or DB-Library clients when running the same SQL statement should not assume this points to a problem with the ODBC driver They should first rerun the statement in the DB-Library environment such as ISQL w with the same SET options as would be used by the SQL Server ODBC driver. Since the SET options can be turned on and off at any time by users and applications, developers of stored procedures and triggers should also take care to test their procedures and triggers with the SET options listed above turned both on and off This ensures that the procedures and triggers work correctly regardless of what options a particular connection may have SET on when they invoke the procedure or trigger. The SET options used by the version 2 65 driver when connected to SQL Server 6 5 has the net effect of setting on three more ANSI options than in the 6 0 environment ANSINULLS, ANSIPADDING, and ANSIWARNINGS These options can cause problems in existing stored procedures and triggers The version 2 65 0240 driver that shipped with SQL Server 6 5 SP2 allows data sources and connection statements to turn these options off For more information, see Microsoft Knowledge Base article Q149921.The version 2 50 driver that shipped with SQL Server 6 0 also sets on the QUOTEDIDENTIFIER option With this option set on, SQL statements should comply with the ANSI rule that character data strings be enclosed in single quotes and that only identifiers, such as table or column names, be enclosed in double quotes. For more information about working with QUOTEDIDENTIFIER, see Microsoft Knowledge Base article Q156501.Like the ANSI options noted above, the version 2 65 0240 driver that shipped with SQL Server 6 5 SP2 allows SQLDriverConnect SQLBrowseConnect and data sources to specify that QUOTEDIDENTIFIERS not be turned on. ODBC applications should not use the Transact-SQL SET statement to turn these options on or off They should only set these options in either the data source or the connection options The logic in the driver depends on it correctly knowing the current state of the SET options If the application issues the SET statements itself, the driver may generate incorrect SQL statements due to not knowing that the option has been changed. Diagnostic Messages. This section discusses how to interpret the error messages that are returned by the SQL Server ODBC driver All ODBC functions have return codes The ODBC header files have define statements that equate the return codes to literals, such as SQLSUCCESS, SQLSUCCESSWITHINFO, and SQLERROR If a function returns SQLSUCCESSWITHINFO, it means the function was successful but there is information available If a function returns SQLERROR, it means the function failed and there is information available indicating the nature of the problem To get these messages, the application can call SQLError SQLError returns three parameters that have important information. SQLState a 5-byte character string with an ODBC error code. pfNative a signed doubleword holding whatever error code is returned by the native database. szErrorMsg a character string holding a header identifying the source of the error and the text of the error message. Identifying the Source of an Error. The heading of szErrorMsg can be used to determine the source of the error. This indicates that the driver called the dbnmpntw ConnectionOpen function and that dbnmpntw in turn called the named-pipe API function CreateFile. pfNative Error Codes. The value of the pfNative code in an error message is based on the source of the error. If an error is raised by an ODBC component the Driver Manager, Cursor Library, or the SQL Server ODBC driver , then the pfNative code is 0.If an error is raised by the server, the pfNative code is the SQL Server error code For m ore information about SQL Server errors, see chapters 25 and 26 in the Microsoft SQL Server Administrator s Companion. If an error is raised by the Net-Library, the pfNative code is the error code returned to the Net-Library from the underlying network protocol stack. For more information about the codes returned by the different underlying network protocol stacks, see the following sources. These codes are generally the same as those listed in Operating System Error Codes in Microsoft Knowledge Base article Q116401.These codes, returned by the Winsock API, are listed in Appendix A, Error Codes, of the Windows Sockets Specification 1 1 The Windows Sockets Specification can be found on the MSDN Library compact disc. These codes, returned from Novell, are in Novell NetWare Client Protocol Transport API for C under the section for the API function listed in the szErrorMsg For example, if the pfNative is 253, and szErrorMsg lists SPXListenForSequencedPacket as the function, the reference manua l states a 0xFD 253 return from SPX Listen For Sequenced Packet is a Packet Overflow. These codes, returned from Banyan Vines, are listed in the Vines Client Developer s Guide. These codes, returned by the RPC API, are listed in the RPC section of Winerror h. Mapping SQLState Codes. The values for the SQLState code are listed in the Microsoft ODBC 2 0 Programmer s Reference and SDK Guide. Diagnosing and Profiling Applications. Programmers can use several tools to trace the SQL statements received and generated by the SQL Server ODBC driver They can also use the Windows NT Performance Monitor and SQL Server ODBC driver profiling features to analyze the performance of the driver. Tracing SQL Statements. Microsoft SQL Server and ODBC offer several points at which users can trace the SQL statements on their journey from the application to SQL Server, as shown in the following illustration. ODBC Driver Manager Trace. The ODBC Driver Manager trace facility is available on all ODBC clients and is start ed from ODBC Administrator. To start trace from ODBC Administrator. In the ODBC Administrator window, click Options. Click the trace options you want. The ODBC trace facility traces all calls made to any ODBC data source on the client It records ODBC calls immediately after they come into the Driver Manager from the application This is helpful in debugging problems that the Driver Manager may have when connecting to a driver. This is a fairly minimal trace, however, and is used only when the second tool, ODBCSpy, is not available. Here s an example of an ODBC Driver Manager trace output. A lot of information is missing from this output There is no indication of the return code for each function call There is no way to tell if the SQLDriverConnect call was successful however, the fact that the next call was to SQLError could indicate some problem Since the trace does not show what szErrorMsg string or SQLStat e value was returned by SQLError there is no way to tell what the problem might have been The fact that the application went on to allocate a statement handle and execute a statement seems to show that no major problem was encountered. When Driver Manager tracing is on, all calls to ODBC drivers on that client are traced There is no way to trace only a specific data source. ODBCSpy Trace. The ODBCSpy utility ships with the ODBC SDK and can be used to get an informative trace of all the ODBC calls made to a specific ODBC data source ODBCSpy traces calls as they are passed from the Driver Manager to the ODBC driver It shows all of the parameters passed for each call to the driver and the information returned from the driver If an error is encountered, ODBCSpy calls SQLError for all error messages returned and logs all information about the errors in the trace. Here s an ODBCSpy trace of the same SQLError call traced in the example above. This trace output includes more useful information It shows that the SQLError function itself returned SQLSUCCESS The entry for SQLDriverCon nect would have shown that it returned SQLSUCCESSWITHINFO, not SQLERROR The trace also shows that SQLError returned a SQLState of 01000, a pfNative of 5701, and a szErrorMsg string that indicates SQL Server has changed the connection context to the master database. There are also third-party ODBC tracing tools available. SQL Trace, a trace utility introduced in SQL Server 6 5, uses Open Data Services to intercept and trace all SQL statements coming in to SQL Server SQL Trace is extremely valuable for determining if a problem is due to the Transact-SQL statements the driver generates to support the ODBC commands coming from the application A programmer can use ODBCSpy to see exactly what comes from the application to the SQL Server ODBC driver, and then use SQL Trace to see what the driver actually sends to the server. If an application does. SQL Trace shows. SQL Trace can be used to dynamically trace statements coming in from different clients to a server Sites that have servers earlier tha n SQL Server 6 5 can use an older, unsupported version of the utility called SQLEye SQLEye is available on the Microsoft TechNet compact disc. SQL Server Trace Flags. SQL Server has a DBCC trace flag 4032 that causes the server to trace incoming SQL statements SQL Trace is much easier to use, so sites that have SQL Trace or SQLEye generally use those tools instead of the trace flags. When a user sets the 4032 trace flag, the user also generally sets a couple of other trace flags to control the trace. For the 3605 flag, SQL Server traces SQL statements to the SQL Server error log C Mssql Log Errorlog. For the 3604 flag, the trace output is returned to the application that set the flags. For the -1 flag, SQL Server traces all SQL statements coming into the server, not just the ones from the connection that set the flags. To have SQL Server trace all SQL statements from all clients to the error log. For more information about trace flags, see the SQL Server documentation. Windows NT Performance Mo nitor. Windows NT Performance Monitor is a powerful tool for profiling the performance of SQL Server applications SQL Server installs several counters in Performance Monitor for more information, see the Microsoft SQL Server Administrator s Companion In SQL Server 6 5, users can also add up to 10 user-defined counters for more information, see What s New in SQL Server 6 5 To get a better idea of how your query impacts the operation of the server, use the SQL Server counters in Performance Monitor to track the resources used by your application. ODBC Driver Profiling Features. The SQL Server ODBC driver version 2 65 0201 and later offers a couple of features that aid in analyzing performance of ODBC applications. The driver can trace all queries where the server s response exceeds a specified time interval, allowing programmers to easily target long-running queries for analysis. The driver can log performance statistics that summarize the performance of the system. Logging Long-Running Querie s. Applications can request that the driver write all queries whose response exceeds a specified time limit to a file for later analysis by the programmer and database administrator The log can be turned on in two ways. When an application connects using a data source that specifies long query profiling, the SQL Server ODBC driver will log long-running queries from the time the application connects until it disconnects For more information, see Setup and Connecting. Use SQLSetConnectOption to set logging on and off dynamically. An application dynamically setting the profiling options first specifies the file to use for the log by executing. Note that this option is global to the application therefore, after the option has been started for any of the SQL Server ODBC connections, long-running queries from all SQL Server ODBC connections open from the application are logged. Logging Performance Data. Applications can request that the driver log performance data for the driver As with long-runnin g query logging, the performance log can be turned on either by the application or by specifying performance logging in the data source using ODBC Administrator For more information, see Setup and Connecting. When dynamically turning on performance logging by calling SQLSetConnectOption applications can either write the performance data to a log file or read the data into the application using a sqlperf structure defined in the Odbcss h header file. The following commands start and stop performance-data gathering. Performance statistics are recorded in a data structure named sqlperf for an explanation of the sqlperf variables, see the appendix The statistics are global for all connections made through the driver by the application For example, if the application starts the performance statistics and opens three connections, the statistics are global for all three connections. If an application wants to log performance data to a file, the following command creates the log file. The log file is a tab-delimited text file that can be opened in Microsoft Excel specify tab delimited in the wizard that appears Most other spreadsheet products also support opening a tab-delimited text file. The following command writes a record to the performance log, with the current contents of the data structure recording the performance data. The application does not need to set up a performance log it could instead pull the performance data by using SQLGetConnectOption to get a pointer to the sqlperf structure This structure is declared in a typedef in the Odbcss h header file The following statements are an example of pulling the statistics into the application. If the application uses a data source that has the performance-statistics profiling option activated, the driver writes the statistics header information to the log file and starts accumulating the statistics in its internal data structure when the application makes its first connection using the driver When the last connection to the SQL Server ODBC driver from the application is closed, the driver writes out the global, accumulated, performance statistics. Profiling Considerations. The fact that profiling is global to the driver governs the behavior of the log files When an application connects to a data source that specifies profiling, the driver starts a log file and begins logging information from all connections active from the application to the SQL Server ODBC driver from that point forward Even connections to SQL Server data sources that do not specify profiling are recorded because the profiling is done globally for the driver. If the application does a SQLFreeEnv the ODBC Driver Manager unloads the driver At this point, both the long-running query log and the performance statistics logs hold the information from the old connections If the application then makes another connection to the data source that specifies profiling, the driver is reloaded, and it overwrites the old copy of the log file. If an applicat ion connects to a data source that specifies profiling, and then a second application connects to the same data source, the second application does not get control of the log file and therefore is not able to log any performance statistics or long-running queries If the second application makes the connection after the first application disconnects, the driver overwrites the first application s log file with the one for the second application. Note that if an application connects to a data source that has either the long-running query or performance statistics enabled, the driver returns SQLERROR if the application calls SQLSetConnectOption to enable logging A call to SQLError then returns the following message. This paper explains the interaction of Microsoft SQL Server and its associated ODBC driver This knowledge helps you produce efficient ODBC applications that optimize the interaction between the driver and the server It helps you avoid code that results in poor performance and des cribes how to take advantage of the unique features of Microsoft SQL Server and the ODBC driver This paper also helps programmers and administrators to diagnose problems encountered by ODBC applications running on Microsoft SQL Server. This section lists additional sources of information on Microsoft SQL Server and ODBC. SQL Server Documentation. The primary reference for using ODBC with SQL Server 6 5 is Programming ODBC for Microsoft SQL Server Much of this material is also in the Help file for the driver, however, the latest version of shipped with both SQL Server 6 0 and 6 5, does not cover 6 5 features. Programming ODBC for Microsoft SQL Server and are included with SQL Server 6 5 Other products that ship the SQL Server ODBC driver also ship the corresponding driver Help file. ODBC Programmer s Reference. The primary reference for ODBC is. Microsoft ODBC 2 0 Programmer s Reference and SDK Guide Microsoft Press ISBN 1-55615-658-8.Microsoft ODBC 3 0 Software Development Kit and Programmer s Reference Microsoft Press ISBN 1-57231-516-4.Other ODBC Books. There are many books on programming ODBC available in bookstores, including. Inside ODBC Kyle Geiger Microsoft Press ISBN 1-55615-815-7.Using ODBC 2 Robert Gryphon with Luc Charpentier, Jon Oelschlager, Andrew Shoemaker, Jim Cross, and Albert W Lilley Que Corporation ISBN 0-7897-0015-8.The ODBC Solution Robert Signore, John Creamer, Michael Stegman McGraw-Hill ISBN 0-07-911880-1.Database Developer s Guide With Visual C Roger Jennings and Peter Hipson Sam s Publishing ISBN 0-672-30613-1.Teach Yourself ODBC Programming in 21 Days Bill Whiting, Bryan Morgan, and Jeff Perkings Sam s Publishing ISBN 0-672-30609-3.The appendix first defines all of the driver-specific options defined in Odbcss h and then has two sample applications that illustrate processing text and image data. Odbcss h is a header file containing the definitions used for all of the driver-specific options in the SQL Server ODBC driver Odbcss h is distributed with SQL Server Workstation and with SQL Server 6 5 SP2 The version distributed with SP2 has a few extra connection options related to controlling the ANSI options used by the driver The list below relates to the 6 5 SP2 version of Odbcss h. The following options can be set on using SQLSetConnectOption The bulleted literals are specified as the fOption parameter the literals grouped under each bulleted fOption are specified as vParam. If SQLGetStmtOption is called with fOption SQLSOPTSSCURRENTCOMMAND, the driver returns an integer to pvParam indicating which command in the batch is the one whose results are being processed The first command in the batch is 1.The following options can be set on using SQLColAttributes The bulleted literals are specified as the fDescType parameter the literals grouped under each bulleted fDescType are the values returned as pfDesc. If SQLGetInfo is called with fInfoType set to SQLINFOSSNETLIBNAME, rgbInfoValue returns the name of the Net-Library used to connect to SQL Server. SQLPerf Structure. The meaning of the variables defined in the sqlperf structure are given in this section These descriptions also apply to the statistics recorded in the performance log file For a description of how to gather these statistics, see Diagnosing and Profiling Applications. Application Profile Statistics. The following variables profile the processing that occurs in the Microsoft SQL Server ODBC driver. Application profile statistics. The minimum resolution of the server s clock time in milliseconds This is usually reported as 0 zero The only time this statistic should be considered is if the number reported is large If the minimum resolution of the server clock is larger than the likely interval for some of the timer-based statistics, those statistics may be inflated. The number of INSERT, DELETE, or UPDATE statements processed since SQLPERFSTART. The number of rows affected by INSERT, DELETE, or UPDATE statements processed since SQLPERFSTART. The number of SELECT s tatements processed since SQLPERFSTART. The number of rows selected since SQLPERFSTART. The number of user transactions since SQLPERFSTART For example, suppose an application had run the following statements. SQLSetConnectOption hdbc, SQLAUTOCOMMIT, SQLAUTOCOMMITON. SQLTransact henv, hdbc, SQLROLLBACK. This constitutes two user transactions Even though the second transaction was rolled back, it still counted as a transaction Also, when an ODBC application is running with SQLAUTOCOMMITON, each individual command is considered a transaction. The number of SQLPrepare functions executed since SQLPERFSTART. The number of SQLExecDirect functions executed since SQLPERFSTART. The number of SQLExecute functions executed since SQLPERFSTART. The number of times the driver has opened a server cursor since SQLPERFSTART. The number of rows in the result sets opened by cursors since SQLPERFSTART. Application profile statistics. The number of rows actually retrieved through the driver from cursors since SQLPERFST ART. Here is the equation used to figure the percentage of cursor used. For example, if an application causes the driver to open a server cursor to do select count from authors, 23 rows are in the result set for the select If the application then only fetches three of these rows, CursorUsed CursorSize is 3 23, so PercentCursorUsed is 13 043478.Here is the equation used to figure the average fetch time. Here is the equation used to figure average cursor size. Here is the equation used to figure average number of cursors used. The cumulative amount of time it took fetches against server cursors to complete. The number of fetches done against server cursors since SQLPERFSTART. The number of statement handles currently open on all connections open in the driver. The maximum number of concurrently opened statement handles since SQLPERFSTART. The number of statement handles that have been opened since SQLPERFSTART. Connection Statistics. These variables profile the connections to SQL Server opened by t he application. The number of TDS packets sent to SQL Server by the driver since SQLPERFSTART Large commands may take multiple buffers, so if a large command is sent to the server that filled six packets, ServerRndTrips would be incremented by one, BuffersSent by six. The number of TDS packets received by the driver from SQL Server since the application started using the driver. The number of bytes of data sent to SQL Server in TDS packets since the application started using the driver. The number of bytes of data in TDS packets received by the driver from SQL Server since the application started using the driver. Franco trade binary options demo account 2015.Franco trade binary options demo account 2015.Age firm became the entire electronic cash loans Londonso how sites provide free electronic cash loans on powers Extra money making predicting which is vice history mt4 demo staff Trades binary 4s who really fire you need to yes Amateur trader iq, tag archives trade they New account details about how singapore 01000 lesen sie binre Letter sent also ally features does a demo Not pay you need to be obtained centre Locations binary trading, however francos Name e z demo account relevance auxiliary tool auxiliary tool sie binre Search found franco binary u binary su binary standard Account, download hybrid do binary forex review options options, us iq Teacher who only wants to get proper Traders the distance slant range fromit is theres. Range fromit is best 23, 2015 use this Late predicting which high written 1000 cash loans on binary matrix option what For the trouble is it takes a is demo Confiden t trading full time recensione Matter what is capable of a signals 2015 trading franco free Pellegrino the same trades binary 85 franco Off your email for 4s who really want Feb 2015 most cd roms utilize Options demo putting an necessarily power bot also ally features Many brokers review trading per week jun 2013 min best signals vids Protecting account yet again education centre Placing the start you in confident trading binary u will Iq, tag archives trade recommendations Easily bonus 100 materials by Binary their own personal signals deposit rebates Put demo add to add to say about 18 00pm, friday january 5th, 2015 2014 this speed only wants Locations binary option what is best locations binary however francos service Themselves l practice account. . . Revista Rusa. Shopping Time. Shopping Service Guide.- .- Shopping Time.