Testes de Iniciação e Disciplina Patinagem Artística HCM 24 Outubro 2020 @ Maceda

APP TV vodafone Windows

Esta mensagem de erro "Existe outro tipo de software de vídeo em funcionamento. Feche por favor estas aplicações e tente novamente". 

No meu caso era por ter em execução a aplicação Anydesk basta terminar a aplicação.

Filmagem parcial do treino com os Pousadinha e Mauro

The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /homeMagicMirror/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.

agicmirror@2.11.0 start /home/viper5000/MagicMirror

> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

[35198:0629/190209.828643:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/viper5000/MagicMirror/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.

$ find . -name chrome-sandbox
./node_modules/electron/dist/chrome-sandbox

$ sudo chown root ./node_modules/electron/dist/chrome-sandbox

$ sudo chmod 4755 ./node_modules/electron/dist/chrome-sandbox

Isso é o que se chama passar perto...

Treino Multisport Coimbra Bike

Track Mania Parte 2

TrackMania

trackmania ecrã em branco

Tutorial

1. Edit Nadeo.ini -file (this is the default installation path, your game files might be elsewhere.)

C:\Program Files\(x86)\Steam\steamapps\common\TrackMania Nations Forever\Nadeo.ini

2. Find a row with "Distro=XXXXX". Delete contents after "Distro=" and change it to "Distro=MILIN". Save and close the file.

3. Download the update file (it says "United Forever" but it doesn't matter, it works great with TM Nations too)

http://files2.trackmaniaforever.com/TmUnitedForever_Update_2010-03-15_Setup.exe

4. Install the patch and point it to your Trackmania Nations Forever folder, for example:

C:\Program Files\(x86)\Steam\steamapps\common\TrackMania Nations Forever

5. That's it! When the installation is finished, you are ready to play the game. Depending on what the problem was, the game should work well now.

Nadar no Mondego

Pinball Action

Sofia a jogar sonic

Como o bixo mexe é natal 4k

Converter uma imagem em vídeo, com o ffmpeg

ffmpeg -loop 1 -i in.png -c:v libx264 -t 7 -pix_fmt yuv420p -vf scale=X:Y viper5000.mp4

Torne o apt mais rápido

remover as traduções

sudo nano /etc/apt/apt.conf.d/99translations 

E adicione a linha:

Acquire::Languages "none";

sudo rm -rf /var/lib/apt/lists/* 

sudo apt update 

sudo apt upgrade

2 remover os dados de 32bitds

sudo nano /etc/apt/sources.list

ANTES

deb http://repositório de sua distro

no meu caso

deb http://deb.debian.org/debian buster main
DEPOIS
deb [arch=amd64] http://repositório de sua distro

sudo rm -rf /var/lib/apt/lists/* 

sudo apt update 

sudo apt upgrade

Materiais e a sua condutividade (eléctrica e térmica) e resistência eléctrica

Agora em Gráfico :) é bem mais fácil para analizar

ImportError: No module named setuptools

Traceback (most recent call last):
  File "setup.py", line 1, in 
    from setuptools import setup, find_packages, Extension
ImportError: No module named setuptools




sudo apt-get install python-setuptools

Impressoras 3d

Modelos

Os modelos mais comuns são os listados abaixo

• Eixos XYZ, com a cabeça de impressão nos eixos XZ e mesa no eixo Y. Neste modelo, a cabeça de impressão move para os lados e para cima, enquanto a mesa se move para frente e para trás. Ex: Prusa i3,  Mendel, Huxley, …
• Eixos XYZ, com a cabeça de impressão nos eixos XY e mesa no eixo Z. Neste modelo, a cabeça de impressão se move para os lados e para frente/trás, sendo que o conjunto fica fixo na parte superior. A mesa se move para baixo durante a impressão. Ex: Ultimaker, Cliever, ..
• Delta, em que existem 3 eixos verticais, ligados à cabeça de impressão através de um conjunto de hastes. Os eixos se movem para cima e para baixo, de forma sincronizada, para criar a movimentação da cabeça nos 3 eixos de impressão. Ex: Rostock, Kossel, …

Dentro destes 3 modelos, existem inúmeras variações, de forma que se torna inviável citar todas e descrever suas diferenças. O importante é que, dentro de cada modelo, as características que diferem são os materiais utilizados, o hardware (eletrônica, motores, …), o posicionamento do tracionador de filamentos, o posicionamento da eletrônica e fonte, o tipo de display utilizado. Assim, compreendendo cada um dos modelos, a escolha de uma ou outra variação se torna uma questão de mera conveniência.

Eixos XYZ

Os 2 primeiros são muito parecidos, ou seja, para qualquer um, o usuário vai acabar com um aparelho semelhante a um cubo (mais largo, mais profundo ou mais alto), com dimensões que partem 40cm de lado para uma mesa de 20cm x 20cm, aproximadamente.

Elas ocupam mais espaço, horizontalmente, porém, algumas delas, permitem mesas de impressão bastante grandes (60cm x 40cm de base, por exemplo). Também são menos complexas e de manutenção mais simples.

Delta

As Delta são impressoras onde a altura é, em geral 2x maior (ou mais) que a largura, possuindo uma mesa circular, a área de impressão é relativamente pequena, mas compensam na altura de impressão e na velocidade da cabeça de impressão (tendem a serem mais rápidas para imprimir peças mais complexas, onde a impressão não é contínua). A manutenção é um pouco mais complexa, pois a cabeça de impressão fica suspensa em 3 eixos.

Aquisição

Existem 3 forma de se adquirir uma impressora 3D FDM:

1. Comprar a impressora montada (pronta): Caso você não se considera apto a montar sua própria impressora, ou mesmo não tenha paciência para tal empreitada, sempre é possível comprar uma impressora pronta. Existem produtos mais comerciais, com marca própria e produtos mais “genéricos”, montados por empresas / pessoas especializadas. A vantagem disso é que, você recebe a impressora e, em uma hora ou duas, deve estar apto a utilizá-la. As desvantagens, são o preço mais alto e, em caso de problemas (defeitos de fabricação, componentes estragados), será necessário recorrer à assistência do fabricante ou vendedor.
2. Comprar um kit e montar você mesmo: Se você se considera apto a montar um dispositivo que possui partes mecânicas, fiação e eletrônica, se você possui paciência para investir entre 15 e 25 horas, se você consegue resistir a frustrações, então esse é a forma ideal de aquisição, na minha opinião. É consideravelmente mais barato do que adquirir uma impressora montada (às vezes até R$ 1.000,00 mais barato, ou mais), e você recebe todas as pelas necessárias de uma vez só, sem precisar garimpar lojas / internet. Além disso, ao montar o aparelho, você adquire conhecimento sobre o seu funcionamento, e tem condições de consertá-lo você mesmo. Por fim, da mesma forma, adquire conhecimento para poder realizar melhorias nela.
3. Comprar as peças de forma separada e montar você mesmo: Essa forma, apesar de ser a mais barata de todas, considero a menos recomendável. Obviamente, tem todas as vantagens e desvantagens da forma anterior, porém, é necessário que você tenha muito conhecimento do que está fazendo. Muitas pessoas pensam: “é só seguir o tutorial X”. Mas não é bem assim: muitos tutoriais são incompletos, por vezes, as peças utilizadas naquele tutorial não estão mais disponíveis ou são difíceis de encontrar. Além disso, várias peças estruturais, em geral, também são impressas, o que faz com que você precise de alguém que as imprima.

Calibrar o extrusor

medir 120mm e marcar o filamento  com origem no inicio do extrusor

Executar os comandos gcode

G1 E100 F100

medir novamente do extrusor até a marca do filamento

Correr o comando M503 ele vai devolver um valor.

encontre a linha M92 E e verifique o valor que está no final este e o valor atual 

passos por mm

Formula

120- valor medido do extrusor a marca= valor total da extrusão

Valor atual passos por mm *100 = Passos dados



Passos  / Valor actual extruido = valor correcto de passos por mm

agora

M92 Evalor correcto de passos por mm

para guardar

M500 

para confirmar se o valor foi guardado

M503 

para confirmar se ficou tudo bem

voltar a marcar 120m e

G1 E100 F100

Fonte dos dados

https://all3dp.com/

End Gcode

G91 ;Relative positioning
G1 E-2 F2700 ;Retract a bit
G1 E-2 Z0.2 F2400 ;Retract and raise Z
G1 X5 Y5 F3000 ;Wipe out
G1 Z10 ;Raise Z more
G90 ;Absolute positionning

G1 X0 Y{machine_depth} ;Present print
M106 S0 ;Turn-off fan
M104 S0 ;Turn-off hotend
M140 S0 ;Turn-off bed

M84 X Y E ;Disable all steppers but Z

start gcode

; Ender 3 Custom Start G-code by ViPeR5000
G92 E0 ; Reset Extruder
G28 ; Home all axes
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
M117 LET THE PURGE BEGIN!
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X5 Y20 Z0.3 F5000.0 ; Move over to prevent blob squish

M117 Autobots! Roll Out!

Eye robot controler

Eye robot controler

via IFTTT

Erro Buzz ps2

Erro Buzz ps2

via IFTTT

Filamento com diametros diferentes

no cura por exemplo, é melhor actualizar no flow
1.75/1.66*100=105.42%
Depois imprime um cubo 20mm sem top e bottom, 3 walls, e mede a grossura das paredes, se o nozzle for de 0.4mm então terão que dar 1.2mm (evite medir na parte onde fica colado na cama) se não der 1.2mm corrija o flow, se medir p.ex. 1.18mm
Regra 3 simples:
1.18mm -> 105.42%
1.2mm -> x
X = (1.2*105.42)/1.18
X =107.2%
Corrige o flow para 107.2% e imprime outro cubo, volta a medir e volta a corrigir se necessário.
Não esquecer de usar o valor do flow usado na impressão ao fazer o cálculo.

Client error on WebSocket API Cannot connect to host 172.30.32.1:8123

20-04-16 10:44:18 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-16 10:44:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-16 10:44:23 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-16 10:44:23 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-16 10:44:24 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/states/binary_sensor.snapshots_stale: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]

Adicionar

  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 192.168.1.0/24
        - 172.16.0.0/16
        - 127.0.0.1
        - ::1
      allow_bypass_login: true
    - type: homeassistant

No meu caso  - 172.16.0.0/16

VMware Workstation Device/Credential Guard are not compatible

bcdedit /set hypervisorlaunchtype off

/bin/rm: Argument list too long

Erro quando se tenta apagar uma pasta com uma grande quantidade de ficheiros
Quando se usa por exemplo

rm -rf *

Solução é

find . -type f -delete

The AppX Deployment Service (AppXSVC) service entered the running state.

The AppX Deployment Service (AppXSVC) service entered the running state.
The AppX Deployment Service (AppXSVC) service entered the stopped state.



"this process is used for installing, uninstalling, and updating Store apps. Windows automatically updates Store apps in the background, and many of the apps included with Windows"



Desativar o serviço.

ERROR (MainThread) [homeassistant.components.discovery] Network is unreachable

sudo sysctl net.ipv4.igmp_max_memberships=40

Wsus System.Data.SqlClient.SqlException -- Could not allocate space for object 'dbo.tbDeadDeployment'.'PK__tbDeadDe__5EF8D717DBC55AEB' in database 'SUSDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

System.Data.SqlClient.SqlException (0x80131904): Could not allocate
space for object 'dbo.tbXml'.'PK__tbXml__D14A66A975A36718' in
database 'SUSDB' because the 'PRIMARY' filegroup is full. Create disk
space by deleting unneeded files, dropping objects in the filegroup,
adding additional files to the filegroup, or setting autogrowth on for
existing files in the filegroup.
 at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsol
eteConnections(SqlException e)
 at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCo
mmandNoResult()
 at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAcce
ss.ExecuteSPImportUpdate(Int32 upstreamServerLocalId, String
xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, Int32&
localRevisionId)
 at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAcce
ss.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[]
xmlUpdateBlobCompressed, String xmlSdpBlob, Int32&
localRevisionId)
 at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAcce
ss.ImportUpdateWithFileUrls(Int32 upstreamServerLocalId, String
xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, String
xmlSdpBlob, ServerSyncUrlData[] fileUrls, Boolean setCatalogSiteFlag,
Guid updateId)
 at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ImportSi
ngleUpdate(ServerSyncUpdateData updateData, List`1 allFileUrls)
 at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ImportM
ultipleUpdates(List`1 metadata, List`1 fileUrls, Boolean isConfigData)
ClientConnectionId:652a1b25-c14d-4f9e-8297-b0295fbcac46
Error Number:1105,State:2,Class:17

System.Data.SqlClient.SqlException (0x80131904): Could not allocate
space for object 'dbo.tbXml'.'PK__tbXml__D14A66A975A36718' in
database 'SUSDB' because the 'PRIMARY' filegroup is full. Create disk
space by deleting unneeded files, dropping objects in the filegroup,
adding additional files to the filegroup, or setting autogrowth on for
existing files in the filegroup.
 at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsol
eteConnections(SqlException e)
 at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCo
mmandNoResult()
 at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAcce
ss.ExecuteSPImportUpdate(Int32 upstreamServerLocalId, String
xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, Int32&
localRevisionId)
 at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAcce
ss.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[]
xmlUpdateBlobCompressed, String xmlSdpBlob, Int32&
localRevisionId)
 at
Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAcce
ss.ImportUpdateWithFileUrls(Int32 upstreamServerLocalId, String
xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, String
xmlSdpBlob, ServerSyncUrlData[] fileUrls, Boolean setCatalogSiteFlag,
Guid updateId)
 at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ImportSi
ngleUpdate(ServerSyncUpdateData updateData, List`1 allFileUrls)
 at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ImportM
ultipleUpdates(List`1 metadata, List`1 fileUrls, Boolean isConfigData)
ClientConnectionId:652a1b25-c14d-4f9e-8297-b0295fbcac46

Error Number:1105,State:2,Class:17



Possíveis problemas

1 Falta de espaço no disco

2 Limitação da base dados SQL activar autogrouwth / maxsize

Abrir o SqL Management
Propriedades da Base de dados
Files

3 Teres atingido os 10GB do SQL express e não teres licença para uma base de dados maior.
conclusão tens que passar para o Windows Internal Database

SQL Server Database Growth and Autogrowth Settings

It's easy to create a database nowadays with point-'n-click, but if you've left your database's autogrowth settings at their default, you may hit problems in the future. Why? What do I do about it? Read on!

There are a lot of maintenance jobs that SQL Server performs under the covers. Whilst this makes SQL Server an easier database management system to administer with very little training, it has the consequence that the industry has many accidental DBAs who are managing SQL Server without really knowing what the database engine does behind the scene to keep their databases up and running. Microsoft provides point and click actions to define a number of maintenance tasks like defining databases, creating tables, backing up databases, performing data integrity checks, shrinking databases, etc. Being able to create these routine database administration tasks provides using point and click provides the accidental DBA an easy method to quickly build maintenance routines.

Many of these automatic maintenance events that SQL Server handles for you are controlled using configurable settings that have predetermined values which might not be appropriate in all installations. As a DBA you have control to override the predetermined configuration settings and you should consider providing a setting that is appropriate for your situation, One of those settings you should know something about is the ‘auto-growth’ settings that are established when you first create a database. In this article I will discuss the auto-growth options for a database, and how you should use it to appropriately manage your database growth. Additionally, I will provide you with some scripts to help you manage your database auto-growth events.

Auto-growth

What exactly are auto-growth events? An auto-growth event is the process by which the SQL Server engine expands the size of a database file when it runs out of space. The amount by which a database file grows is based on the settings that you have for the file growth options for your database.

Each database file that is associated with your database has an auto-growth setting. There are three different settings you can use to identify how your database files will grow. They can grow by a specific size, a percentage of the current size, or not grow at all. Additionally you can set your files to unrestricted growth, which means they will keep growing as they need more space or you run out of disk space. Or you can restrict the growth of a database file to grow no larger than a specified size. Each one of these different auto-grow setting have defaults, or you can set them for each database file.

If you are not properly managing your auto-growth setting for a database, then your database might experience many auto-grow events, or very few. Auto-growth events. Each time an auto-growth event is performed SQL Server holds up database processing while an auto-growth event occurs. This means that processing against that database will be held up while the auto-growth event completed. This equates to slower response time for those SQL commands that are being processing against the database that is growing.

When an auto-growth event occurs SQL Server needs to find additional disk space in which the database can grow. Most likely this disk space will not be physically right next to the existing database space, but instead will be somewhere else on the disk. This causes your database file to be physically fragmented on the disk. The more auto-growth events you have the more physical fragmentation you will have. When your database is physically fragmented it takes longer for SQL Server to read that databases, because it has to move the disk head around to all the different fragmented pieces to read your database. To avoid the issues associated with auto-growth events you need to minimize the number of auto-growth events that occur.

The default auto-growth settings for a database are rarely the ideal settings for how your database should grow. If you have an idea of the growth profile of your database when you first build it then you should set your auto-growth properties based on those growth projections. If you don’t have any idea of how fast your database will grow then you should be monitoring for auto-growth events. Knowing how often your database grows will give you some ideas of the growth rate of your database.

Establishing Your Auto-growth Settings When Creating a New Database

You can set database auto-growth setting by using SQL Server Management Studio, scripted SMO or by using T-SQL when you create your database. You can also use these methods to change the auto-growth settings of existing databases. Let me first show you how to set the auto-grow settings using SQL Server Management Studio when you create a database.

The initial settings for auto-growth are set to the default values when defining a new database. These defaults are established by using the auto-growth settings on the model database files. You can see my default values on the “New Database” screen shot in Figure 1 when I am creating a new database named “MyDB”. My default auto-growth setting for the data file is 1 MB with unrestrictive growth, and the log file is set to grow by 10% with unrestricted growth. If you haven’t tweaked your model database settings then you will have the same default auto-growth setting as I do.

Figure 1: Setting Auto-grow settings using the New Database dialog

By clicking on the ellipses buttons, which are circled in red in Figure 1, I can define auto-growth settings that make sense for the database I am creating. When I click on the ellipses button the Windows dialog box in Figure 2 is displayed.

Figure 2: Options for Changing the Autogrowth settings

Using the dialog box shown in Figure 2 I can change my file auto-growth option to any one of the three different possible values. The first option is the check box at the top that says “Enable Autogrowth”. This option allows you to turn on or off whether “MyDB” can auto-grow. By having this box checked I’m telling SQL Server to allow this database to auto-grow. By unchecking this box I’m telling SQL Server I do not want my database to auto-grow.

The next option I can set is the “File Growth” option. It allows me to set how my data file will grow when it runs out of space. As you can see there are two radio buttons identifying whether or not you want the file to grow by a percentage or in megabytes. I normally only allow my database auto-grow settings to grow based on megabytes instead of a percentage; I do this because I want all my auto-growth events to be of a uniform fixed size. If I was to allow them to grow based on a percentage, the auto-growth amount would get bigger as my database got larger. When databases are allowed to grow by a percentage the amount they grow might be substantial especially for the large multi-gigabyte or terabyte databases. If a large database was to grow based on a percentage it most likely will take way more space then it will needs to handle growth for next year, or so. This causes these large databases to be over allocated from a disk space perspective. Worse yet a large database might grow so big it takes all the available disk space, and we don’t want this to happen. When setting the number of megabytes a new database should grow I do it based on whatever information I have regarding the growth profile of the new database.

The last option is the “Maximum File Size” option. This option allows me to set the maximum size that SQL Server will allow my file to grow. I normally use the unrestricted growth option, because I know most of my applications are well behaved and are highly unlikely to grow uncontrollably. Plus using the unrestricted options minimizes application failures due to auto-growth restrictions. I also monitor disk space usage and auto-growth events fairly close so I would most likely notice a database consuming all of my available disk space. If you want to make sure no one database uses up all your disk space then setting a maximum file size would be a way to prevent this.

If you are using T-SQL to create a new database you can set the auto-growth options on the CREATE DATABASE command. The code in Listing 1 shows how I can set auto-growth option when I create a new database named AnotherDB.

USE MASTER; GO CREATE DATABASE AnotherDB ON ( NAME = AnotherDB_data,     FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\AnotherDB.mdf',     SIZE = 125MB,     MAXSIZE = 500MB,     FILEGROWTH = 25MB ) LOG ON ( NAME = AnotherDB_log,     FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\AnotherDB.ldf',     SIZE = 5MB,     FILEGROWTH = 5MB ) ; GO

Listing 1: Setting auto-grow sizes when creating database using T-SQL

If you look at the code in Listing 1 you can see that I used the MAXSIZE, and FILEGROWTH options of the CREATE DATABASE command to control the auto-growth options of my database files. The MAXSIZE option is used to specify how large a file can grow and the FILEGROWTH option is used to specify how much my file is supposed to grow each time it needs to grow. The code in Listing 1 allows my file “AnotherDB_data” to grow to a maximum size of 500MB in 25MB chunks. For the log file “AnotherDB_log”, I allowed it to grow unrestricted, since I didn’t provide a “MAXSIZE” options, but when it does grow it will grow in “5MB” chunks.

Identifying Databases that are using the Default Auto-growth Settings

The default auto-grow settings associated with the installed model database are not the best settings for how databases grows. If you have inherited a SQL Server Instance, or haven’t been diligent at setting the auto-grow parameters when you created databases then you might want scan your instance to determine which databases are using the default setting.

Remember now that the default settings for auto-growing for the model database that is installed with SQL Server data is 1 MB for data files and 10% for log files. Therefore it is a simple matter of running a T-SQL script against your instance to identify those databases that are using the default auto-growth settings. In Listing 2 I provide the script I use to identify databases that use the default auto-growth settings.

-- Drop temporary table if it exists IF OBJECT_ID('tempdb..#info') IS NOT NULL        DROP TABLE #info;   -- Create table to house database file information CREATE TABLE #info (      databasename VARCHAR(128)      ,name VARCHAR(128)     ,fileid INT     ,filename VARCHAR(1000)     ,filegroup VARCHAR(128)     ,size VARCHAR(25)     ,maxsize VARCHAR(25)     ,growth VARCHAR(25)     ,usage VARCHAR(25));      -- Get database file information for each database   SET NOCOUNT ON; INSERT INTO #info EXEC sp_MSforeachdb 'use ? select ''?'',name,  fileid, filename, filegroup = filegroup_name(groupid), ''size'' = convert(nvarchar(15), convert (bigint, size) * 8) + N'' KB'', ''maxsize'' = (case maxsize when -1 then N''Unlimited'' else convert(nvarchar(15), convert (bigint, maxsize) * 8) + N'' KB'' end), ''growth'' = (case status & 0x100000 when 0x100000 then convert(nvarchar(15), growth) + N''%'' else convert(nvarchar(15), convert (bigint, growth) * 8) + N'' KB'' end), ''usage'' = (case status & 0x40 when 0x40 then ''log only'' else ''data only'' end) from sysfiles ';   -- Identify database files that use default auto-grow properties SELECT databasename AS [Database Name]       ,name AS [Logical Name]       ,filename AS [Physical File Name]       ,growth AS [Auto-grow Setting] FROM #info WHERE (usage = 'data only' AND growth = '1024 KB')    OR (usage = 'log only' AND growth = '10%') ORDER BY databasename   -- get rid of temp table DROP TABLE #info;

Listing 2: Identify databases that have default auto-grow settings

The script in listing 2 uses an undocumented system stored procedure sp_MSforeachdb stored procedure to get the auto-growth setting from the sysfiles system table within each database, and store that information into a temporary table. Note the sp_MSforeachdb system store procedure has a bug in the code that causes it to sometime to not process through each and every database. Aaron Bertrand has noted this bug in his blog and has identified alternative method for processing through all databases with a T-SQL script: http://sqlblog.com/blogs/aaron_bertrand/archive/2010/02/08/bad-habits-to-kick-relying-on-undocumented-behavior.aspx. If you really want to make sure this code doesn’t randomly skip databases then I would suggest you implement a solution similar to solution to the one that Aaron’s documented in the link above when processing through your databases. For the case of displaying databases that are using the default auto-grow settings doing this is not critical but you still might miss databases.

Changing the Auto-grow settings of an Existing Database

Like most SQL Server settings, you can change them using either SQL Server Management Studio GUI tool, a script using SMO, or you can write T-SQL to modify them. To change the auto-growth setting in SQL Server Management Studio, first right click on the database for which you want to change the auto-growth settings and then click on the “Properties” item in the menu that is displayed. This will bring up the “Database Properties” dialog box for the database you selected. Next click on the “Files” item in the left pane under the “Select a page” section, this will display the database file information in the right pane. To get to the window where you can actually change the auto-growth setting, click on the button containing the 3 dots (“…”) or commonly referred to as the ellipses button. That will bring up the “Change Autogrowth…” window as seen in Figure 2. In the “Change Autogrowth…” window you can change the auto-grow settings for your database, just like you would when you create a database using SQL Server Management Studio. In Listing 3 I have provided a SQL statement that changes the FILEGROWTH settings for a database named “MyDB”.

ALTER DATABASE MyDB   MODIFY FILE   (NAME=MyDB_Log,FILEGROWTH=20MB);

Listing 3: Change the Auto-growth setting using T-SQL

In the ALTER DATABASE statement in Listing 3 I set FILEGROWTH size of the transaction log file named “MyDB_Log” in database MyDB to 20 MBs. You can use the ALTER DATABASE MODIFY FILE option to set the auto-growth numbers for any one of the files (DATA and/or transaction Log) associated with a database.

Identifying How Often an Auto-growth Event has Occurred

When SQL Server performs an auto-grow event, the transaction that triggered the auto-grow event will have to wait until the auto-grow event completes before the transaction can finish. These auto-growth events cause your performance to degrade a little when an auto-grow event is taking place. For this reason it is best if you can size your database appropriately so auto-growth events rarely occur.

If you are interested in how often an auto-growth event occurs on your system you can capture those events using a trace. By knowing which databases are performing auto-growth events allows you to adjust those database file growth properties so they will perform auto-growth events less frequently. You can use the profiler “Data File Auto-grow” and/or the “Log File Auto-grow” events to track these database auto-growth events. If you are running SQL Server 2005 or above, both these auto-grow events are already being captured by the default trace. If you haven’t turned off the default trace then you can use the default trace file to find these auto-grow events. If you have turned off the default trace you can either enable it, or setup a new profiler trace to capture the “Data File Auto-grow” and “Log File Auto-grow” events.

The default trace logs to a file. I have provided the code in Listing 4 to show you how to extract all the auto-growth events from the default trace files. If you create your own profiler trace session to capture these auto-grow events then you will need to modify this script to meet your profiler trace settings.

DECLARE @filename NVARCHAR(1000); DECLARE @bc INT; DECLARE @ec INT; DECLARE @bfn VARCHAR(1000); DECLARE @efn VARCHAR(10);   -- Get the name of the current default trace SELECT @filename = CAST(value AS NVARCHAR(1000)) FROM ::fn_trace_getinfo(DEFAULT) WHERE traceid = 1 AND property = 2;   -- rip apart file name into pieces SET @filename = REVERSE(@filename); SET @bc = CHARINDEX('.',@filename); SET @ec = CHARINDEX('_',@filename)+1; SET @efn = REVERSE(SUBSTRING(@filename,1,@bc)); SET @bfn = REVERSE(SUBSTRING(@filename,@ec,LEN(@filename)));   -- set filename without rollover number SET @filename = @bfn + @efn   -- process all trace files SELECT   ftg.StartTime ,te.name AS EventName ,DB_NAME(ftg.databaseid) AS DatabaseName   ,ftg.Filename ,(ftg.IntegerData*8)/1024.0 AS GrowthMB ,(ftg.duration/1000)AS DurMS FROM ::fn_trace_gettable(@filename, DEFAULT) AS ftg INNER JOIN sys.trace_events AS te ON ftg.EventClass = te.trace_event_id   WHERE (ftg.EventClass = 92  -- Date File Auto-grow     OR ftg.EventClass = 93) -- Log File Auto-grow ORDER BY ftg.StartTime

Listing 4: Display Auto-growth Events Contained in the Default Trace files

The code in Listing 4 identifies the name of the current trace file by using the fn_trace_getinfo function. Since the default trace might have multiple rollover files, I have to rip apart the file name so I can get the file name without the rollover number included. The code then passes the file name to the fn_trace_gettable function to return the profiler trace information from all the different rollover trace files. By using the output produced by this code you can identify what databases have had auto-growth events and when those auto-growth events have occurred. If this code doesn’t produce any auto-growth events then that means your instance doesn’t have any auto-growth events captured in the existing default trace files. In Report 1 I have provided a sample of the output produced by the code in Listing 4.

StartTime               EventName              DatabaseName  Filename    GrowthMB  DurMS ----------------------- ---------------------- ------------- ----------- --------- ----- 2011-10-21 20:01:00.483 LOG FILE Auto-grow     tempdb        templog     0.312500  10 2011-10-28 10:33:41.343 Data FILE Auto-grow    VNIK          VNIK_Data   0.250000  26 2011-10-30 17:00:50.703 Data FILE Auto-grow    PERS          PERS_Data   1.000000  26

Report 1: Sample Output of the Data and Log Auto-growth Events

If you really want to keep a close eye on your auto-growth events you could create a SQL Agent job that sends you email about recent auto-growth events. The SQL Agent job could be run as a routine, and should execute some code similar to the code in Listing 4 that would show all auto-growth events since the last time the SQL Agent job ran. In Listing 5, I’ve provided a sample of some code that you could put in your SQL Agent job.

-- This script will email DBA if a auto-grow event occurred in the last day -- Written by: Greg Larsen -- Date: 10/06/2011   DECLARE @filename NVARCHAR(1000); DECLARE @bc INT; DECLARE @ec INT; DECLARE @bfn VARCHAR(1000); DECLARE @efn VARCHAR(10); DECLARE @DL VARCHAR(1000); -- email distribution list DECLARE @ReportHTML  NVARCHAR(MAX); DECLARE @Subject NVARCHAR (250);   -- Set email distrubution list value SET @DL = 'greg.larsen@simple-talk.com'   -- Get the name of the current default trace SELECT @filename = CAST(value AS NVARCHAR(1000)) FROM ::fn_trace_getinfo(DEFAULT) WHERE traceid = 1 AND property = 2;   -- rip apart file name into pieces SET @filename = REVERSE(@filename); SET @bc = CHARINDEX('.',@filename); SET @ec = CHARINDEX('_',@filename)+1; SET @efn = REVERSE(SUBSTRING(@filename,1,@bc)); SET @bfn = REVERSE(SUBSTRING(@filename,@ec,LEN(@filename)));   -- set filename without rollover number SET @filename = @bfn + @efn   -- Any Events Occur in the last day IF EXISTS (SELECT *              FROM ::fn_trace_gettable(@filename, DEFAULT) AS ftg                WHERE (EventClass = 92  -- Date File Auto-grow                    OR EventClass = 93) -- Log File Auto-grow                   AND StartTime > DATEADD(dy,-1,GETDATE())) BEGIN -- If there are autogrows in the last day   SET @ReportHTML =     N' ' + N'Auto-grow Events for ' +    CAST(SERVERPROPERTY('MachineName') AS NVARCHAR(128)) +     + CASE WHEN SERVERPROPERTY('InstanceName') IS NULL            THEN ''              ELSE N'\' +  CAST(SERVERPROPERTY('InstanceName') AS NVARCHAR(128))       END +     N'

' +

    N'' +

    N' Start TimeEvent Name' +

    N'Database NameFile NameGrowth in MB' +

    N'Duration in MS

' +

    CAST((SELECT

              td = ftg.StartTime, '',

              td = te.name, '',

              td = DB_NAME(ftg.databaseid), '',

              td = Filename, '',

              td =(ftg.IntegerData*8)/1024.0, '',

              td = (ftg.duration/1000)

          FROM ::fn_trace_gettable(@filename, DEFAULT) AS ftg

               INNER JOIN sys.trace_events AS te ON ftg.EventClass = te.trace_event_id  

          WHERE (EventClass = 92  -- Date File Auto-grow

              OR EventClass = 93) -- Log File Auto-grow

             AND StartTime > DATEADD(dy,-1,GETDATE()) -- Less than 1 day ago

          ORDER BY StartTime  

          FOR XML PATH('tr'), TYPE

    ) AS NVARCHAR(MAX) ) +

    N'

' ;

    

 

    

    -- Build the subject line with server and instance name

    SET @Subject = 'Auto-grow Events in Last Day ' +

                   CAST(SERVERPROPERTY('MachineName') AS NVARCHAR(128)) +

                 + CASE WHEN SERVERPROPERTY('InstanceName') IS NULL

                        THEN ''  

                        ELSE N'\' +  CAST(SERVERPROPERTY('InstanceName') AS NVARCHAR(128))

                   END

 

    -- Send email to distribution list.    

    EXEC msdb.dbo.sp_send_dbmail @recipients=@DL,

           @subject = @Subject,  

           @body = @ReportHTML,

           @body_format = 'HTML',

           @profile_name='Server_DBAs Mail' ;

END; -- If there are autogrows in the last day

Listing 5: Email the Auto-growth events that have occurred in the last 24 hours to the DBA

The code in Listing 5 shows all the auto-growth events that have occurred in the last 24 hours. If an auto-growth event is found then it emails me a report of the auto-growth events.

Don’t let your Auto-growth Events Run Wild

Auto-growth events are expensive operations that slow down the performance of your database. Take the following preventive steps to ensure your auto-growth events do not run wild:

• Pre-Size your databases and establishing appropriate auto-growth settings for your databases based on their growth profile.
• Minimize future auto-growth events by monitoring the growth of your databases, and re-establishing auto-growth settings when a database growth profile changes.
• Monitor auto-growth events so you can be alerted when your databases grow.
• Consider defragmenting your database file system if you have let your auto-growth run wild.

Taking these preventive and proactive measures will help improve your database performance and better manage your disk space utilization.

fonte https://www.red-gate.com/simple-talk/sql/database-administration/sql-server-database-growth-and-autogrowth-settings/